[Owasp-leaders] Proposing new guidelines to start code/tool projects
johanna curiel curiel
johanna.curiel at owasp.org
Tue Aug 26 16:42:37 UTC 2014
Helping to extend an existing project is often much easier and more useful
than starting a completely new one...
Yes, we need to unify forces serving the same purpose, it makes it easier
We need to review carefully the submission of new projects so we can guide
new potential project leaders into exisiting projects and they should take
the time to verify if they revive an inactive one, join forces with
existing one or starting a new one, especially document projects seem to
suffer more of this issue(many treating the same subject almost
identically) than tools or code projects
On Tuesday, August 26, 2014, psiinon <psiinon at gmail.com> wrote:
> I'm in favor of this as well.
> A slightly related point - in this industry we do seem to suffer a lot
> from NIH (Not Invented Here, for non native English speakers).
> When someone proposes a new project can we ask them to check that there
> isnt already a related OWASP project?
> Helping to extend an existing project is often much easier and more useful
> than starting a completely new one...
> On Mon, Aug 25, 2014 at 8:07 AM, Munir Njiru <munir.njiru at owasp.org
>> I totally agree with that idea
>> On Thu, Aug 21, 2014 at 8:30 PM, johanna curiel curiel <
>> johanna.curiel at owasp.org
>>> 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
>>> 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
>>> OWASP-Leaders mailing list
>>> OWASP-Leaders at lists.owasp.org
>> Munir Njenga,
>> OWASP Chapter Leader (Kenya) || Information Security Consultant ||
>> Mob (KE) +254 (0) 734960670
>> Chapter Page: www.owasp.org/index.php/Kenya
>> Email: munir.njiru at owasp.org
>> Facebook: https://www.facebook.com/OWASP.Kenya
>> Mailing List: https://lists.owasp.org/mailman/listinfo/owasp-Kenya
>> OWASP-Leaders mailing list
>> OWASP-Leaders at lists.owasp.org
> OWASP ZAP <https://www.owasp.org/index.php/ZAP> Project leader
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OWASP-Leaders