Skip to content

Commit a924f69

Browse files
mhdawsonmhdawson
committed
doc: first cut at sponsor agreements, and sponsor page documentation
Signed-off-by: Michael Dawson <[email protected]>
1 parent 8ef2f39 commit a924f69

7 files changed

+412
-0
lines changed

‎sponsorship/README.md

+126
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,126 @@
1+
# Sponsorship
2+
3+
The Node.js project needs a variety of sponsors in order to make the delivery
4+
of Node.js possible. Sponsors support the project through people time,
5+
infrastructure and monetary donations.
6+
7+
## Sponsor Recognition
8+
9+
The project aims to recognize sponsors who help keep the `lights on` by
10+
contributing in ways that support
11+
12+
* Releases
13+
* CI stability
14+
* Security
15+
* Infrastructure
16+
17+
In addition the project aims to recognize sponsors who make significant
18+
individual or organizational monetary donations which are not directed
19+
towards a specific purpose.
20+
The project has enabled crowd funding platforms and can also receive
21+
22+
funds through directed contributions to the OpenJS foundation and from
23+
OpenJS programs like the
24+
[Ecosystem Sustainability Program]
25+
26+
Sponsors who have made a contribution of 5000 us or more will be
27+
included in a rotating set of sponsors on the main Nodejs.org landing
28+
page with a visibility in proportion to the level of
29+
contribution that they have made.
30+
31+
All sponsorships are considered as being a calendar year sponsorship
32+
with the calendar year starting on the date the donation was made.
33+
34+
## Releases
35+
36+
Organizations or individuals who commit to do at least 4 releases per
37+
year are included in the `Releasers` section of the sponsor page on the
38+
Node.js website.
39+
40+
All of the logos shown in the `Releasers` section will be of the same
41+
general size.
42+
43+
If you are a releaser or an organization who employs a releaser
44+
See the [Releasers sponsor agreement](releasers_sponsor_agreement.md)
45+
for how to be included in the releasers supporters.
46+
47+
## CI stability
48+
49+
The project documented the need for a stability lead as part of
50+
enabling crowd funding accounts. Organizations or individuals
51+
that become supporters of 10000 US or higher towards the 60,000 US
52+
goal will be included in the `CI Stability Lead` section of the
53+
sponsors page.
54+
55+
Logos shown in the `CI Stability lead` section will be in proportion
56+
to the percentage of the taget sponsored. For example, if a single
57+
sponsor provides 60,000 US their logo will be the only one in that section.
58+
59+
If you have sponsored the CI stability lead either through
60+
the project's crowd funding accounts or through directed donation
61+
through the OpenJS foundation see the [CI stability lead sponsor agreement]()
62+
for how to be included in the CI stability lead sponsors.
63+
64+
## Security Lead
65+
66+
The project documented the need for a security lead as part of
67+
enabling crowd funding accounts. Organizations or individuals
68+
that become supporters of 20,000 US or higher towards the 300,000 US
69+
goal will be included in the `Security Lead` section of the
70+
sponsors page.
71+
72+
Logos shown in the `Security lead` section will be in proportion
73+
to the percentage of the taget sponsored. For example, if a single
74+
sponsor provides 300,000 US their logo will be the only one in that section.
75+
76+
If you have sponsored the `Security lead` either through
77+
the project's crowd funding accounts or through directed donation
78+
through the OpenJS foundation see the [Security lead sponsor agreement]()
79+
for how to be included in the Security lead sponsors.
80+
81+
## Security Triage
82+
83+
Organizations or individuals who have contributors to the project with the
84+
required trust and commit to cover least one slot in the
85+
security triage rotation are included in the `Security Triage` section of
86+
the sponsor page on the Node.js website. Each slot is 2 weeks long and
87+
a security triager's slot comes up every 2N weeks where N is the total
88+
nubmer of committed triagers.
89+
90+
All of the logos shown in the `Security Triage` section will be of the same
91+
general size.
92+
93+
If you are a triager or an organization who employs a triager
94+
See the [Security triager sponsor agreement](security_triager_sponsor_agreement.md)
95+
for how to be included in the security triage supporters.
96+
97+
## Security Stewards
98+
99+
Organizations or individuals who have contributors to the project with the
100+
required trust and commit to cover least one slot in the
101+
security steward rotation as documented in
102+
[Security Release Stewards](https://github.com/nodejs/node#security-release-stewards)
103+
are included in the `Security Stewards` section of
104+
the sponsor page on the Node.js website. Each slot in the rotation is
105+
for stewarding 1 security release.
106+
107+
All of the logos shown in the `Security Steward` section will be of the same
108+
general size.
109+
110+
If you are a security steward or an organization who employs a security steward
111+
See the [Security Steward sponsor agreement](security_steward_sponsor_agreement.md)
112+
for how to be included in the security steward supporters.
113+
114+
## General Supporters
115+
116+
Logos for organizations and individuals who have contributed at least $500 per year to the project through Open Collective or Open Collective will be shown on the supporters page. In addition a full link to the GitHub sponsors and open collective pages will be included in the sponsors page
117+
. A full list of supporters is available on our GitHub sponsors and Open Collective pages:
118+
119+
120+
## Supporters page template for Nodejs.org
121+
122+
The template will be as shown in
123+
[Nodejs.org Supporters page template](/nodejs_supporters_page_template.md).
124+
125+
126+

‎sponsorship/ci_stability_lead_sponsor_agreement.md

+41
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
# CI stability lead sponsor Agreement
2+
3+
The project documented the need for a stability lead as part of
4+
enabling crowd funding accounts. Organizations or individuals
5+
that become supporters of 10000 US or higher towards the 60,000 US
6+
goal will be included in the `CI Stability Lead` section of the
7+
sponsors page.
8+
9+
In order to be recognized ci stability lead sponsor sponsor, open an PR to add an entry
10+
in the [nodejs/admin/sponsors](https://github.com/nodejs/sponsors) directory titled
11+
`CI stability lead sponsor request - XXXX` where XXXX is the name of the organization
12+
or individual. In that issue include the following template:
13+
14+
## Organization Details
15+
16+
* Organization/Individual Name:
17+
* Organization/Individual Contact:
18+
* Sponsor visiblity level (0-1): (Will be agreed and set in co-operation with the project, based
19+
current sponsors). Used for rotating display on main Nodejs.org landing page.
20+
21+
## Comfirmation of committment
22+
23+
Include reference to contribution through OpenCollective or GitHub sponsors, or
24+
contact at OpenJS foundation that can confirm directed contribution.
25+
26+
## Logo details
27+
28+
* Link to logo to be included on sponsor page
29+
* Link to company website that can be linked to from logo
30+
31+
## Confirmation of use of Logo
32+
33+
* By submitting this issue I confirm that the Node.js project can
34+
use the logo provided and that I have obtained all required
35+
approvals from my organization for the Node.js project to use
36+
the logo submitted.
37+
38+
39+
40+
41+

‎sponsorship/nodejs_supporters_page_template.md

+69
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
# Supporters
2+
3+
The work of the Node.js project is driven forward by volunteers. Our preferred form of support
4+
from an organization is sending your people to contribute on a regular and consistent manner.
5+
6+
However, there is some supporting work within the project that is not the best fit for volunteers.
7+
For example, when vulnerabilities come with a disclosure deadline there is no guarrantee that
8+
a volunteers will have time to get the vulnerabilty fixed and out in a security release out in time.
9+
10+
In addition, the project needs non-people resources to continue operating. For example machines for
11+
the CI infrastructure. While the OpenJS Foundation covers some resources which are needed by the
12+
project it cannot cover all of them.
13+
14+
For cases were volunteers are not a great fit and for non-people resources we are grateful to the
15+
sponsors listed on their page for their support.
16+
17+
## Releasers
18+
Regular and timely releases are a key goal for the projectsc. Organizations and individuals that support
19+
the project by committing to do at least 4 releases per year include:
20+
21+
![LOGOS](https://github.com/user-attachments/assets/53f3fd31-160a-4307-8144-de30c9f963cf)
22+
23+
## CI stability lead
24+
25+
The project has been having ongoing issues with flaky tests and this has been a major pain point.
26+
The project, therefore, has a goal to hire a short term ci stability lead who can improve
27+
ci stability and implement tooling and processes that will provide longer term benefits. The following
28+
sponsors have made this possible:
29+
30+
![LOGOS](https://github.com/user-attachments/assets/53f3fd31-160a-4307-8144-de30c9f963cf)
31+
32+
## Security
33+
34+
Maintaining a good security posture and addressing vulnerabilities in a timely manner is a key goal
35+
for the project. We thank the following sponsors for their support in helping to do that.
36+
37+
### Security Lead
38+
39+
Organizations and individuals that support the project by funding our security lead for a mininmum of
40+
10000 US per year include:
41+
42+
[LOGOS]
43+
44+
### Security Triage
45+
Organizations and individuals who support the project by commiting at least one person to take a regular slot in our
46+
security triage rotation include:
47+
48+
![LOGOS](https://github.com/user-attachments/assets/53f3fd31-160a-4307-8144-de30c9f963cf)
49+
50+
### Security Steward
51+
Organizations and individuals that support the project by committing at least one person to
52+
take a regular slot in our security steward rotation include:
53+
54+
![LOGOS](https://github.com/user-attachments/assets/53f3fd31-160a-4307-8144-de30c9f963cf)
55+
56+
## Infrastructure
57+
Organizations and individuals that support the project by contributing at least $5000 of resources
58+
to the project per year include:
59+
60+
![LOGOS](https://github.com/user-attachments/assets/53f3fd31-160a-4307-8144-de30c9f963cf)
61+
62+
## General supporters
63+
64+
Organizations and individuals who have contributed at least $500 per year to the project. A
65+
full list of supporters is available on our GitHub sponsors and Open Collective pages:
66+
* https://github.com/sponsors/nodejs
67+
* https://opencollective.com/nodejs
68+
69+
![lager sponsors](https://github.com/user-attachments/assets/96539660-0578-4a77-97ea-92176bf1a737)

‎sponsorship/releasers_sponsor_agreement.md

+44
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
# Releasers Sponsor Agreement
2+
3+
Orgnizations or individuals who commit to do at least 4 releases per
4+
year are included in the `Releasers` section of the sponsor page on the
5+
Node.js website.
6+
7+
In order to be recognized as a releaser sponsor, open an PR to add an entry
8+
in the [nodejs/admin/sponsors](https://github.com/nodejs/sponsors) directory titled
9+
`Releasers sponsor request - XXXX` where XXXX is the name of the organization
10+
or individual. In that issue include the following template:
11+
12+
## Organization Details
13+
14+
* Organization/Individual Name:
15+
* Organization/Individual Contact:
16+
* Releasers Github handles:
17+
* Sponsor visiblity level (0-1): (Will be agreed and set in co-operation with the project, based
18+
current sponsors). Used for rotating display on main Nodejs.org landing page.
19+
20+
## Comfirmation of committment
21+
22+
By submitting this issue I confirm that:
23+
24+
* I have the ability to commit the named resources to doing releases
25+
* If this request is on behalf of an organization, I confirm that the
26+
releasers named have been allocated to do at least 4 releases per
27+
year.
28+
29+
## Logo details
30+
31+
* Link to logo to be included on sponsor page
32+
* Link to company website that can be linked to from logo
33+
34+
## Confirmation of use of Logo
35+
36+
* By submitting this issue I confirm that the Node.js project can
37+
use the logo provided and that I have obtained all required
38+
approvals from my organization for the Node.js project to use
39+
the logo submitted.
40+
41+
42+
43+
44+

‎sponsorship/security_lead_sponsor_agreement.md

+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
# CI stability lead sponsor Agreement
2+
3+
The project documented the need for a security lead as part of
4+
enabling crowd funding accounts. Organizations or individuals
5+
that become supporters of 20,000 US or higher towards the 300,000 US
6+
goal will be included in the `Security Lead` section of the
7+
sponsors page.
8+
9+
In order to be recognized as security release lead sponsor, open an PR to add an entry
10+
in the [nodejs/admin/sponsors](https://github.com/nodejs/sponsors) directory titled
11+
`Security release sponsor request - XXXX` where XXXX is the name of the organization
12+
or individual. In that issue include the following template:
13+
14+
## Organization Details
15+
16+
* Organization/Individual Name:
17+
* Organization/Individual Contact:
18+
* Sponsor visiblity level (0-1): (Will be agreed and set in co-operation with the project, based
19+
current sponsors). Used for rotating display on main Nodejs.org landing page.
20+
21+
## Comfirmation of committment
22+
23+
Include reference to contribution through OpenCollective or GitHub sponsors, or
24+
contact at OpenJS foundation that can confirm directed contribution.
25+
26+
## Logo details
27+
28+
* Link to logo to be included on sponsor page
29+
* Link to company website that can be linked to from logo
30+
31+
## Confirmation of use of Logo
32+
33+
* By submitting this issue I confirm that the Node.js project can
34+
use the logo provided and that I have obtained all required
35+
approvals from my organization for the Node.js project to use
36+
the logo submitted.

‎sponsorship/security_steward_sponsor_agreement.md

+49
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# Releasers Sponsor Agreement
2+
3+
Organizations or individuals who have contributors to the project with the
4+
required trust and commit to cover least one slot in the
5+
security steward rotation as documented in
6+
[Security Release Stewards](https://github.com/nodejs/node#security-release-stewards)
7+
are included in the `Security Stewards` section of
8+
the sponsor page on the Node.js website. Each slot in the rotation is
9+
for stewarding 1 security release.
10+
11+
In order to be recognized as a security steward sponsor, open an PR to add an entry
12+
in the [nodejs/admin/sponsors](https://github.com/nodejs/sponsors) directory titled
13+
`Security steward sponsor request - XXXX` where XXXX is the name of the organization
14+
or individual. In that issue include the following template:
15+
16+
## Organization Details
17+
18+
* Organization/Individual Name:
19+
* Organization/Individual Contact:
20+
* Security steward Github handles:
21+
* Sponsor visiblity level (0-1): (Will be agreed and set in co-operation with the project, based
22+
current sponsors). Used for rotating display on main Nodejs.org landing page.
23+
24+
## Comfirmation of committment
25+
26+
By submitting this issue I confirm that:
27+
28+
* I have the ability to commit the named security steward to covering a slot
29+
in the security steward rotation
30+
* If this request is on behalf of an organization, I confirm that the
31+
security stewards named have been allocated to cover at least one slot in the
32+
rotation.
33+
34+
## Logo details
35+
36+
* Link to logo to be included on sponsor page
37+
* Link to company website that can be linked to from logo
38+
39+
## Confirmation of use of Logo
40+
41+
* By submitting this issue I confirm that the Node.js project can
42+
use the logo provided and that I have obtained all required
43+
approvals from my organization for the Node.js project to use
44+
the logo submitted.
45+
46+
47+
48+
49+

0 commit comments

Comments
 (0)