On Mar 2, 2013, at 8:02 PM, Ross Gardler <rgard...@opendirective.com> wrote:
> On 2 March 2013 10:37, Shane Curcuru <a...@shanecurcuru.org> 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 more high school level (I forget its name) but it runs > later in the year and projects are discreet and less code focussed. We've > not participated in that programme for a good few years but that's only > been due to lack of someone to drive our engagement. Is it Google Code-in [1] ? Documentation seems to rightly fit here. Suresh [1] - https://developers.google.com/open-source/gci/2012/ > > Ross > > > >> 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 >> fundraising look a little prettier, having an easier to navigate events >> area, etc. >> >> Should I try to find enough discrete tasks here to submit a >> documentation-type GSoC idea? Or is that not likely to find any students / >> going to be too much work to pull together? >> >> I love the idea of offering a non-heavy-code project, and I will have a >> little spare time over the summer (when I'm taking a 12 week leave of >> absence from $dayjob). >> >> Ideas? Anyone want to help? >> >> - Shane >> > > > > -- > Ross Gardler (@rgardler) > Programme Leader (Open Development) > OpenDirective http://opendirective.com
