Skip to content
Permalink
Browse files

Create SPONSORING.md

  • Loading branch information...
devGregA committed Jul 8, 2018
1 parent 20464fc commit 0e37913f7c18332cd64dc7d2f1e3745ea8ae5903
Showing with 25 additions and 0 deletions.
  1. +25 −0 SPONSORING.md
@@ -0,0 +1,25 @@
On April 5th, 2018, OWASP clarified their sponsorship requirements to note that time, software, or any other quantifiable contribution can be counted towards the $1000 threshold outlined by the [OWASP Global Policy](https://www.owasp.org/index.php/Project_Sponsorship_Operational_Guidelines).

Below is our sponsorship guidelines to provide further clarification specific to our project for non-monetary contributions:

**Maintainers**

As a maintainer, you invest a significant number of hours reviewing code, contributing code, validating architecture, and helping the community. With the time you contribute, maintainers are entitled to name a sponsor, whether it be your employer or yourself, as long as you have written permission to have the entity’s logo displayed on the wiki and on our github repository. Should your relationship end with the entity you have designated (i.e. change of jobs) the entity will be grandfathered for calendar year at the time of your change.

**Contributors**

Contributors who earn 100 Sponsorship Points in a calendar year will qualify for sponsorship status. Sponsorship Points are available in the following forms.

For reporting a bug that is verified, the contributor will receive 10 point.

For merged pull requests, points will be awarded as follows:

1 - 10 lines = 1 Point

11 - 20 lines = 2 Points

21- 30 lines = 3 Points

Etc, etc

Issues will also be labeled with points. When a fix is merged, the contributor will receive the corresponding points, and the points associated with the line rewards above.

0 comments on commit 0e37913

Please sign in to comment.
You can’t perform that action at this time.