[Owasp-leaders] Proposing new guidelines to start code/tool projects

Josh Sokol josh.sokol at owasp.org
Thu Aug 21 21:14:46 UTC 2014

I like the idea.  One thing to keep in mind though is that this may force
us to change the definition of an "incubator" project as the current
definition gives a project leader in this stage one year to produce a draft
or development release (
The problem is that while we say we're going to go back and remove the ones
who don't accomplish this, I'm not sure if we ever really have done that in
the past and so they linger on and on...


On Thu, Aug 21, 2014 at 12:30 PM, johanna curiel curiel <
johanna.curiel at owasp.org> wrote:

> Leaders
> After reviewing the entire list of code and tool projects , from incubator
> to labs and flagship I have observed a main issue: Many projects start
> without a single line of code, a binary or executable version of a program.
> This really creates an 'empty' list of projects(more than 50 projects were
> empty) that never launched or released a single line of code.
> At OWASP we don't have an army of volunteers or paid staff to keep up
> monitoring and maintain this, therefore I'm proposing a new guideline to
> solve this issue. Anyone who wishes to start a project(tool/code) must have
> at least:
> -An open source repository
> -At least some code written
> The bar is low to allow development, but I think that any code/tool
> project must have at least this in order to be consider incubator.
> Let me know your thoughts and we can add this to the guidelines
> Regards
> Johanna
> _______________________________________________
> 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-leaders/attachments/20140821/f0bd1c24/attachment.html>

More information about the OWASP-Leaders mailing list