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

Maintenance Review proposed items #88

Open
heathervc opened this issue Sep 28, 2017 · 1 comment
Open

Maintenance Review proposed items #88

heathervc opened this issue Sep 28, 2017 · 1 comment

Comments

@heathervc
Copy link
Member

  • Add language that Spec Leads should use collaborative methods for RI development.
  • Add language that Spec Leads should provide access to the TCK to JSR Expert Group Members and Contributors for examination purposes only.
  • Add language that Spec Leads should specify Terms of Use for their JSR collaboration projects that comply with the JSPA.
  • Add language that allows redistribution of the Process Document.
  • Maintenance Lead specify at Maintenance Release whether future changes are expected.
  • Add language around transparency of MR in Maintenance Review process.
  • Ease the transition of a JSR from one Sped Lead to another.
  • Normalize review periods to days, and revised times for JSR Review Milestones - change to minimum of 15 days for EDR and PR (we have this minimum already for JSR Review and MR).
  • Allow EDR and PR times to start once PMO announces a link available.
  • Reduce EC ballots from 14 to 7 days, and reduce minimum times to provide updates to drafts for EC votes (PR and MR).
  • Correct reference to 'one or both Executive Committees'.
@heathervc
Copy link
Member Author

Based on feedback from the EC, we will normalize to 14 days for the minimum review periods (JSR Review, EDR, PR, MR) in the Maintenance Release.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant