[development] Intelligent use of time (Re: Perm for setting RTBC

Fernando Silva fsilva.pt at gmail.com
Tue Jul 3 14:56:52 UTC 2007

We are trying to find a solution, for a problem that does not exist.

The logic road for an issue is:
[feature or bug] -> patch -> work -> review -> commit

And there is no problem, if the commiters do their work and keep the
commit queue almost empty. It's so easy!!! Are core developers afraid
of having to go through many issues, to find that is a loss of time?
If you keep them empty it's not a loss of time.

* Do not set your own patch to RTBC, will keep most of the patches of the queue
* Somebody will have to look at it, and it's easy to read reviews from
others and give them credits.

Want the holly grail solution? Here it is:
1. fill the issue queue
2. start making patches for the issues
3. people will review those patches and write about it
4. for each good review a "core developer" finds he will give that
review a rating
5. for each patch that is commited, the guys that reviewed it will
have some points according to their rate
6. people will start to have points for their merit, and will start to
influence issues in the queue
7. issues with reviews from high ranked reviewers will go up
8. core developers will start to do their job of commiting patches

A technical rating system to solve a social system! Right?!

On 7/3/07, andrew morton <drewish at katherinehouse.com> wrote:
> On 7/3/07, Earnie Boyd <earnie at users.sourceforge.net> wrote:
> Knowing what a pain it
> is to gather up reviewers for the votes would encourage people to be
> less honest that a previously RTBC patch is now PNW or CNR.

More information about the development mailing list