Skip to content
This repository has been archived by the owner on Mar 5, 2024. It is now read-only.

JSR358-98: Require a renewal ballot when Dormant JSRs are revived? #69

Open
apastsya opened this issue Apr 12, 2016 · 1 comment
Open
Labels

Comments

@apastsya
Copy link
Member

Jira issue originally created by user pcurran:

Should we require a Renewal Ballot when Dormant JSRs are revived?

@apastsya
Copy link
Member Author

Comment created by ldemichiel:

The Process document (version 2.10) refers to a JSR becoming Dormant for 2 reasons:

  1. 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.

  2. 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.

@apastsya apastsya added the bug label Jun 22, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant