You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 5, 2024. It is now read-only.
The Process document (version 2.10) refers to a JSR becoming Dormant for 2 reasons:
Section 3.2.2.5 (Relinquishing ownership) the Spec Lead or Maintenance lead discontinuing their work at any time, and either not locating a new Spec or Maintenance lead or the having the Transfer ballot fail. In this case, if a new Spec Lead steps up, a subsequent Transfer ballot is held.
Section 3.2.3 (JSR deadlines) Section 3.2.3 of the Process document states that the Spec Lead may voluntarily request that the JSR be declared Dormant (presumably due to the inability to progress the JSR to meet milestone deadlines), and that a JSR Renewal Ballot must be held in order for the Expert Group to resume activities at a later date.
In case 1), it seems reasonable that a successful Transfer ballot should be sufficient and that a renewal ballot (in addition) should not be required.
Jira issue originally created by user pcurran:
Should we require a Renewal Ballot when Dormant JSRs are revived?
The text was updated successfully, but these errors were encountered: