OGB Group Lifecycle Administrative Procedures

From Genunix

Jump to: navigation, search

Communities, Projects and User Groups Creation

This is a process and procedures document that is referenced by the OGB_2008/010_OpenSolaris_Constitution_2009 It is maintained by the OGB, and is expected to evolve as needed to meet the needs of the community.

See also: http://opensolaris.org/os/community/web/infrastructure-setup/

This document uses the term "group" to refer to an instance of a Community, Project or User Group.

Goals/Desires

  1. Groups can be Created, Archived and Reactivated as well as change into other Group Types
  2. We desire there to be a lightweight process for creation
  3. All Group Types are considered equal for the purposes of this document, though individual groups may align themselves with others in arbitrary relationships. It is the responsibility of the leaders and facilitators of any such groups to monitor, and if needed, manage, the lifecycles of their related groups.
  4. Survival of the fittest, matching natural open source evolution
  5. Communicate that something new has been formed to those interested
  6. Retain OGB oversight to act as a "safety valve" for exceptional cases

Creation Process

(Note: While this process currently uses Bugzilla as an issue tracking mechanism, the OGB is eager to modify it when a better workflow solution becomes available to the OpenSolaris community)

  1. Go to http://defect.opensolaris.org
  2. Create a new "bug" under Community > Infrastructure > Create with the following information
    1. Your opensolaris.org user ID (required)
    2. Type (Community, Project, User Group)
    3. Group Name
    4. Title
    5. Description
    6. Leaders (opensolaris.org user IDs required)
    7. Mailing List Requirements
  3. Someone other than yourself with an Opensolaris.org user ID needs to vote for the "bug" you just created. Group requests will only be accepted once they have one or more votes from people other than the originator.
  4. Wait. As someone becomes available, your request will be processed by one of the admin team and you will be notified.

Group Type change

  1. Go to http://defect.opensolaris.org
  2. Create a new "bug" under Community > Infrastructure > Change with the following information
    1. Your opensolaris.org user ID (required)
    2. Group Name
    3. New Type (Community, Project, User Group)
    4. Rationale/context
  3. Wait. As someone becomes available, your request will be processed by one of the admin team and you will be notified.

Archiving

From time to time, a group may become dormant. If there has been no activity from a particular group for 6 months, or at the discretion of the OGB or its nominated Board Committee acting in the interests of the community, the following may happen:

  • Mailing list changed to 'no subscriptions'.
  • Web page visibly tagged with 'Dormant'
  • List of leaders/participants reset to zero
  • SCM write disabled

Reactivating

Should you wish to reactivate an Archived group

  1. Go to http://defect.opensolaris.org
  2. Create a new bug under Community > Infrastructure > Activate with the following information
    1. Group Name
    2. Reasons to activate
    3. Leaders (At least two, opensolaris.org user IDs required)
  3. Wait. As someone becomes available, your request will be processed by one of the admin team and you will be notified.

Implementation Notes

  • All notifications to bugs in Community > Infrastructure > Creation will be sent to group-creation@opensolaris.org
  • Leaders are those who have admin and decision rights within their respective group
  • Leaders can add permission rights as and when they see fit, so there is no need to burden the group creation process with a requirement to gather a list of people who will get Contributor rights
  • Mailing list names should indicate purpose, and have one of the following suffices
    • - dev: Developer discussion
    • -discuss: General discussion
    • -notify: Notification alias for SCM putbacks
  • Private mailing lists may be granted in exceptional circumstances, but full rationale is required and OGB signoff
  • Although this process is intended to be essentially one of assumed automatic approval, the OGB reserves the right to veto group requests.

The places where "wait" is indicated above are presumed to be interfaces to other processes and people - if there is urgency or concern that a request has gotten dropped, please bring the matter to the attention of the OGB, either by sending mail to ogb-discuss or by calling in to an OGB board meeting and inquiring.

Retrieved from "http://wiki.genunix.org:8080/wiki/index.php/OGB_Group_Lifecycle_Administrative_Procedures"
Personal tools