cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Luigi Bai <>
Subject Re: Let's deprecate the PHP block
Date Tue, 26 Oct 2004 21:21:47 GMT
On Tue, 26 Oct 2004, Stefano Mazzocchi wrote:

> Luigi Bai wrote:
>> On Tue, 26 Oct 2004, Stefano Mazzocchi wrote:
>>> forth: some of us spend a great amount of their life trying to come up 
>>> with strategies that avoid the use of those rules, and understand how 
>>> complex groups form and dissolve, how innovation happens and how community 
>>> fractures can be avoided. When shit works well, like this project, it's 
>>> easy to think it 'just happened' and much harder to see all the social 
>>> work that made it possible, including allowing informal votes to happen 
>>> and keeping rules to a bare minimum.
>> Maybe it is more precise to say "When shit works /mostly/ well...". The 
>> presence of a large number of outstanding Bugzilla issues, especially ones 
>> with [PATCH]es attached, implies that things work well for committers, less 
>> well for those of us who have to wait until "someone just gets around to 
>> it". Fixing bugs isn't sexy, like Flow or Forms or Real Blocks. But it 
>> should happen every once in a while, especially when other people have 
>> already proposed the patches.
> If you have ideas on how to make it better, we are wide open to suggestions.

Okay, assuming your sincerity - what is the current method for committers 
to find/fix/close issues in Bugzilla? Are votes used, or longest time 
open, number of comments? How often are these criteria applied 
(periodically, only FirstFriday, only before release)?

Knowing these, we can figure out a way to improve the system, or the 
users's expectations (or both!).


View raw message