[arc-discuss] Opening the ARC process - a 4 step plan

[James Carlson]

Richard Lowe writes:
> Justin Erenkrantz wrote:
> > While this email hints at it, can someone please point us non-Sun
> > folks at a definition of PSARC and LSARC?  What does PS and LS stand
> > for?  What's the dividing line between these ARCs?
> > 
> 
> PS is Platform Software
> LS is Layered Software

The dividing line is intentionally quite fuzzy.  The ARC is intended
to operate as a single body.  We're split into separate groups mostly
to help with load balancing (there are a lot of projects to review)
and to help provide a little more focus in some specific technology
areas.

When a new project comes in through the triage process, it gets placed
on a list.  Once a week, the ARC chairs meet and assign the projects
to specific ARCs.  This is often based on the subject matter of the
case (i.e., a driver would likely go to PSARC, while a browser would
probably go to LSARC), but also takes into account history: if one of
the ARCs has handled several related cases, the new case might go
there just to maintain context.

But the overall intent is that the xxARCs are all one ARC.  And we've
been known to rotate members around.

Note that this is architecture review, not design or code.  So, in
many cases, it's overall system engineering that matters.

-- 
James Carlson, KISS Network                    <james.d.carlson at sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677