JCPNEXT4-91: JCP 2.10 Implementation Checklist

[apastsya]

Jira issue originally created by user heathervc:

Create Checklist for Process Change JSRs; draft below.

1. Addition of definitions to the Process.
   2. Add Membership Levels - Full Member, Partner, Associate.
   3. Change Maintenance Process timing - flexibility in review times, length of ballot.
   4. Add section on Membership Fees.
   5. Add Contributors to JSR Expert Groups.
   6. Add language around voluntarily going Dormant, language around updates to milestones within a ballot period, intentions of SL around Maintenance.
   7. Add language around implementers being able to discuss TCK results.
   8. Modify JCP EC Elections process and add Community Seats and flexibility in timing.
   9. Add Evaluation Form for Process Change JSRs.
   10. Transition period for EC from JCP 2.9 to JCP 2.10.

[apastsya]

Attachments:

• JSR-364-checklist.txt

[apastsya]

Comment created by heathervc:

Updates to list based on Working Group discussion: Create Checklist for Process Change JSRs; draft below.

1. Addition of definitions to the Process.
   2. Add Membership Levels - Full Member, Partner, Associate.
   3. Change Maintenance Process timing - flexibility in review times, length of ballot.
   4. Add section on Membership Fees.
   5. Add Contributors to JSR Expert Groups.
   6. Add language around voluntarily going Dormant, language around updates to milestones within a ballot period, intentions of SL around Maintenance.
   7. Add language around implementers being able to discuss TCK results.
   8. Modify JCP EC Elections process and add Community Seats and flexibility in timing.
   9. Add Evaluation Form for Process Change JSRs.
   10. Transition period for EC from JCP 2.9 to JCP 2.10.

[apastsya]

Comment created by pcurran:

As we discussed at the Working Group meeting, this list need not include anything that is purely related to changes to the Process Document itself. We've reviewed that thoroughly, and it's now complete. Either its language reflects our intentions or we made a mistake and either omitted something or did not clearly state our intent. It is what it is.

The checklist should only include items that refer to the way in which we implement the Process rather than to the document itself. I therefore don't believe that we need to include the following items, at least as they are worded here:

4. Add section on Membership Fees.
5. Add language around voluntarily going Dormant, language around updates to milestones within a ballot period, intentions of SL around Maintenance.
6. Add language around implementers being able to discuss TCK results.

Items 4 and 6 could be reworded as follows:

• Eliminate membership fees
• Periodically remind Spec Leads of apparently inactive JSRs that they can voluntarily declare their JSR Dormant
• Do not accept changes to Spec later than 10 days prior to end of Public Review period and publish any revision at least 7 days prior to end of Review.
• At Final Release and Maintenance Release ask Spec Leads and Maintenance Leads whether they anticipate further changes through (additional) Maintenance Releases.

I can't see any reason to include item 7.

Further, for clarity, the first item should be reworded as:

1. Add Process definitions to JCP.org.

[apastsya]

Comment created by pcurran:

I've attached a draft checklist as a separate document (it will be easier to maintain and to use in this form).