Hi all,

Just a quick idea to throw out there: The steering board has a weekly
patch review meeting where they take a popular patch that's been
sitting in the tracker for a while (multifont, bmp resize, snc viewer,
etc), give it a thorough analysis, and post the results to the task
and/or mailing list. I think that this would be a lot more effective
and encouraging to developers than a more generalized push to say,
improve recording, playback, the UI, etc, which may leave patch
maintainers feeling a little bit "same old, same old". By giving the
patch a good going-over, the pros and cons can be clearly stated and
it can actually be given a chance to move forward or be pushed to the
side, instead of continuing to rot. This is something that a lot of
people have wanted time for, or has secretly hoped someone else would
take the initiative on, but it's just never happened. I realize that
it's not exactly the type of job that the RSB was created for, but I
think it fulfills the stated purpose of breaking blocks to
development.

Throw your darts.

Regards,
Marc
Received on 2008-10-02