[Owasp-leaders] Shall we fix projects together?

Liam Smit liam.smit at gmail.com
Thu Dec 17 22:22:52 UTC 2015

Hi Timo

As we discussed at the B-Sides Cape Town conference, a simple minimum
requirement for different types of projects may help a lot.

E.g. a documentation project needs to have at least some documentation
(RFC, outline, draft, etc) before it can be considered a project.
Similarly a software project would need some code (prototype, proof of
concept, etc) to qualify as a project.

If it's only an idea or a concept then it's pre-project. The way to
turn that into a project is to then write some code or documentation.

If there has been no update to a project for a year then that is stale
assuming that there is something workable / usable that exists because
if nothing exists after a year then it's unlikely to ever exist. It
should be possible to automate the generation of a report of such
stale projects which could then be reviewed and then either be
resuscitated, removed / archived or put in limbo status (pending
further review).


On Thu, Dec 17, 2015 at 9:43 AM, Timo Goosen <timo.goosen at owasp.org> wrote:
> There needs to be a greater focus on quality in projects. At the moment the
> board only cares about quantity and not about quality.
> Also we need incentive to attract good mature security related to become
> associated with OWASP.
> Also we need to get rid of outdated and unmaintained projects.
> Johanna and I tried to also make a minimum requirement for starting
> projects, but there still seems to be a trend of starting empty projects.
> I suggest the board members need to start doing project reviews, so that
> they have a good idea of the quality and quantity of projects at the moment.
> Regards.
> Timo
> On Wed, Dec 16, 2015 at 6:51 PM, Tom Brennan - OWASP <tomb at owasp.org> wrote:
>> What are your thoughts?
>> http://lists.owasp.org/pipermail/owasp-board/2015-December/016835.html
>> Tom Brennan
>> Global Board of Directors
>> NYC/NJ Metro Chapter Leader
>> 973-506-9304
>> --
>> The information contained in this message and any attachments may be
>> privileged, confidential, proprietary or otherwise protected from
>> disclosure. If you, the reader of this message, are not the intended
>> recipient, you are hereby notified that any dissemination, distribution,
>> copying or use of this message and any attachment is strictly prohibited.
>> If you have received this message in error, please notify the sender
>> immediately by replying to the message, permanently delete it from your
>> computer and destroy any printout.
>> _______________________________________________
>> 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

More information about the OWASP-Leaders mailing list