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

Commit ec0f393

Browse files
apastsyaapastsya
committed
Initial commit
0 parents  commit ec0f393

File tree

297 files changed

+20577
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

297 files changed

+20577
-0
lines changed

‎README.md

+26
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
<table width="100%" border="0" cellspacing="0" cellpadding="0">
2+
<tr>
3+
<th><h2>Welcome to the JSR 348 (JCP.next) project</h2></th>
4+
<th><img src="./images/JCP-process-tiny.jpg" alt="Java Community Process" /> </th>
5+
</tr>
6+
</table>
7+
8+
This is the public project for [JSR 348: Towards a new version of the Java Community Process](http://jcp.org/en/jsr/detail?id=348),
9+
the first of three JSRs to modify the JCP's processes.
10+
11+
This JSR will focus on relatively simple changes that can be implemented quickly (we hope to finish before October 2011.)
12+
The second JSR - which will be filed soon - will focus on merging the two Executive Committees into one,
13+
while the third JSR will tackle more complex issues, including any necessary changes to the JSPA.
14+
15+
Since one of the main themes of JSR 348 is transparency, and since it will require that future JSRs be run in a transparent manner,
16+
the Expert Group has committed to running this JSR according to those requirements.
17+
18+
We will therefore discuss our business in public, publish all of our working materials and meeting minutes, and track issues in the open:
19+
20+
* To join the Observers' alias (to review and perhaps respond to Expert Group communications) go <a href="http://java.net/projects/jsr348/lists">here</a>. (You'll need a java.net login to subscribe.)
21+
* Visit the <a href="http://java.net/projects/jsr348/forums/General">discussion forum</a> to comment on the work of the Expert Group (we'd prefer that you use this rather than the Observer alias, to keep mail traffic down.)
22+
* For our meeting minutes and working documents, visit the <a href="http://java.net/projects/jsr348/pages/DocumentIndex">document archive</a>.
23+
* We use the <a href="http://java.net/jira/browse/JSR348">issue tracker</a> to record your comments and track issues.
24+
25+
![Java Community Process](./images/JSR-lifecycle.jpg)
26+

‎files/Meeting Materials/2011-06-01-Agenda.md

+24
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
# JSR 348 Expert Group Meeting
2+
1 June 2011
3+
4+
## Meeting details
5+
6+
* Date & Time
7+
* Wednesday June 1, 2011, 8:00 - 9:00 am Pacific time
8+
9+
* Teleconference logistics
10+
* +1 (866) 682-4770
11+
* Conference code: 627-9803
12+
* See email for the security code
13+
* For global access numbers see [http://www.intercall.com/oracle/access_numbers.htm](http://www.intercall.com/oracle/access_numbers.htm)
14+
* If those (free) numbers don't work, try +1 (408) 774-4073
15+
* WebEx[](https://jcp.webex.com/jcp/j.php?ED=144242297&UID=491098062&PW=NMDI4ZjE2NmQ4&RT=MiM0) logistics
16+
* [https://jcp.webex.com](https://jcp.webex.com/) (browse from here)
17+
* No registration required (enter your name and email address)
18+
* See email for password
19+
20+
## **Agenda**
21+
22+
* Review [minutes](/files/Meeting%20materials%20-%20pre%20Expert%20Group/2011-05-25-Minutes.md) from last week's meeting
23+
* Plan for submission of proposal for Expert Group's working style to full EG at June 7 EC meeting
24+
* Next steps

‎files/Meeting Materials/2011-06-01-Minutes.md

+67
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
# Minutes of JSR 348 Expert Group Meeting
2+
1 June 2011
3+
4+
## Meeting details
5+
6+
* Date & Time
7+
* Wednesday June 1, 2011, 8:00 - 9:00 am Pacific time
8+
9+
## **Agenda**
10+
11+
* Ballot results
12+
* Review [minutes](/files/Meeting%20materials%20-%20pre%20Expert%20Group/2011-05-25-Minutes.md) from last week's meeting
13+
* Plan for submission of proposal for Expert Group's working style to full EG at June 7 EC meeting
14+
* Next steps
15+
16+
## **Attendees**
17+
18+
* Patrick Curran
19+
* Mark Rogalski
20+
* Radomir Vencek
21+
* Alex Terazzas
22+
* Chris Wood
23+
* Calinel Pasteanu
24+
* Christoph Kuhmuench
25+
* Mike DeNicola
26+
* Werner Keil
27+
* Ben Evans
28+
* Heather Vancura
29+
* Scott Jameson
30+
* Sean Sheedy
31+
* Steve Wolfe
32+
* John Rizzo
33+
* Bruno Souza
34+
35+
## Minutes
36+
37+
_**Ballot Results**_
38+
39+
* SE/EE EC: 15 yes, 1 did not vote (Google)
40+
* ME EC: 11 yes, 5 did not vote (AT&T, Stefano Andreani, SK Telecom, Samsung, Vodafone)
41+
* See [http://jcp.org/en/jsr/results?id=5209](http://jcp.org/en/jsr/results?id=5209)
42+
43+
_**Review minutes from last meeting**_
44+
45+
Mike DeNicola confirmed that he will chair the Working Group. Meetings that are labeled (in advance) as Expert Group rather thanWG meetings will be chaired by Patrick.
46+
47+
We agreed that we'll probably need some additional f2f meetings of the WG. Patrick to poll for suitable dates.
48+
49+
Patrick to poll re moving back the date of the August EC meeting to allow time for public review .
50+
51+
_**Plans for EC meeting on June 7**_
52+
53+
Tighten up last week's minutes into a formal presentation/document for review and approval at June 7 EC meeting.
54+
55+
Review the JSR1 list for new members' benefits.
56+
57+
_**Next steps**_
58+
59+
Will Eduardo be the official maintainer/editor of our two documents?
60+
61+
How to proceed with editing the docs? Use the JSR1 list as a starting point. Assign people to draft language where necessary. Discuss and review proposed changes on the alias. Pass to the editor for inclusion. Review.
62+
63+
Rinse, repeat....
64+
65+
NOTE: we agree that will do work in between meetings, on the alias...
66+
67+
We agreed to meet at our usual time next Wednesday after the EC meeting on Tuesday. We will need Eduardo.

‎files/Meeting Materials/2011-06-07-Minutes.md

+48
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
# Minutes of JSR 348 Expert Group Meeting
2+
7 June 2011
3+
4+
## Meeting details
5+
6+
* This meeting was held as part of the June 7 Executive Committee meeting
7+
8+
## **Agenda**
9+
10+
* ([Presentation](http://java.net/projects/jsr348/downloads/download/Meeting%20Materials/JSR348-update-060711.pdf))
11+
* The JSR approval ballot
12+
* Working style
13+
* Transparency plan
14+
* Schedule
15+
16+
## **Attendees**
17+
18+
* See EC meeting minutes (link to be supplied)
19+
20+
## Minutes
21+
22+
### Inactive JSRs
23+
24+
In the context of a discussion on Inactive JSRs during the EC meeting Patrick Curran pointed out that this topic would be addressed in JCP.next. He reminded members that we propose to institute a series of _time-outs_ so that JSRs that did not reach Early Draft Review within one year, Public Review within two years, or complete within three years would be subject to a _JSR Reconsideration Ballot_ and potentially shut down. John Rizzo and Bruno Souza suggested that three years is too long, and that the required milestones be tighter. Ben Evans pointed out that whether or not a JSR was really inactive depends on the amount of engineering and development work that is actually taking place. He suggested that some JSRs (for example, JSR 292) that appear to be inactive might actually be working hard. Patrick responded that the solution to this problem is to issu an Early Draft Review. He pointed out that it's OK for an EG to issue multiple EDRs. Members responded that this isn't necessarily widely known, and suggested that this should be publicized. (This has been added to the [AI list](http://java.net/projects/jsr348/downloads/download/Working%20documents/AIs.md).)
25+
26+
John Rizzo argued that there should be a limit on the number of EDRs. Patrick responded that the requirement that a JSR reach the next stage (Public Review) within a specified period would ensure this.
27+
28+
Patrick reminded members that the requirements of the new Process Document would not apply to existing JSRs, implying that the existing cleanup process would need to be continued for quite some time.
29+
30+
### **JSR approval ballot**
31+
32+
Patrick reported the results of the JSR approval ballot. See the [presentation](http://java.net/projects/jsr348/downloads/download/Meeting%20Materials/JSR348-update-060711.pdf) for details.
33+
34+
### **Working style**
35+
36+
Patrick presented the Working Style proposals from the Working Group. John Rizzo suggested that since EC members are automatically members of the Expert Group, we should require them to acknowledge that they have read the minutes of the WG and have followed the discussion, so as to guard against the possibility of "surprises" when the JSR came to a formal vote. Scott Jameson and others expressed concern at this suggestion, pointing out that every member company has its own way of seeking internal feedback and approval, and that the Working Group could not second-guess or try to define how this process would work. After a lively discussion we agreed to move on, expressing the hope that all Expert Group members would follow the activities of the Working Group, and would raise any concerns early, so that there would be no surprises during formal votes.
37+
38+
Edin Bestevic asked whether Oracle would be exempt from the suggestion that members "disagree and commit" where they have problems with a particular proposal. Patrick responded that as with all JSRs, the Spec Lead could not be forced to implement something that they believe runs contrary to their business interests. Either a consensus is reached, or the Working Group disbands and the JSR fails to progress (as with the previous attempt to modify the JSPA and Process Document - JSR 306.)
39+
40+
The Expert Group then approved the Working Style as documented in the [presentation](http://java.net/projects/jsr348/downloads/download/Meeting%20Materials/JSR348-update-060711.pdf).
41+
42+
### **Transparency plan**
43+
44+
Patrick presented the Working Group's propsed Transparency Plan, as implemented in the [java.net project](http://java.net/projects/jsr348). Expert Group members approved the Transparency Plan as documented in the [presentation](http://java.net/projects/jsr348/downloads/download/Meeting%20Materials/JSR348-update-060711.pdf).
45+
46+
### **Schedule**
47+
48+
Patrick reviewed the schedule, pointing out the goal of completing before the October election. He noted that the schedule is very tight, and pointed out the need to modify the date of the August EC teleconference to align with the proposed schedule of reviews and ballots. Bruno Souza argued that if we miss the October deadline this wouldn't be a great problem.

‎files/Meeting Materials/2011-06-08-Agenda.md

+30
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
# JSR 348 Working Group Meeting
2+
8 June 2011
3+
4+
## Meeting details
5+
6+
* Date & Time
7+
* Wednesday June 8, 2011, 8:00 - 9:00 am Pacific time
8+
9+
* Teleconference logistics
10+
* +1 (866) 682-4770
11+
* Conference code: 627-9803
12+
* See email for the security code
13+
* For global access numbers see [http://www.intercall.com/oracle/access_numbers.htm](http://www.intercall.com/oracle/access_numbers.htm)
14+
* If those (free) numbers don't work, try +1 (408) 774-4073
15+
* WebEx[](https://jcp.webex.com/jcp/j.php?ED=144242297&UID=491098062&PW=NMDI4ZjE2NmQ4&RT=MiM0) logistics
16+
* [https://jcp.webex.com](https://jcp.webex.com/) (browse from here)
17+
* No registration required (enter your name and email address)
18+
* See email for password
19+
20+
## **Agenda**
21+
22+
* Review minutes from [last week](/files/Meeting%20Materials/2011-06-01-Minutes.md)'s and [yesterday](/files/Meeting%20Materials/2011-06-07-Minutes.md)'s meetings.
23+
* Review [Action Items](/files/Working%20documents/AIs.md)
24+
* WebEx and/or chat-room?
25+
* Status of 'observer' feedback.
26+
* Confirm our starting/working documents (listed [here](http://java.net/projects/jsr348/pages/WorkingDocuments))
27+
* How to conduct the reviews and updates.
28+
* Entire WG works on everything? Assign sections to individuals?
29+
* Review sections outside of meetings, then email proposals to WG?
30+
* Detailed schedule and milestones .

‎files/Meeting Materials/2011-06-08-Minutes.md

+82
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,82 @@
1+
# Minutes of JSR 348 Expert Group Meeting
2+
8 June 2011
3+
4+
## Meeting details
5+
6+
* Date & Time
7+
* Wednesday June 8, 2011, 8:00 - 9:00 am Pacific time
8+
9+
## **Agenda**
10+
11+
* Review minutes from [last week](/files/Meeting%20Materials/2011-06-01-Minutes.md)'s and [yesterday](/files/Meeting%20Materials/2011-06-07-Minutes.md)'s meetings.
12+
* Review [Action Items](/files/Working%20documents/AIs.md).
13+
* WebEx and/or chat-room?
14+
* Status of 'observer' feedback.
15+
* Confirm our starting/working documents (listed [here](http://java.net/projects/jsr348/pages/WorkingDocuments))
16+
* How to conduct the reviews and updates.
17+
* Entire WG works on everything? Assign sections to individuals?
18+
* Review sections outside of meetings, then email proposals to WG?
19+
* Detailed schedule and milestones.
20+
21+
## **Attendees**
22+
23+
* Patrick Curran
24+
* Alex Terazzas
25+
* Scott Jameson
26+
* Eduardo Gutentag
27+
* Mike DeNicola
28+
* John Weir
29+
30+
## Minutes
31+
32+
### How we will work - assigning tasks
33+
34+
Mike noted that we have very little time to create Early Drafts of the two docs: Process Doc, and Standing Rules. (We need to have these completed by the July 12 EC meeting.) We won't complete this work if we don't set ourselves targets, and if we don't do work between meetings.
35+
36+
Alex suggested: breaking up the documents so that different people can work on them simultaneously.
37+
38+
We updated the [JSR1 list](/files/Working%20documents/JSR1-list-June08.md), assigning a number and an owner to each proposed change. Before the next meeting owners will review their tasks and will email the Experts alias with suggested document changes or additions. For example:
39+
40+
> To: [email protected]
41+
> Subject: Suggested change for JSR1 list item 1.3.1 (change logs)
42+
>
43+
> Change lines 463-466 of JCP2 NEXT 2.9-Draft6-Clean.pdf to:
44+
>
45+
> **definition - Change Log**: An area accessible from the Spec Page that lists all changes made to the Specification, RI, TCK, and licenses since the previous release. There are six sections: PROPOSED (changes not yet made to the Specification), ACCEPTED (changes made to the Specification), DEFERRED (changes to be considered in a new JSR) and RI (changes made to the RI), TCK (changes made to the TCK) and LICENSING (changes to licensing terms.)
46+
47+
Eduardo will act as editor, incorporating the suggested changes after any discussion. However, he will be on vacation/traveling late in June and early in July, so someone else will need to take over the editor role during that period.
48+
49+
<span class="highlight">NOTE: The Process Document is currently structured to mirror the various JSR stages. This means that there's no logical place to put new requirements that aren't tied to a particular stage. In order to avoid duplication we agreed to add a **_General Procedures_ _(Section 0)_** at the beginning of the document for requirements that apply to all of the subsequently-described stages</span>
50+
51+
A couple of significant Cleanup tasks have been assigned to Eduardo (these are already completed?) but for other cleanup work we agreed not to explicitly assign. Instead, as people review the documents they should email the alias with any suggested cleanup tasks.
52+
53+
### Micro schedule before the next full meeting of the Expert Group (at the July EC meeting)
54+
55+
* June 15 First cut/feedback on each section from assignees
56+
* June 22 Refine/complete (Eduardo will have integrated suggestions)
57+
* June 29 Earl draft ready for review
58+
* July 6 Finish/polish EDR for submission to full EG at July 12 meeting
59+
* July 12 EC meeting
60+
61+
The goal for the Early Draft Review is to have restructured both documents with at least preliminary text for all suggested changes and additions. We will refine the actual words later.
62+
63+
### Availability of current attendees over the next month
64+
65+
* Alex: OK
66+
* John: OK (will be in Bangalore next week)
67+
* Scott will miss June 15 and June 22 meetings
68+
* Patrick: OK
69+
* Eduardo: will miss June 29, and possibly July 6
70+
* Mike: not available on June 22
71+
72+
Mike agreed to email the Experts alias requesting additional participation and encourage members to follow the discussion. He will also remind EC members that we are planning on operating completely transparently. This means that they will receive copies of all the messages suggesting and discussing proposed changes to the documents.
73+
74+
### WebEx and/or chat-room?
75+
76+
We agreed that since WebEx provides a built-in chat, and also a "raise hands" feature, we will stick with it for now. (But we will plan on using these features more.)
77+
78+
### Status of 'observer' feedback.
79+
80+
Patrick reported that so far we have no "external" observers since we haven't yet advertised that we're open for business. We will do so soon, and will continue to monitor the situation.
81+
82+
Update: 3:00 pm June 6\. We are now public (see [http://blogs.oracle.com/java/entry/jcp_next_update](http://blogs.oracle.com/java/entry/jcp_next_update)) and we have our first external observer.

‎files/Meeting Materials/2011-06-15-Agenda.md

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# JSR 348 Working Group Meeting
2+
15 June 2011
3+
4+
## Meeting details
5+
6+
* Date & Time
7+
* Wednesday June 8, 2011, 8:00 - 9:00 am Pacific time
8+
9+
* Teleconference logistics
10+
* +1 (866) 682-4770
11+
* Conference code: 627-9803
12+
* See email for the security code
13+
* For global access numbers see [http://www.intercall.com/oracle/access_numbers.htm](http://www.intercall.com/oracle/access_numbers.htm)
14+
* If those (free) numbers don't work, try +1 (408) 774-4073
15+
* WebEx[](https://jcp.webex.com/jcp/j.php?ED=144242297&UID=491098062&PW=NMDI4ZjE2NmQ4&RT=MiM0) logistics
16+
* [https://jcp.webex.com](https://jcp.webex.com/) (browse from here)
17+
* No registration required (enter your name and email address)
18+
* See email for password
19+
20+
## **Agenda**
21+
22+
* Review [minutes](/files/Meeting%20Materials/2011-06-08-Minutes.md) from last week's meeting.
23+
* Review [Action Items](#%20Status%20of%20alias%20problem.).
24+
* Status of alias problem.
25+
* Review suggested changes submitted to date.
26+
* See updated [JSR1 list](http://java.net/projects/jsr348/downloads/download/Working%20documents/JSR1-list-June14.md).
27+
* Review schedule and milestones .

0 commit comments

Comments
 (0)