Re: Hidden agendas and Soft Targets [Was: Re: Warning fixes]

On Wed, 2006-10-18 at 15:10 +0200, Andre Klapper wrote:

> yes, but should poking really be necessary all the time?
> it ain't cool to *beg* for important stuff to get done, especially if
> the important stuff is not that hard to recognize (in bugzilla, we have
> target milestones, we have severity/priority - what else do we need?
> another wiki page, another mailing list rant/discussion as we had for
> the 2.6 UI changes?). 

What I think is really needed is a location for front line development.
By that I mean, a location where the actual development happens. Rather
than a location where past development gets reviewed.

It's uncommon in software development that a changeset is immediately
correct. It's extremely common that software developers discuss and play
with each others ideas and experiments. The discussions and experiments
are the real development happening. 

This is not happening at the Evolution project. Especially not outside
of the Novell building. 

> use bugzilla correctly, be careful with target milestones, take a look
> at the "urgent" or "blocker" issues regularly, review patches - this
> only seems to have happened partially for the last development cycles,
> and i unfortunately don't expect any improvements in the short run. :-/

Agree

> > Andre has been approving i18n/Documentation related
> > patches for more than a release now.
> 
> i did because i was annoyed of waiting for nothing to happen, so this
> isn't an example of potential non-novell maintainers, but quite
> contrary: the reviews weren't fast enough or didn't take place at all,
> so at some point i told myself: well, even if i break something, why
> should i care? better to break something from time to time, then to not
> have any progress at all.

Exactly the feeling that I'm experiencing with many other parts of the
Evolution projects. Especially (for me) Camel.

Except that for those other parts, there's no you. There's no Andre who
made the decision to have progress.


-- 
Philip Van Hoof, software developer
home: me at pvanhoof dot be
gnome: pvanhoof at gnome dot org
work: vanhoof at x-tend dot be
blog: http://pvanhoof.be/blog