-
-
Notifications
You must be signed in to change notification settings - Fork 140
doc: use of OpenCollective and GitHub sponsors #1658
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 5 commits
21cd6bb
812a2c8
1b7def6
a4934c0
0a38db1
e9daced
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,34 @@ | ||
| # Node.js GitHub sponsors | ||
|
|
||
| The project has enabled GitHub sponsors in order to to accept | ||
| sponsorships. Currently there is only a single one time tier which is | ||
| called "sponsor" and one monthly tier which is called "monthly-sponsor" | ||
| with no specific rewards. | ||
|
|
||
| The funds are to be used for specific efforts as decided by the TSC and | ||
| documented on this page. | ||
|
|
||
| ## Account details | ||
|
|
||
| The account is manged by the TSC. The user id and password | ||
| are shared with TSC members through 1password. All payments for | ||
| sponsorships received will be made to the OpenJS Foundation who has | ||
| agreed to manage the funds that are received on behalf of the project. | ||
|
|
||
| ## Disbursements - management | ||
|
|
||
| Potential disbursements will be agreed through TSC discussion | ||
| and before approval, documented in a PR in the | ||
| [TSC repository](https://github.com/nodejs/TSC) which adds | ||
| the intended use and funding envelope to this page. The disbursement | ||
| is considered approved once TSC consensus in the PR has | ||
| been reached. | ||
mhdawson marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| When work is complete for an approved disbursement, a request will be | ||
| made by the TSC to the OpenJS foundation to pay the person chosen by | ||
| the TSC to do the work. | ||
|
|
||
| ## Disbursements approved | ||
|
|
||
| | Intended use | funding envelope | paid | | ||
| |------------------------------------------|--------------------|--------------| | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,36 @@ | ||
| # Node.js Open Collective | ||
|
|
||
| The project maintains an Open Collective that is used to accept donations. | ||
|
|
||
| The funds are to be used for specific efforts as decided by the TSC and | ||
| documented on this page. | ||
|
|
||
| ## Account details | ||
|
|
||
| The account is manged by the TSC. The user id and password | ||
| are shared with TSC members through 1password. | ||
|
|
||
| ## Disbursements - management | ||
|
|
||
| Potential disbursements will be agreed through TSC discussion | ||
| and before approval, documented in an PR in the | ||
| [TSC repository](https://github.com/nodejs/TSC) which adds | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should it be the admin repo?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We already have the similar doc for the bug bounty fund in the TSC repo so I've added them here to be consistent. Havingf said that I don't have a strong feeling one way or the other.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don’t know how consistent we are with this, my understanding is that nodejs/TSC would be for stuff internal to the TSC, so folks who are not TSC members can safely unsubscribe from that repo without missing any info relevant to them. |
||
| the intended use and funding envelope to this page. The disbursement | ||
| is considered approved if there's no objections from a project member | ||
| in 72 hours, and consensus has been reached in the TSC. Objections can be | ||
| overridden with a TSC vote. | ||
|
|
||
| Once work has been completed the recipient will open | ||
| a request through open collective in the amout approved. | ||
|
|
||
| The Chair of the Technical Steering committee will then | ||
| "push the required buttons" in the Open collective account | ||
| to initiate the payout in accordance with the agreement reached in the | ||
| TSC PR and if possible include a reference to the PR | ||
| in the TSC repository adding the intended use and funding | ||
| envelope to this page. | ||
|
|
||
| ## Disbursements approved | ||
|
|
||
| | Intended use | funding envelop | paid | | ||
| |------------------------------------------|-------------------|--------------| | ||
Uh oh!
There was an error while loading. Please reload this page.