[Owasp-board] Empty and incomplete projects again

johanna curiel curiel johanna.curiel at owasp.org
Wed Nov 4 23:15:45 UTC 2015

Hi Claudia

I think it motivates a leader to 'obtain and earn' a wiki project page at
owasp  when they have to work and deliver some content
Right now these projects are empty and now your work is to be behind these
leaders so they can produce content?

The conditions were clear: Produce a content then you can obtain and setup
a wiki page. Minimum requirement is at least a plan called 'Table of
Contents', that is not hard to do and at least the leaders has shown he has
think of a plan.

All new projects that were started before you joined owasp , when we
defined these rules, were done like this and it worked. Wether leaders
invest the energy and 'earn' a wiki project space and are able to announce
they have a project or never is announced.

This rule was implemented to avoid 'phoney' projects.

I don't know WHY has been decides to change the rules (but on the website
are still the old ones)

Again If we made rules for a very good reason, why are they broken now and
not clearly communicated?  My advice is, communicate with the Project
leaders on then mailing list or the slack, create a survey and see how
people feel about this.

Again, WHY has been this changed and how this benefits owaps image? Please
think about this.



On Wed, Nov 4, 2015 at 6:47 PM, Claudia Casanovas <
claudia.aviles-casanovas at owasp.org> wrote:

> Hi Johanna,
> These two project leaders are working on their completion and I will
> ensure both are completed. They currently marked as In Process for the
> Project Task Force.
> https://www.owasp.org/index.php/OWASP_Security_Ninja_Program_Project -
> Wiki Page will be Deleted as Project Leader has a new name https://www.
> owasp.org/index.php/OWASP_Security_Ninja_Project
> Page will be deleted (as this was only a name change instance) once the
> Project Leader adds the completed information.
> This particular project is taking over the work from on Secure
> Development Training Project which is in process of shutting down on which
> Tobias is the Project Leader and Chris Romeo will be taking over the
> project but with a new name and new added content.  The Secure Development
> Training Project is not yet merged as Chris Romeo is working on the content
> on the new wiki page.
> David Shaw is working on the content and has been in contact with me this
> week.
> https://www.owasp.org/index.php/OWASP_API_Security_Project
> I agree on your concern and will be diligently working with the Project
> Leaders to ensure completion this week.
> On Wed, Nov 4, 2015 at 2:18 PM, johanna curiel curiel <
> johanna.curiel at owasp.org> wrote:
>> Hi Project Task Force, and members of the Board
>> A while ago I noticed that people have decide to change the rules and
>> allow empty projects , what that means is that there is nothing produced
>> (not even a table of contents) and wiki pages are being setup as 'projects,
>> even worse, templates with no content
>> I feel quite disappointed to see this, especially after the amount of
>> work I and other volunteers with some staff took to clean up the 'empty
>> projects'
>> These projects have no content delivered as mentioned on the conditions
>> for starting a project
>> https://www.owasp.org/index.php/OWASP_Security_Ninja_Program_Project
>> https://www.owasp.org/index.php/OWASP_API_Security_Project
>> Again, what is the benefit of changing the rules and allow this again?
>> For documentation :(still is mentioned on the website)
>> https://www.owasp.org/index.php/Category:OWASP_Project#tab=Starting_a_New_Project
>>    1. Project Name,
>>    2. Project purpose / overview,
>>    3. Project Roadmap,
>>    4. Project links (if any) to external sites,
>>    5. [[Guidelines_for_OWASP_Projects#Project_Licensing|Project
>>    License],]
>>    6. Project Leader name,
>>    7. Project Leader email address,
>>    8. Project Leader wiki account - the username (you'll need this to
>>    edit the wiki),
>>    9. Project Contributor(s) (if any) - name email and wiki account (if
>>    any),
>>    10. Project Main Links (if any).
>>    11. For Documentation: A table of Contents
>>    12. For Code: A prototype hosted in an open source repository of your
>>    choice. Make sure it has read access
>> regards
>> Johanna
> --
> Claudia Aviles-Casanovas <claudia.aviles-casanovas at owasp.org>
> Project Coordinator
> Phone:973-288-1697
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-board/attachments/20151104/e901580b/attachment-0001.html>

More information about the Owasp-board mailing list