My votes:
[+1] All committers follow Commit-Then-Review for safe changes,
Review-Then-Commit for potentially breaking changes. What
constitutes a breakng change is a judgment call to be made
by each committer. The rule of thumb is that changes which
involve advanced/sophisticated C++ features, C99 features,
or optional POSIX (and other) extensions may cause breakage
on some platforms.
[-1] All committers follow Review-Then-Commit for all changes
with no exceptions.
[+1] New committers and committers who haven't been active in
more than [6] months follow the RTC policy for at least
[3] weeks of sustained activity, all others CTR.
