apastsya / jcpnext4

0 stars 0 forks source link

JCPNEXT4-13: The definition of Agent is too broad #2

Closed apastsya closed 7 years ago

apastsya commented 13 years ago

Jira issue originally created by user pcurran:

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..."

apastsya commented 10 years ago

Comment created by heathervc:

Patrick will address as part of Issue #2 Definitions.

apastsya commented 10 years ago

Comment created by pcurran:

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.

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 jpampuch:

The term "Agent" has been removed, so this issue 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"