I've noticed that the text here:

  http://opensolaris.org/os/projects/

is now out of step with the current OGB-approved project creation
policy:

  http://mail.opensolaris.org/pipermail/ogb-discuss/2007-May/000437.html

Could we have this text updated?  In particular:

  OpenSolaris projects are collaborative efforts that produce objects
  such as code changes, documents, graphics, or collaboratively
  authored products.  Projects will have code repositories and
  committers and can live within a community or independently.

Problems:

  - Projects may also include interest areas that don't actually
    produce any code changes or documents.  (Minor issue, but needed
    for the marketing and outreach community.)

  - Projects don't necessarily have code repositories, but they can.

  - Projects are always sponsored by a community; none are
    independent.

And for this section:

  The process for requesting a new project requires that a community
  member write a proposal to the opensolaris-discuss list and at least
  one other community member agree with the proposal. If the proposal
  doesn't garner a seconder within 30 days, it will be considered
  void. The process is intentionally lightweight because we expect
  that the bulk of new collaborative efforts will be projects with
  many growing into full communities comprised of one or more
  projects.

Essentially none of this is true now.  Instead, the following:

  - Projects must be endorsed by communities and may be endorsed by
    more than one.

  - Communities themselves may determine how they want to endorse
    projects, which projects to endorse, and what process (if any)
    they'll use to do so.  They may also remove endorsement.

  - Communities need to communicate to the OGB (perhaps via someone
    serving in a "project approver" role) which projects have been
    endorsed, and provide the required information to have resources
    for the project allocated.

  - The usual way to start a new project is to bring up the topic
    within a community discussion list, hash out the issues there, and
    then request project creation when agreement is reached.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

Reply via email to