apastsya / jcpnext4

0 stars 0 forks source link

JCPNEXT4-1: Add a section in the Process Document for Membership #10

Closed apastsya closed 7 years ago

apastsya commented 10 years ago

Jira issue originally created by user heathervc:

Add a section in Part IV , or a sub-section in 'Section 1. General Procedures' of the Process Document to address Membershis Levela and Fees, to include all agreements that need to be signed and the membership rights of the Membership Levels.

apastsya commented 10 years ago

Comment created by pcurran:

See the document Membership Levelsfor proposed definitions of the new/revised membership levels.

Once we agree on this I'll draft actual text for the Definitions and body of the Process Document.

apastsya commented 10 years ago

Comment created by heathervc:

Also update the Participation overview on jcp.org: https://jcp.org/en/participation/overview As well as FAQ, SL Guide, etc https://jcp.org/en/introduction/faq https://jcp.org/en/resources/guide

apastsya commented 10 years ago

Comment created by pcurran:

During the May EC meeting it was suggested that in the section on Partner Members the wording "Individual JUG members must join as Affiliates if they wish to do more than act as Observers" should be clarified since the proposal specifies that Partner Members (in their role as as "organizational members") will have more rights than Observers.

apastsya commented 10 years ago

Comment created by pcurran:

During the May EC meeting it was also suggested that we should create a simple table t defining the different membership roles, specifying who qualifies for each, and listing the obligations and benefits that are incurred for each. Even if we don't include this table in the Process Document we could post it on JCP.org as a guide to potential members

apastsya commented 10 years ago

Comment created by heathervc:

John Weir has offered to create this table and has already produced a draft; we can discuss at the 20 May EG Meeting.

apastsya commented 10 years ago

Comment created by heathervc:

Added revised charts to the Downloads section of the JSR 364 wiki: https://java.net/projects/jcpnext4/pages/WorkingDocuments updated flow chart on June 12 2014.

apastsya commented 10 years ago

Comment created by pcurran:

Proposed fix

See the document Membership Levels Text for proposed additions to the Process Document.

apastsya commented 10 years ago

Comment created by pcurran:

Suggested text has been incorporated into version 1 of the revised Process Document.

apastsya commented 10 years ago

Comment created by heathervc:

We should consider the use case of a person employed by a corporate JCP Member who wants to participate as an Individual, not as a representative of the Full Corporate Member. Currently the workflow diagram does not allow for this, but we should consider a mechanism to allow this.

apastsya commented 10 years ago

Comment created by heathervc:

Werner brought up in the July EC meeting that we might want to restrict JUG primary representation (Partner Member). If primary Partner Member is employed by a Full JCP Member, they would not be allowed to serve in this capacity to serve on the EC?

apastsya commented 10 years ago

Comment created by heathervc:

Discuss how to continue to enable academic participation, based on additional research Heather completed in June 2014, at the July 15 2014 EG Meeting..

apastsya commented 10 years ago

Comment created by pcurran:

Heather commented:

"Werner brought up in the July EC meeting that we might want to restrict JUG primary representation (Partner Member). If primary Partner Member is employed by a Full JCP Member, they would not be allowed to serve in this capacity to serve on the EC?"

This is already fixed in the EDR version of the Process Document.

apastsya commented 10 years ago

Comment created by pcurran:

Heather has added another issue to this...

apastsya commented 10 years ago

Comment created by pcurran:

Opened new issues (54 and 55) to address Heather's recent comments. This issue can now be closed again.

apastsya commented 10 years ago

Comment created by jpampuch:

This issue (and many related) is addressed in section 3.1 in the EDR. This can be closed.

apastsya commented 10 years ago

Comment created by pcurran:

John Pampuch has verified that this issue is fixed.

apastsya commented 10 years ago

Issue was closed with resolution "Fixed"