[Zope-Coders] how are we doing?

[seb bacon]

I've committed to a CMF branch only.

Like everyone else, I'm very busy, and internal projects simply have
to take priority - I run my own company and work 12 hour days
regularly :\ 

There is definitely some impedence to committing:

 - being unfamiliar with the setup, I tend to triple-check everything;
   therefore even small changes take a while

 - I'm nervous about checking in even tiny bugs without passing them
   by someone else

 - I spent about an hour doing some STX changes, only to find Andreas
   was doing the exact same changes and committed them first!

These factors add up to me feeling like I really need to set aside a
a large portion of a day even to do a small fix, at the moment.

The fact that everyone's so busy can't really be helped; I think 
having more committers is the only way to get more activity in this
respect.  Typically, I would expect to see commit activity coming in
bursts, in synch with internal commitments.  For me, that means a
burst every 6 weeks or so.

The nervous / unfamiliar thing will go over time.  An important
question: is it good or bad to be extremely cautious?  Would it
perhaps be better to have more mistakes but a higher turnaround of
fixes?  Would you guys like to see more fixes happening unilaterally? 

I entirely agree that the collector should help focus these issues.
I'd like to see ZC nominate some minor areas of Zope for which the
outside commiters can assume full responsibility, and then channel
these via the Collector.  

seb

* Casey Duncan <c.duncan@nlada.org> [011031 14:15]:
> On Wednesday 31 October 2001 09:47 am, you wrote:
> > About a month or so ago we opened up CVS access to... I think... 6 new
> > people or so?  I've seen a few checkins from Steve Alexander, but nobody
> > else, which surprises me.  Is this because folks are still getting their
> > bearings or because the new folks with checkin privileges are busy with
> > other stuff; or maybe the checkins list isn't reporting some checkins?