On Tue, Jul 26, 2011 at 4:49 PM, Chad <innocentkiller(a)gmail.com> wrote:
On Tue, Jul 26, 2011 at 4:42 PM, Platonides
If the author considers it ready to merge and
there has been no
opposition in a week, then merge it.
That would solve the rotting problem. I don't think it would be hard to
keep a branch up to date for a week (at least without other merges).
I disagree here. Silence should not be taken for assent. Perhaps we
should formalize the "approval" process for RfCs. I agree with the
rest of your message in that we absolutely need to get more eyes on
RfCs...and I'm open to suggestions on how to do so.
Well, I think checking into trunk after a week could work once we get
caught up with code review on trunk, though email to wikitech-l needs
to be a required part of the process. I'd ask that everyone hold off
on being this aggressive before we get caught up, since this will only
exacerbate the review backlog. As of today, we're closer than we've
been for a very long time, with 728 "new" revisions, and we're
trending in the right direction.
The RfC process can work if people make an earnest effort to get their