[Owasp-board] [Owasp-leaders] Google Summer Of Code - limited places

Jason Li jason.li at owasp.org
Wed Apr 4 15:58:41 UTC 2012


Indeed - that's what I suggested in response to your original project
support email:

There's also a very fine line we're treading. Back in 2009, the Board made
> a decision to change the way we view funding for projects. Specifically,
> the Board decided that people should not be paid to do work on OWASP
> projects. That decision fundamentally changed how the GPC supports projects
> and is one of the reasons that OWASP has not had a "Season of Code" since
> 2008. We have been towing that party line - so if we're going to have
> interns working on projects, the Board is going to have to reconsider its
> policy decisions.
>
> I suggest that we take advantage of the Google Summer of Code effort and
> create a parallel program to grow potential project support. We will
> hopefully receive many many applicants and we know that Google will come
> back and tell us that was can only accept 4-8 of them. I suggest that we
> establish a funding pull to "match" Google so that we can accept an
> additional 4-8 applicants. Those applicants won't be official GSoC
> participants (i.e. GSoC t-shirt, recognized by Google, etc) but otherwise,
> the program would follow the same eligibility rules, timelines, mentorship
> guidelines, etc. (If approved, I will certainly reach out to Google and see
> if they're willing to include these "unofficial" participants as well in
> their promotional literature if we front the student stipend costs)
>
> There are project leaders who took the time and answered Fabio's request
> for project ideas and those projects are probably first in line for this
> supplemental program. And we should encourage project leaders to add to the
> list of ideas and convince students to apply.
>
> I think that this implementation would be a step in the right direction
> that:
> 1) Allows us to slowly step back into "funding" development of OWASP
> projects (should the Board decide that's a step they want to take)
> 2) Provides an established and proven "structure" for the funding
> 3) Lets us take advantage of some buzz around GSoC
> 4) Ensures that the projects that get "intern" help are the ones that are
> making effort and took the time to actually think about how they would use
> an intern
>
> First and foremost is a frank Board discussion on whether or not OWASP will
> shift it's earlier policies about paying people to do work on projects.
> Admittedly, it's a fine line with a delicate balance and should not be
> undertaken lightly. After all, we don't pay people to hold chapter meetings
> or run conferences so why should we be paying people to be working on
> projects? But there's definitely something to be said about growing
> projects.


http://lists.owasp.org/pipermail/owasp-board/2012-March/010792.html

-Jason

On Wed, Apr 4, 2012 at 11:46 AM, Eoin <eoin.keary at owasp.org> wrote:

> Hi,
> The owasp project reboot shall be able to cover some of these applications.
> There is overlap here I suspect??
> Eoin.
>
>
> Eoin Keary
> BCC Risk Advisory
> Owasp Global Board
> +353 87 977 2988
>
>
> On 4 Apr 2012, at 14:22, Fabio Cerullo <fcerullo at owasp.org> wrote:
>
> > All,
> >
> > Just to clarify a bit more Simon's mail below we received so far 22
> > proposals from students across the globe that are willing to
> > participate in different OWASP projects through Google Summer of Code.
> > As this is our first time participating in this programme, Google will
> > not be provide funding for all of them and probably only a few will be
> > accepted leaving several strong candidates outside this initiative.
> >
> > I believe Simon proposal is to "sponsor" some of these students by
> > using OWASP funds. However, I think it is still too early to know how
> > many student proposals will be accepted by Google. That decision will
> > be made at the end of April and until then we shouldn't be much
> > concerned about this. Once we know the final number of accepted
> > students, and those potentially left out, we could then discuss if
> > some OWASP funds could be allocated.
> >
> > I will keep you posted about the progress in the following weeks.
> >
> > Thanks,
> >
> > Fabio
> >
> > On Wed, Apr 4, 2012 at 1:45 PM, psiinon <psiinon at gmail.com> wrote:
> >> Hi folks,
> >>
> >> I know these is a separate GSoC list, but I really wanted to raise this
> on
> >> the leaders list.
> >> It looks like first time mentoring orgs only get at most 2 places,
> which is
> >> a real problem for orgs like OWASP with multiple products.
> >> A person on the GSoC mentors list mentioned that orgs could always add
> >> student places themselves, ie not part of GSoC but obviously inspired
> by it.
> >> Dont know about the other OWASP projects, but there have been a load of
> >> really strong proposals for ZAP.
> >> I'd hate not to get any of them, eg if OWASP was just allocated 1 place
> and
> >> that didnt go to ZAP.
> >> If we are very limited in the number of places, if there an potential
> for us
> >> to still employ some of the students, eg out of project or central
> funds?
> >> I realise there will be a load of complications, which is why I wanted
> to
> >> raise it on the leaders list.
> >>
> >> Cheers,
> >>
> >> Simon
> >> --
> >> OWASP ZAP: Toolsmith Tool of the Year 2011
> >>
> >>
> >> _______________________________________________
> >> OWASP-Leaders mailing list
> >> OWASP-Leaders at lists.owasp.org
> >> https://lists.owasp.org/mailman/listinfo/owasp-leaders
> >>
> > _______________________________________________
> > OWASP-Leaders mailing list
> > OWASP-Leaders at lists.owasp.org
> > https://lists.owasp.org/mailman/listinfo/owasp-leaders
> _______________________________________________
> OWASP-Leaders mailing list
> OWASP-Leaders at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/owasp-leaders
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-board/attachments/20120404/b8fb2103/attachment.html>


More information about the Owasp-board mailing list