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

Konstantinos Papapanagiotou Konstantinos at owasp.org
Tue Feb 9 13:13:43 UTC 2016


Thank you Johanna for your input. Personally, I'd rather have OWASP
deciding slot policy and project participation rather than leaving that to
Google.

Kostas

On Tue, Feb 9, 2016 at 3:10 PM, johanna curiel curiel <
johanna.curiel at owasp.org> wrote:

> >>In the way that we run GSoC until today we have the capability to assign
> more slots to an active project if everyone agrees.
>
> Exactly, 'if' leaders agree.
>
> This is where the definition of 'active project' comes into place ;-)
>
> The rules under Gsoc define active project as:
> 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/>*. *
> https://developers.google.com/open-source/gsoc/faq
>
> BRL-CAD is a quite well developed and very active project :
> https://www.openhub.net/p/brlcad
> See Project activity icon is very high
>
> Similar project in OWASP is ZAP.: https://www.openhub.net/p/zaproxy
>
>
> Many LAB projects do not have the caliber of these ones. And a 'group'
> should be running the project, meaning developers dedicate to that project.
> OWASP could support the project as an Admin , since you can register up to
> 5 admins per submission per project.
>
> IMHO OWASP should apply as umbrella organisation and allow project leaders
> to apply individually.
> I don't think that a project with very low activity (see project activity
> under Openhub: http://blog.openhub.net/about-project-activity-icons/)
> would get a chance
> https://www.openhub.net/orgs/OWASP
>
> Gsoc has made this more explicit this year, so it becomes clear what kind
> of projects they expect to submit.
>
> Also, why not allow project leaders to decide what they want? Create a
> survey and submit a vote.
>
> Seen the past submissions and multiple discussions regarding slots, I
> think the best is to allow leaders decide if they submit individually and
> OWASP submits as an umbrella organisation.
>
> On Tue, Feb 9, 2016 at 8:34 AM, Konstantinos Papapanagiotou <
> Konstantinos at owasp.org> wrote:
>
>> I agree that all projects should have an Ideas page that should reflect
>> their roadmap and vision regardless if we participate in GSoC or not.
>> I don't believe that being an umbrella organization will result in
>> getting more slots overall. Each organization that falls under an umbrella
>> org usually gets 1-2 slots.
>> In the way that we run GSoC until today we have the capability to assign
>> more slots to an active project if everyone agrees.
>>
>> Kostas
>>
>> On Tue, Feb 9, 2016 at 2:06 PM, johanna curiel curiel <
>> johanna.curiel 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.
>>>
>>> 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/ca2034ae/attachment-0001.html>


More information about the OWASP-Leaders mailing list