My counter proposal (with implementation suggestions
in parenthesis that are simply suggestions) is
1) UNCHANGED
Core Contributors in a Community Group
A new [core] contributor in a collective is identified.
The community's voting process starts when an existing
core contributor in the community identifies a potential
new [C/CC] for that community and suggests a vote be
taken. The community votes on the nomination using
whatever voting mechanism is appropriate.
Assuming that the vote is positive...
2) The facilitator in that collective
DELETE:
Sends email to ogb-discuss to alert the OGB that a
successful vote for new C/CCs has occurred.
REPLACE WITH:
Interacts with the Core Contributor nominees to
ascertain their willingness to accept the status of
Member [OGB 2009/007].
Enters the appropriate data into their CG Electorates
in Auth.
(extra credit for having text fields where the
facilitator can copy/paste mail archive references
to the above discussions re: willingness and substantive
contributions)
The Auth web application notes that this Auth change
still needs OGB Secretary approval and adds the
item to the Secretary's work queue.
(The Auth app could generate a message (or a
daily digest or ...) for ogb-discuss that notifies the
OGB and the extended governance community of
these pending changes)
3) The OGB secretary
DELETE:
Checks that a valid vote has taken place in the
community and makes sure that any new CCs
have shown their willingness to accept the
status of Member [aka OGB 2009/007]
Puts the new names into poll/Auth.
REPLACE WITH:
Accesses the Auth web app and is presented
with a list of all pending C/CC grants, along
with a mechanism to
Approve an item,
Flag it as something that needs more attention, or
Deny it.
(The Auth app could generate a message (or a
daily digest or ...) for ogb-discuss that notifies the
OGB and the extended governance community of
any changes)
4) Automatic
UNCHANGED
The Auth application and the official poll database show this
person as a new C/CC.
