Loosening Quotient review requirements

[email protected] Mon, 04 Jan 2010 20:40:24 -0000
Newsgroups gmane.comp.python.quotient.dev
Message-ID <20100104204024.15596.1635065940.divmod.xquotient.856@localhost.localdomain>
Hello all,

I'd like to hear what people think about removing mandatory reviews from 
the Divmod Quotient development process.

At this point, I think I'm the only person interested enough in Quotient 
to work on it.  This makes it hard to get anything done with the normal 
development workflow.  I've gotten a little help on very small fixes so 
far (thanks faldridge!) but I don't really expect this to continue, or 
keep up with the pace of development I'd like to see.

The development process for all the rest of the Divmod projects would 
remain the same (at least for now).  I would do self-reviews and 
continue to seek out a high level of quality in the code.

This would only apply to me, since I seem to be the only developer.  If 
someone else shows up, then the problem goes away and we can resume 
reviews.

The alternative isn't very different.  There are things in Quotient I 
really want to fix; if reviews remain required and no reviewers are 
available, then I'll end up with a de facto fork of Quotient, also with 
no independent code review.  It would be simpler if I could avoid such a 
fork.

I expect most people on this don't really care about Quotient, but I'd 
like to hear from the two or three people who might have some interest, 
now or in the future.

Jean-Paul