Chris Jones <cjones@rupert.honors.montana.edu> writes:
> So, what *are* the responsibilities of core?  Does it all boil down
> to, "Decide what code is clean (or good, or whatever) enough to go
> into the tree?"  Or is there a lot more to it?

Core doesn't deal with 99% of commits. People may not realize this,
but after a new developer has gone through their probationary period
(where their sponsor usually looks at most of what they do), people
generally just "know" what they can commit without asking anyone, what 
they have to run past a mailing list or show around to others first,
etc.

Generally speaking, people audit each other's code if it is
significant, but the supervision isn't formal and isn't mostly done by
Core. Core's job is mostly dealing with fights and such, and approving 
big things like "can we cut 1.4 now?"

Perry