Request for vote to reduce inactive collaborator duration

votes/initiateNewVote/_EDIT_ME.yml

@@ -3,7 +3,7 @@
 
 # 1. Select a subject for the vote. This can be a question addressed to the TSC
 #    voting members.
-subject: REPLACEME
+subject: Reduce in-active collaborator duration
 
 # 2. You can leave the header instructions as is, or modify them if you see fit.
 headerInstructions: |
@@ -24,8 +24,8 @@ headerInstructions: |
 #    voters express their preference for each candidates, no matter how many
 #    there are.
 candidates:
-  - TODO
-  - TODO
+  - Status Quo: Keep the current in-active collaborator duration of 12 months
+  - Reduce the in-active collaborator duration to 9 months
 
 # 4. Pass the following to false if it's important to keep the candidates in the
 #    order you define above. Presenting candidates in a fixed order tends to
@@ -35,10 +35,25 @@ canShuffleCandidates: true
 # 5. Insert here a short description of the vote objectives and link to the
 #    issue it was discussed on to give the full context.
 footerInstructions: |
-  TBD
+  The objective of this vote is to reduce the in-active collaborator duration
+  from 12 months to 9 months. This vote was discussed in pull-request
+  https://github.com/nodejs/node/pull/52459 and the issue #1524.
+
 
 # 6. Optionally, insert a brief introduction for the vote PR, in the markdown format.
 prBody: |
+  Currently, Node.js collaborators are considered inactive if they have not
+  contributed to the project for 12 months. The definition of contribution in
+  the context of Node.js collaborators is any approval or review of a pull
+  request, or any commit to the Node.js repository.
+  The proposed reduction in the duration of inactivity for Node.js collaborators,
+  from 12 months to 9 months, is rooted in the principle of encouraging more
+  consistent and frequent engagement within the community. Node.js being a very
+  dynamic and fast-evolving project, it is vital to have regular input from
+  all active contributors. A three month reduction in the timeframe might seem
+  small, but this can provide a significant boost in the cycle of receiving
+  feedback. This vote is a crucial step in ensuring that the Node.js project
+  remains a vibrant and inclusive community.
 
 # 7. Optionally, choose an id that will be used for the branch name as well as
 #    the vote folder name. If not supplied, a UUID will be used.