OpenSolaris

This is a list of projects that need to be done as part of the OpenSolaris ARC community, with the aim of developing the processes and tools needed to support the evolution of OpenSolaris's architecture.

At this point (community launch) this is more of a list of questions and TODO items than anything else.

  -John Plocher

Community Charter

• What do the OpenSolaris charter, governance and development process proposals currently say about the ARCs; what should they say?

• Charter: <http://www.opensolaris.org/jive/thread.jspa?threadID=3186&tstart=0>
• Governance: <http://www.opensolaris.org/jive/thread.jspa?threadID=1341&tstart=29>, <http://www.opensolaris.org/jive/thread.jspa?threadID=1393&tstart=30>
• Dev Proc: <http://www.opensolaris.org/os/community/on/os_dev_process/> 

•  * Brainstorming and discussion of what works, what should be done, logistics and infrastructure, etc:
•  * Getting started - self-reviews and fasttracks from the community
•  * Getting serious - full reviews and community membership
•  * Are there differences between "today", "while we are in a transition", and "when we are done"?
•  * If ARC membership comes from the set of community leaders because they are the stewards of their shared source-code commons, how are you involved with the OpenSolaris community?

Community membership 

• How do people join the ARC community?  
•  * Is it tied to mailing list subscription?
•  * Is it automatic (i.e., all community leaders are also ARC community members)?
•  * What is the community's relationship to Sun's existing ARCs?  PSARC?
• What does "join" mean?
•  * mechanics: mailing lists/forums...
•  * What are the various responsibilities? leader -vs- member -vs- observer...
• How does affiliation enter into the picture?  
• What is the relationship between members, leaders and those who can/should be able to add/modify web site content?

Define an Architectural development processes and start using it

• What are the goals of such a process?
• learn from history what works, what doesn't...
•  * Historical @Sun
•  * Historical Apache
•  * Historical Linux
• Nail down our own "givens and druthers" (constraints and desires)
• Propose a process
• play, test and improve - how it is done is less important than getting the results we desire - make sure we understand what we really need!

Tools and other infrastructure
   what do we need to do/have to make this extremely easy for developers to actually use*?  

•  * Changes to the OpenSolaris web site?
•  * Tools for members, projects, communities...
  • * Metrics, dashboards and other reports
  • * Workflow (who is waiting for what...)
  • * Communication (forums, IM/IRC, announcements...)
  • * Searching and metadata (tags, conversations, archival...)