A project to define the intended relationship and associated
interactions between the Architecture Community and the other
OpenSolaris Community Groups and Projects.
Charter: To develop a formal proposal that can be brought back
to the ARC community and thus to the OS.o community at large that
sets forth the specifics of what the relationship should be
between the Architecture CG and the rest of OS.o, how it is
expected to interact with the various CGs and Projects, and how
the Architecture CG itself is intended to operate.
Context
ON/Nevada OpenSolaris Development Process
http://www.opensolaris.org/os/community/on/osdevprocess/
Sun's ARC Process
http://www.opensolaris.org/os/community/arc/handbook/sun-reviewprocess/
Some of the things that I expect that this project will need to
contemplate, address and/or define are:
For context and understanding:
How does the Sun ARC system operate today?
What was the ARC/dev process that was developed as part of the OS.o
community launch?
What other development processes are in use in the community?
What roles exist in the OS.o community?
How do they relate to the development and ARC processes?
What workflows exist in the OS.o community today?
How do they relate to the development and ARC processes?
Who should "do" ARC? When and how long?
Who/what should "be" ARCd? When and how often?
Who consumes the output of the ARC process?
What are those artifacts?
Are ARC decisions binding or merely advisory?
Who decides?
Not all CGs/Projects have the same needs.
What interactions are expected or desired between the
Consolidation CGs, the "other" CGs, Projects, the various
Distros, the Architecture Community and this thing we call the "ARC"?
What do the terms "do", "be" and "ARC" mean as used above?