33
44# 1. Select a subject for the vote. This can be a question addressed to the TSC
55# voting members.
6- subject : REPLACEME
6+ subject : Reduce in-active collaborator duration
77
88# 2. You can leave the header instructions as is, or modify them if you see fit.
99headerInstructions : |
@@ -24,8 +24,8 @@ headerInstructions: |
2424# voters express their preference for each candidates, no matter how many
2525# there are.
2626candidates :
27- - TODO
28- - TODO
27+ - Status Quo : Keep the current in-active collaborator duration of 12 months
28+ - Reduce the in-active collaborator duration to 9 months
2929
3030# 4. Pass the following to false if it's important to keep the candidates in the
3131# order you define above. Presenting candidates in a fixed order tends to
@@ -35,10 +35,18 @@ canShuffleCandidates: true
3535# 5. Insert here a short description of the vote objectives and link to the
3636# issue it was discussed on to give the full context.
3737footerInstructions : |
38- TBD
38+ The objective of this vote is to decide whether duration to determine
39+ inactivity of a from 12 months to 9 months. This vote was discussed
40+ in pull-request https://github.com/nodejs/node/pull/52459 and the issue #1524.
3941
4042# 6. Optionally, insert a brief introduction for the vote PR, in the markdown format.
4143prBody : |
44+ Currently, Node.js collaborators are considered inactive if they have not
45+ contributed to the project for 12 months. The definition of contribution in
46+ the context of Node.js collaborators is any approval or review of a pull
47+ request, or any commit to the Node.js repository. The proposed reduction
48+ in the duration of inactivity for Node.js collaborators, from 12 months
49+ to 9 months.
4250
4351# 7. Optionally, choose an id that will be used for the branch name as well as
4452# the vote folder name. If not supplied, a UUID will be used.
0 commit comments