Brian Gupta writes:
> On Nov 28, 2007 3:16 PM, James Carlson <james.d.carlson at sun.com> wrote:
> > I agree with making this document clearer. It should explicitly say
> > that the OGB itself doesn't approve projects, and that you (the
> > project proposer) need to find and talk to the appropriate community
> > group (or groups ...), and then get that group's facilitator to talk
> > to Eric.
>
>
> The OGB seems to provide a centralized registration facility for newly
> approved projects. Would this be a better way of wording it?
I think that will still confuse people. If we're providing a document
that explains how to use the mechanism, we shouldn't dive into the
details of where the mechanism came from or who provides what.
Instead, spell out what the user must do in order to be successful.
Nothing more or less than that.
To be successful in creating a new project, you must:
- Draft a project proposal with at least the following
information:
<insert here>
- Discuss that proposal within a Community Group that you
believe should endorse the project.
- Ask the Community Group to endorse the project. Absent some
other local policy, the common policy is a consensus vote of
the Core Contributors.
- Ask the Community Group's Facilitator to contact the Project
Herald and create any necessary resources for the project.
Absent a Facilitator, ask one of the Core Contributors to
help.
That's all. No OGB needed.
--
James Carlson, Solaris Networking <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
