OAF commit policy

[Maciej Stachowiak <mjs eazel com>]

Hey everyone,

I decided the OAF commit policy was too anal as written. Below is the
new version, from HACKING. It seemed silly to try to be more anal
about checkins than gcc (where about 80 people total have blanket or
local commit privs), so I came up with something more modelled on what
gcc does (but more lax). Plus, it's closer to what I was actually
doing.

I also put a bunch of people in MAINTAINERS with various levels of
bits (Me, Elliot, Darin, Mathieu, Michael and a couple of other
people).

Merry Christmas,

Maciej

-------------

Please send patches to gnome-components-list gnome org with
descriptive ChangeLog enttry for review before committing, and get
approval from Maciej (or Darin in his absence). Generate patches with
diff -u or better yet diff -up. Please send to the list and not to
anyone directly so everyone has the opportunity to comment. Always
write an informative ChangeLog entry for your changes.

If the patch is an obvious fix and you don't get any feedback in a
reasonable time frame, just go ahead and commit. For critical bug
fixes (won't compile, crashes on startup, etc) feel free to just
commit but please bring the issue to my attention (I can check the cvs
history if I need to, but I'll be happier if you send a patch; just
`cvs diff -up | mail -s "Patch I just committed" gnome-components-list gnome org'
before  you `cvs commit').

If you are listed in MAINTAINERS as having blanket commit priveleges,
just go ahead and commit anything reasonable (likewise if you are
listed with local commit privs for an area, and want to change that
part of the code). Use your best judgement deciding what changes are
better to discuss first (I'll try to discuss major issues publicly
too). I'm open to giving pretty much anyone at least local commit
privs for particular areas if they do sustained good work in that
area.