Paul Butcher wrote:
I would like to see two things happen:
1) Make the process by which patches are accepted or rejected
2) Clean up the patches currently in the databases so that their status
is clear, and then keep on top of new patches as they come in. There may
be more patches than can be efficiently applied by the core team, but
they don't arrive so quickly that they can't at least be responded to
indicating where they stand w.r.t the transparent process.
I'd love to see a team of trusted Trac gardeners to help prioritise
incoming patches and deal with noise. There's no reason that the core
committers have to be the only people who can do this.