[Owasp-leaders] Google Code-in 2014 // Call for volunteers

Fabio Cerullo fcerullo at owasp.org
Fri Nov 7 15:47:42 UTC 2014

hi there,

We are putting together a list of tasks that could be done by 13-17 years
old teenagers on this page as part of the Google Code-In initiative:


- Do you need a new logo for your project?
- Do you need someone to update your wiki page?
- Do you need to translate some documentation?
- Do you need to fix a small bug in your code base?
- Do you want to create videos about your project?

Please go ahead and add any tasks that you consider beneficial to your
project/chapter/etc. Next Monday we will know if OWASP has been accepted in
Google Code-In.

And if you want to join this effort, please ping me offline.


On Tue, Nov 4, 2014 at 12:33 AM, Fabio Cerullo <fcerullo at owasp.org> wrote:

> hi there,
> Do you have plenty of small tasks that need to be accomplished for your
> OWASP project but don't have the time/resources to do them? Eg. wiki pages
> that need to be updated, documentation that needs to be completed, a small
> patch/fix that needs to be developed.
> Would you be interested to have a passionate group of teenagers students
> working on various tasks for your OWASP project?
> Google runs a programme called Google Code-in (GCI) that might be the
> right fit for you.
> *So, what is GCI?*
> Google Code-in is a contest for pre-university students (e.g., high school
> and secondary school students ages 13-17) with the goal of encouraging
> young people to participate in open source by doing small tasks. The best
> students who complete these tasks get a ticket to Google HQ in San
> Francisco.
> *What kind of tasks?*
> The tasks are grouped into the following categories:
> *Code: *Tasks related to writing or refactoring code
> *Documentation/Training: *Tasks related to creating/editing documents and
> helping others learn more
> *Outreach/Research: *Tasks related to community management,
> outreach/marketing, or studying problems and recommending solutions
> *Quality Assurance:* Tasks related to testing and ensuring code is of
> high quality
> *User Interface: *Tasks related to user experience research or user
> interface design and interaction
> Tasks generally take students 3-5 hours to complete. Usually, a
> participating organisation generates between 200-250 tasks during the time
> frames set below.
> *Time frames*
> The Google Code-in 2014 contest will run from December 1, 2014 to January
> 19, 2015. *The deadline for organisations to apply is November 10th,
> 2014.*
> *Interested?*
> Please ping me as I'm trying to build a team before the GCI submission
> deadline next 10th November. The only condition to participate is to have
> plenty of ideas/tasks for the students to progress them, and loads of
> patience to handle a highly demanding & young task force group.
> Thanks for your support.
> All the best,
> Fabio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-leaders/attachments/20141107/a17dcb29/attachment.html>

More information about the OWASP-Leaders mailing list