[maemo-developers] QA process = bug fixing disincentive?

[From: Andrew Flegg]

Alan wrote:
> On Mon, Nov 2, 2009 at 7:12 AM, Andrew Flegg <andrew at bleb.org> wrote:
>
> > I'd say we've had more intelligent thought and discussion here than
> > I'd expect on this topic on talk
>
> Grrr!
>
> I hate that kind of talk. It only makes the problem worse.

What problem? This mailing list has a higher concentration of involved (and affected) developers than talk. You can have an intelligent discussion here without it devolving into petty spats or rampaging off topic. This is the official mailing list for the development of (and developers for) Maemo.

It is also easier, as someone strapped for time and wanting to make a positive contribution to Maemo, to spend time thinking of fundamental problems like this with a low-volume of well-formed ideas for debate and consensus. Mailing lists have advantages over fora, and vice versa.

Trying to corale all the discussion to one form and medium is just likely to lead frustration for everyone. This is one of the tenets of good knowledge management: there's no single technology which is perfect for all forms of discussion and storage.

> If you aren't part of the solution...

I think streamlining the process so that high quality software can get into Extras in a timely manner without severely disavowing developers from their "release often, release often" tendencies is more important than whether this should be discussed in the wiki, off a blog post, in a brainstorm or on tmo.

Fortunately, there's enough work for everyone - so please feel free to make sure anyone on tmo who can contribute comes here to do so. I don't want to limit the discussion but why should it be Not Here?

Cheers,

Andrew

PS. I wrote this on the train. There's no Maemo offline client for vBulletin ;-)

-- 
Andrew Flegg -- mailto:andrew at bleb.org  |  http://www.bleb.org/