Re: [Evolution] Evo bug squash?

[Chenthill <pchenthill novell com>]

On Thu, 2009-04-09 at 14:29 +0200, Patrick Ohly wrote: 
> Hello Andrew!
>
> Thanks for raising this issue and for this "bug squash" initiative. I
> agree with everything you said so far, in particular about treating open
> source software like any other software engineering project;
> unfortunately my time is very much limited, so I won't have time to
> participate in the "bug squash" event.
>
> On Wed, 2009-04-08 at 13:14 -0400, Andrew Montalenti wrote:
> > I've been thinking about a way I could take Art's advice and make my
> > criticism more constructive.  The only thing I can think of is by
> > volunteering my own time to organize a "bug squash" day for Evolution.
>
> Such a "bug squash" may be useful to fix some of the low hanging fruits.
> I'm less sure about the more fundamental aspects, like reimplementing
> features that were removed when going to the SQLite based folder
> summaries. This may require work that goes way beyond what can be done
> in a weekend.
>
> > Is there already something like this scheduled?  If not, what's the best
> > way for me to organize it?  What wiki should I use?  (I notice one on
> > go-evolution.org and one on live.gnome.org -- which one's better?)
>
> I'm not that much into Evolution development, but as far as I know,
> go-evolution.org is the Wiki used by the development team.
>
> > I'm not a formal evo developer, but have enough C, GTK+ and GObject
> > knowledge to hack around, albeit probably at a slower speed than
> > full-time GNOME hackers.  Anyone else who has software experience and
> > would have some time to volunteer to this?  I'm thinking it could be on
> > an upcoming weekend, to accomodate people's work schedules.
> >
> > Also, what time zone are the core Evolution developers in?
>
> The question is perhaps more fundamental: who are the core developers?
> Who is still active and able to help when non-core developers prepare
> patches? When I fixed some of the calendar issues last year, patch
> review was often delayed considerably.
Probably we could have some page in go-evolution.org to list the core
active developers. It would be good if more people who know the code a
bit get involved for patch reviews to get it done faster. If some
critical patch is waiting w.r.t calendar, it can be assigned to me.

> Perhaps it will be easier when GNOME and thus Evolution switch to git:
> clone the source and then prepare a "community edition" with pending
> patches that haven't been incorporated upstream yet.
>
> On Wed, 2009-04-08 at 18:27 +0100, Pete Biggs wrote:
> > I suspect that the best thing all round is to take this to the
> > evolution-hackers list since this is primarily a users list.
>
> The core developers definetely should be informed; I would hope that
> they read this list. But I think chances to find new people who can work
> on Evolution might be better here: users are the ones motivated to fix
> problems because they still, well, *use* the software and there might be
> some who are capable of helping but haven't joined the hackers list yet.