FLUID-869: OSDPL Governance: Plan the Governance of the OSDPL

Description

Plan the governance of the OSDPL site.

• Resolve questions in the Phase 2 document (http://wiki.fluidproject.org/x/C447)
• Create the OSDPL charter
• Create a document outlining a "Good Design pattern" for authors and editors
• Create a specification for implementation.

Comments

• Jess Mitchell commented 2008-07-22T22:28:45.000-0400

  Iteration16

• Jonathan Hung commented 2008-08-07T13:03:41.000-0400

  Could be useful: Simple review process for drupal.
  http://drupal.org/node/156317

• Jonathan Hung commented 2008-08-07T15:41:06.000-0400

  Currently working on a document that addresses the following questions:

  1. What will the process be for creating patterns and adding them to the library?
  2. What makes a good pattern/what are the guidelines for creating good patterns for the library?
  3. What will the process be for updating patterns?
  4. How should the OSDPL be moderated? By a person? By a technology?
  5. How will "ownership" be maintained?
  6. Who will write up the OSDPL group charter?
  7. Do we need to establish roles for users? If so, what are the different types of access they will need to the OSDPL in each role?

  I have a pretty good understanding of what is involved in answering the above with the exception of #2 and #6. #2 will be discussed with a small number of people via email. #6 will be started by me, but subject to revision by key OSDPL stakeholders.

• Paul Zablosky commented 2008-08-14T19:46:53.000-0400

  We need to think about the various roles people will take on in their associations with the OSDPL
  1. Site administrators and maintainers
  2. Pattern authors
  3. Pattern reviewers
  4. Site architects

  I've put some ideas about this into Jonathan's wiki page on governance.

• Jonathan Hung commented 2008-09-02T15:01:55.000-0400

  Done to the best of our ability. Time to move on to architecture and implementation.