[Owasp-leaders] Google summer of code applications and chances to be selected

johanna curiel curiel johanna.curiel at owasp.org
Tue Feb 9 12:06:30 UTC 2016

>>We could always apply as an umbrella org but we haven't done so since it
would create an administrative overhead for project leaders.

It depends how you see it.

IMHO, A well organised project as ZAP can do it individually and will have
less hassle to share and go through the 'slot' discussion.
As you know, Google provides limited slots and this has always has been a
source of discussions among project leaders of which projects and how many
slots should each project get

I think that if projects self-organise making their own submissions, then
there will be no discussions how many slots will be divided between the
projects if OWASP gets selected as organisation. If that project gets
selected, then he will manage the program itself, as much of the works is
set on mentors.

Also, having a good project idea page per project will allow that project
has better chances to be selected by Google.

On Tue, Feb 9, 2016 at 8:00 AM, Konstantinos Papapanagiotou <
Konstantinos at owasp.org> wrote:

> We could always apply as an umbrella org but we haven't done so since it
> would create an administrative overhead for project leaders. I agree that
> there are advantages but I don't think we are that big of an organization.
> By the way we are already working with Claudia on the application.
> Kostas
> On Tuesday, 9 February 2016, johanna curiel curiel <
> johanna.curiel at owasp.org> wrote:
>> It seems that in order to apply a submission to Gsoc, you dont need to
>> do It under owasp, but project based . You can define that you fall under
>> owasp as organization umbrella.
>> An organisation under gsoc does not have to be an existing org registered
>> but an open source project acting as a mentoring organisation
>> https://developers.google.com/open-source/gsoc/faq
>> What are the eligibility requirements for a mentoring organisation? To
>> be eligible to participate as a mentoring organization, you must be a group
>> running an active free/open source software project, e.g. BRL-CAD
>> <http://brlcad.org/>*. The project does not need to be a legally
>> incorporated entity. Mentoring organizations *must have *already* produced
>> and released software under an Open Source Initiative approved license
>> <http://www.opensource.org/licenses> and have at least two contributors
>> to serve as organization administrators and/or mentors for the entire
>> program in order to participate in the program.
>> In addition, if owasp wants to have more chances to be selected, it needs
>> to work with enough anticipation on the project ideas page and at
>> recruiting students all year long before even the deadline is announced
>> As an individual project, you as project leader can do so.
>> http://en.flossmanuals.net/GSoCMentoring/defining-a-project/
>> Your goal for GSoC is to generate a list of project ideas that capture
>> the development needs of your organization, attract the interest of
>> students, and help you get things done. This is often done as a community
>> effort that involves as many potential mentors as possible, helps create
>> buy-in from these mentors, and gives a broad range of perspectives on
>> organizational needs.* Creating your list of project ideas should also
>> be part of an ongoing long-term strategy, rather than a rushed act to meet
>> the application deadline. Many organizations maintain such project lists
>> year-round*.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-leaders/attachments/20160209/8d4467e1/attachment.html>

More information about the OWASP-Leaders mailing list