Dev Meeting Notes: May 26, 2005
* Create a visual for the relationship between Solaris and OpenSolaris similar to the Mozilla roadmap
Owner: Karyn, CAB
* Determine whether or not we have OpenSolaris releases, and if so, how it is determined when we have a new one?
Owner: CAB
* Develope specific rules and process for when something is kept 'secret', other than previously encumbered code.
Owner: Tonic Team
* Are we going to continue to group software together into consolidations?
Owner: Joe, CAB
* Drive adoption of the existing Solaris Big Rules
Owner: CAB
* Create ability to match people with projects - single place to go to learn about existing projects
Owner: Tonic Team
* Create checklist for the final approver
Owner: John
* Create checklist for ARC
Owner: Bill
* Create process for testing
Owner: Keith
* Create list of 'applicable policies' that may require review/modification for OpenSolaris
Owner: David
* Identify factors for when a change has global impact and requires 'C-Team' review for approval
Owner: David
* Create process for putbacks to multiple branches
Owner: Bill
* Define rules for when to branch and branch rules
Owner: CAB
Future Meeting Topics
* Scalability of the process for the outside developer
* What tools are required to make this process successful?
* How many ARC's do we need/want?