Skip to content

Commit 664af2f

Browse files
committed
Add time limits to some stages of consensus process
1 parent 55dc587 commit 664af2f

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

CHARTER.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -105,6 +105,8 @@ The TSC has final authority over this project including:
105105
- Mediating technical conflicts
106106
- Mediating non-technical conflicts (until a formal Code of Conduct Committee is established)
107107

108+
In joining the TSC, members commit to communicate on a regular basis and respond to issues raised by the TSC in a timely manner. If they are no longer able or willing to make such a commitment, they should discuss this with the TSC or a TSC Chair.
109+
108110
### Section 4.1 Project Operations & Management (optional)
109111
<!-- https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391290 -->
110112

@@ -128,6 +130,8 @@ The Issue must:
128130
- Be labelled with 'tsc-decision'
129131
- Use the provided template, unless there is a good reason not to do so
130132

133+
At any point, any TSC member may notify the TSC that they are taking a period of leave and should be considered to abstain from any signalling or voting. The TSC member must detail when they expect to return.
134+
131135
##### Quick consensus process
132136

133137
In the event a TSC member feels the need for a decision to be expedited, they may create the decision discussion, indicating that they wish to use the quick process rather than the standard consensus process. This should be done by creating a new Issue in the TSC repository.
@@ -172,6 +176,8 @@ The opening comment of the Issue should be kept up to date as to the status of t
172176

173177
Transition between stages may be requested by anyone, but must be called by the facilitator (either a TSC chair or TSC member delegated the facilitator role for a given decision discussion). The stage will be indicated in the opening comment of the Issue and using the appropriate label.
174178

179+
Stages 1 and 6 are required to be open for at least 7 days or until every TSC member has confirmed they wish to progress to the next stage (Progression will still be "called", as above). This includes signals of abstaining given automatically via a notification of period of leave from TSC activity. For stage 2, any TSC member may request a 7 day extension to allow for further consideration. Should there be no reasonable objection (determined by a TSC Chair), the minimum time will be extended by 7 days. A TSC member may request multiple extensions, however lack of justification may result in the TSC member being asked to consider abstaining in stead. There are no other explicit time limits placed on the other stages of the process.
180+
175181
Most of the discussion should happen within the associated Discussion. The Issue should mostly be used to updated and report progress the consensus process. Groups looking to form a proposal or amend a proposal (stages 4 and 5) may make use of other additional Discussions or Issues, but these must be clearly linked. The opening comment should be updated to include links to relevant specific threads and comments in associated Discussion, and any other relevant locations.
176182

177183
Moving to the 'Form a Proposal" stage should be approached when the group might feel able to combine ideas to form a single proposal. Multiple possible solutions should be discussed in the previous stage.

0 commit comments

Comments
 (0)