On 2 March 2013 17:58, Tim Williams wrote:
>
> Wow, that's pretty awesome, I'd like for us to start participating in
> this - these are tomorrow's committers:) What a great soft
> introduction!
>
>
Brilliant. Consider yourself committed ;-)
I'll nag you nearer the time.
Ross
> --
> Ross Gard
On Sat, Mar 2, 2013 at 5:47 PM, Suresh Marru wrote:
> On Mar 2, 2013, at 8:02 PM, Ross Gardler wrote:
>
>> On 2 March 2013 10:37, Shane Curcuru wrote:
>>
>>> Quick sanity check: would it be worthwhile to explore having a non-code
>>> project?
>>
>>
>> Google have always, in the past, been agains
On Mar 2, 2013, at 8:02 PM, Ross Gardler wrote:
> On 2 March 2013 10:37, Shane Curcuru wrote:
>
>> Quick sanity check: would it be worthwhile to explore having a non-code
>> project?
>
>
> Google have always, in the past, been against non-code projects in GSoC.
>
> Assuming this has not chan
On 2 March 2013 10:37, Shane Curcuru wrote:
> Quick sanity check: would it be worthwhile to explore having a non-code
> project?
Google have always, in the past, been against non-code projects in GSoC.
Assuming this has not changed, your ideas are better suited to the other
initiative which is
Hi Shane,
a big + 1 for what you want to accomplish, but I am afraid it might not qualify
as a GSOC project. There was a discussion on gsoc mentor lists recently if CSS
qualifies as a gsoc project. There were mixed opinions without concluding
thoughts but it was clear documentation does not qua
Quick sanity check: would it be worthwhile to explore having a non-code
project? We often decry the lack of understandable or organized
technical documentation, especially on the apache.org site. Similarly,
we could do a much better job simply clearly describing things for
branding, making fu
