JCP 2.8/2.9/2.10 checklist

The Specification Lead for each JCP 2.8/2.9/2.10 JSR should make the answers to the following questions available on the Community tab of the JSR, providing pointers where applicable..

• Is the schedule for the JSR publicly available, current, and updated regularly?
• Can the public read and/or write to a wiki for the JSR?
• Is there a publicly accessible discussion board for the JSR that you read and respond to regularly?
• Have you spoken at conferences and events about the JSR recently?
• Are you using open-source processes for the development of the RI and/or the TCK?
• What are the Terms of Use required to use the collaboration tools you have prepared to use with the Expert Group, so that prospective EG members can judge whether they are compatible with the JSPA?
• What is the location of your publicly-accessible Issue list? In order to enable EC members to judge whether Issues have been adequately addressed, the list must make a clear distinction between Issues that are still open, Issues that have been deferred, and those that are closed, and must indicate the reason for any change of state.
• What is the mechanism for the public to provide feedback on your JSR?
• Where is the publicly-accessible document archive for your Expert Group?
• Does the Community tab for my JSR have links to and information about all public communication mechanisms and sites for the development of my JSR?
• Do you have a Twitter account or other social networking feed which people can follow for updates on your JSR?
• Which specific areas of feedback should interested community members (such as the Adopt-a-JSR program) provide to improve the JSR (please also post this to your Community tab)?

JCP 2.7 checklist

The following constitutes a check-list for the Best Practices of JSR Transparency. Each JCP 2.7 JSR provides this checklist with each milestone posting; the answers are posted to the JSR's Update tab.

• The public can read the names of the people on the Expert Group (ie, not just JCP Members)
• The Expert Group business is regularly reported on a publicly readable alias.
• The schedule for the JSR is publicly available, it's current, and I update it regularly.
• The public can read/write to a wiki for my JSR.
• I have a discussion board for my JSR and I regularly read and respond to posts on that board.
• There is an issue-tracker for my JSR that the public can read.
• I have spoken at conferences and events about my JSR recently.
• I am using open-source processes for the development of the RI and/or TCK.
• The Community tab for my JSR has links to and information about all public communication mechanisms and sites for the development of my JSR.