[JCPNEXT4-13] The definition of Agent is too broad Created: 17/Oct/11  Updated: 29/Jul/14  Resolved: 25/Jun/14

Status: Closed
Project: jcpnext4
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: pcurran Assignee: pcurran
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


The Final Approval Ballot version of the Process Document contains the following definition of Agent:

"an individual - for example an employee, a contractor, or an officer - who is
authorized to act on behalf of a company or organization."

This should be modified to read "...who is authorized to act within the JCP on behalf of..."

Comment by heathervc [ 06/May/14 ]

Patrick will address as part of Issue #2 Definitions.

Comment by pcurran [ 23/Jun/14 ]

Proposed fix

We don't need this term any more. We should remove the definition of Agent and also the associated definition of Member Associate. (A modified definition for Member Representative will be sufficient.)

This will require additional changes:

Line 270: change "Any JCP Member, Member Representative, or Member Associate may request to join an Expert Group" with "Any Full Member or Member Representative may request to join an Expert Group".

Lines 278-9: change "together with the names of individual Member Representatives or Member Associates where appropriate" to "together with the names of individual Member Representatives where appropriate"

Note: the term Agent is also used on lines 275 and lines 728, but those sections should be modified when the new election processes are documented. At that point the term Agent should not be necessary and should be removed or replaced.

Comment by pcurran [ 25/Jun/14 ]

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

Comment by jpampuch [ 19/Jul/14 ]

The term "Agent" has been removed, so this issue can be closed.

Comment by pcurran [ 29/Jul/14 ]

John Pampuch has verified that this issue is fixed.

Generated at Sun Nov 29 02:59:25 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.