2009 09 24 OGB Agenda

From Genunix

Jump to: navigation, search
OpenSolaris Governing Board Conference call details (Admin)
US: USA 866-692-3163 Participant: 2830169#
UK: 0808-238-6025
Sun Extention: x44414
Previous Meeting Agenda for Thursday, September 24, 2009, 9am - 10:30am PDT Next Meeting

Contents

Procedural

  1. Last week's meeting canceled due to problems with dialin.
  2. Attendance - apologies from Michelle, Simon
  3. Calendar items?
  4. AI Review
    • Valerie: send mail with writeup of in memoriam web page for site and process for adding to it
    • Michelle to update draft constitution calendar in light of weekly meetings
    • Simon/John to put draft constitution on co-ment.com - DONE http://www.co-ment.net/text/1506/
    • Michelle to send 1-pager to Bonnie's team for polling UI
    • Michelle to post new draft of project instantiation
    • DS Contributer grants: On Hold until notice from Bonnie about database work complete
    • DS Contributer grants (bugs need to be be filed for all of these)
      • Documentation: michelle (core contributor)
      • Storage: CC grants: jforte??
      • LDoms (bug 11088)
      • SysAdmin (bug 11089)
      • Printing (bug 11199)
      • HPC (bug 11200)

Business

who what
Plocher/JimG/Valerie

Motion: That the Board consider the following proposals re: facilitator/secretary/auth interactions and vote on the following:

The OpenSolaris Community Contributor/CoreContributor promotion process shall be modified as described in

A) None - keep the status quo
[Even keeping the status-quo requires changes to Auth to give the OGB Secretary (and his/her designees) the ability to make these changes.]
1) 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
Sends email to ogb-discuss to alert the OGB that a successful vote for new C/CCs has occurred.
3) The OGB Secretary
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).
The Secretary puts the new name into poll/Auth.
4) Automatic
The Auth application and the official poll database show this person as a new C/CC.
B) Jim's proposal
A simple process could be the following: CG Facilitators post to ogb-discuss their grant changes, the OGB secretary responds with whatever OGB approval process is in place, then the CG Facilitators enter the appropriate data into their CG Electorates in Auth. The threads on ogb-discuss will serve as an open record of the board's approval, and the public relationships screens on Auth will serve as confirmation the data was entered correctly.
[This proposal requires changes to Auth to give facilitators the ability to make these changes.]
----
3) The OGB Secretary
DELETE:
puts the new name into poll/Auth.
ADD:
responds with an "approval email" to OGB-Discuss stating that the OGB's processes have been successfully followed.
The Facilitator in a collective goes into Auth, and for each candidate in their collective who has been "approved", modifies their official database entry to show the promotion
----
C) John's proposal [WITHDRAWN]
Leverage the Auth app's database to enable an automated two-approval workflow, where facilitators "present" new candidates and the OGB Secretary does the required due-diligence and "approves" them.
[This proposal requires changes to Auth to implement the 2-approval workflow and to record the supporting documentation.]
----
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 any Core Contributor nominees to ascertain their willingness to accept the status of Member [OGB 2009/007].
- Enters the promotion and supporting documentation into their collective's Electorate section in Auth.
- [The Auth web application notes internally that this Auth change still needs OGB Secretary approval and adds the item to the Secretary's work queue.]
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 and supporting documentation, along with a mechanism to:
Approve a grant,
Flag it as needing more attention, or
Deny it.
----
D) Peter: A "nominated" list of people who have write access to the Auth DB, starting with the board secretary and growing as appointed to backups and facilitators as they get trained/show expertise. Maybe this grows into a membership committee.
[Even keeping the status-quo requires changes to Auth to give the OGB Secretary (and his/her designees) the ability to make these changes.]
1) 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
Sends email to ogb-discuss to alert the OGB that a successful vote for new C/CCs has occurred.
----
DELETE
3) The OGB Secretary
ADD
3) The OGB Secretary or one of a "nominated" list of people
----
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).
The Secretary puts the new name into poll/Auth.
4) Automatic
The Auth application and the official poll database show this person as a new C/CC.
Plocher Opening Constitution up to public comments
All Constitutional discussion

Current Items

Suggestion Box Review == OGB 2009-2010 Suggestion Box ==

This OGB Suggestion Box wiki is available to any OpenSolaris user that has suggestions, ideas, concerns or solutions that they would like the OGB to consider. Please use the following procedure to enter your suggestions or solutions:

  • Indicate status (Unreviewed initially)
Unreviewed OGB Reviewing Action Taken Reviewed Review Again
  • Increment suggestion number
  • Enter Date
  • Enter Submitter name or OpenSolaris username or anonymous
  • Enter Suggestion
  • Comments field can be used to comment on a suggestion and indicate what related actions were taken


Status Number Date Submitter Suggestion Comments
Action Taken 1 4 May 2009 John Plocher To make voting easier, replace the ssh based poll.os.o election system with a web based one that keys off of the member's os.o login auth info. Need to involve sch and tonic team, need to articulate needs/requirements, request consultation. MO to procure a "request template", JP to fill out. Done, website team working on UI, JW tracking.
Action Taken 2 6 May 2009 James Carlson Since the distinction between Core and non-Core Contributor is voting, you could make it a use-it-or-lose it franchise; those not voting in (say) 2 or more consecutive elections become Contributors, and need to be re-nominated for Core Contributorship. No ability to do this in the current constitution. JP Added to "new constitution" feedback.
OGB Reviewing 3 9 May 2009 Peter Tribble Need a mechanism to alert members and facilitators when membership grants are due to expire. People shouldn't have to manually poll. JP to look into y!Pipe stuff to highlight, ??? to look into how to do more active alerts, maybe use facilitators project and monthly report of new/expiring/expired grants, maybe automate in cron?
Action Taken 4 14 May 2009 Mail Man Admins/mods should moderate their mail queues and read the manual for list operation. List users should read the manual, too, and either subscribe to the lists or take the issue up with the list owners instead of wasting time with cyclical rants about how lists persecute the little people. World peace would be nice as well. JW provided a list of email list best practice areas to the website community, MO to add to website community FAQ
Action Taken 5 12 June 2009 Garrett D'Amore Should have an in memoriam page and status to recognize contributors who have passed. Complete, see http://hub.opensolaris.org/bin/view/Community+Group+ogb/In+Memoriam
Unreviewed ... add new suggestions here...

OGB_future_agenda_items

Any OpenSolaris Member may submit items for a future OGB agenda by adding the item to this OGB future agenda items wiki page. OGB Members or the OGB Secretary may add any item on this list to the agenda for the next meeting if they believe those items to be sufficiently mature.
"Sufficiently mature" items will:
  • have been socialised among the OGB,
  • have an OGB "sponsor"
  • have a motion or discussion brief prepared on a wiki page, together with a summary of the discussion to date,
  • be ready for a discussion likely to lead to significant progress or a definitive decision at the OGB meeting.
Date Added Who What
10 June, 2009 Plocher/Simon Charter update, preamble draft, next draft constitution iteration Talk:OGB_2008/010_OpenSolaris_Constitution_2009
10 June, 2009 Plocher Need a mechanism to alert members and facilitators when membership grants are due to expire. People shouldn't have to manually poll. Look into y!Pipe stuff to highlight, how to do more active alerts, maybe use facilitators project and monthly report of new/expiring/expired grants, maybe automate in cron?
13 May, 2009 Plocher draft best practices for mail man list moderation settings, draft a new policy related to list moderation (http://www.opensolaris.org/jive/thread.jspa?threadID=102430&tstart=0)
10 June, 2009 Michelle update website FAQ based on Plocher's best practices
April 30, 2009 Deirdré twitter
April 30, 2009 Plocher look into a way to turn on/off archival setting on pages for agenda.
  • Wikipedia has "Protected" pages of several flavors. I'm checking with Al Hopper to see if Genunix has this feature. [1]
  • Start with old agendas, move on to policies
Retrieved from "http://wiki.genunix.org:8080/wiki/index.php/2009_09_24_OGB_Agenda"
Personal tools