Project Committee
To provide the support and guidance required by Projects to thrive and contribute to the overall mission and goals of OWASP.
Good OWASP Projects...
Uniqueness
...are submitted as Incubator projects after checking for (and considering to contribute to) a possibily existing similar OWASP project instead.
...have a unique selling point (USP) or vision that sets them apart from possibly existing similar OWASP projects.
Vendor Neutrality
...avoid names that are easily confused with existing organizations or their (commercial) services.
...are truly free and Open Source and do not hide certain features behind any kind of paywall.
...adhere to the "Recognizing Supporters" section of the Donations Policy when referring to supporting individuals or organizations.
...have their own social media presence (e.g. Twitter handle, YouTube channel) and do not "piggy-back" on ones used for commercial purposes.
...have multiple Project Leaders who are not all employed by the same company.
Community Support
...have a channel on the official OWASP Slack optimally named
#project-<name>for easy filtering.
GitHub
...live under the https://github.com/OWASP GitHub organization and not in private GitHub accounts.
...can alternatively have a dedicated GitHub organization if they consist of multiple repositories.
...respond to GitHub issues and pull requests in a timely and friendly manner.
...have all Project Leaders as administrators on their GitHub repository (especially when it lives outside of https://github.com/OWASP).
Website
...keep their landing page on owasp.org up to date (especially regarding release information and project roadmap).
...clearly state they are an OWASP project and link to their OWASP project page from any website they maintain.
Project Information
Slack