You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
2
+
3
+
Below is our sponsorship guidelines to provide further clarification specific to our project for non-monetary contributions:
4
+
5
+
**Maintainers**
6
+
7
+
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.
8
+
9
+
**Contributors**
10
+
11
+
Contributors who earn 100 Sponsorship Points in a calendar year will qualify for sponsorship status. Sponsorship Points are available in the following forms.
12
+
13
+
For reporting a bug that is verified, the contributor will receive 10 point.
14
+
15
+
For merged pull requests, points will be awarded as follows:
16
+
17
+
1 - 10 lines = 1 Point
18
+
19
+
11 - 20 lines = 2 Points
20
+
21
+
21- 30 lines = 3 Points
22
+
23
+
Etc, etc
24
+
25
+
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 commit comments