missing feedback (Re: [kde-announce] Announcing KDE 3.2)

Alexander Neundorf neundorf at kde.org
Thu Feb 5 20:56:33 GMT 2004


On Thursday 05 February 2004 21:30, Andras Mantia wrote:
> On Thursday 05 February 2004 20:12, Christian Loose wrote:
> > So my real question is, how should this be handled when one stumbles over
> > one of those patches? Just test and commit it? What do the other app
> > maintainers think?
>
> Just a vague idea: create a list where the patches are forwarded/sent.
> Anyone (with a CVS account) wanting to take care of those patches can look
> at it, ask the maintainer and if the maintainer doesn't react and the patch
> is good, commit. Hm, are the quality team members a candidate for this?
>
> Andras

Yes, constantly watching b.k.o is too much work for some of the developers 
(e.g. for me). So having somebody work on b.k.o, testing the patches, and 
when they seem to work good, contacting the maintainer "hey, here is a patch 
which I tested and which is really working" would be a good thing.

Bye
Alex
-- 
Work: alexander.neundorf at jenoptik.com - http://www.jenoptik-los.de
Home: neundorf at kde.org                - http://www.kde.org
      alex at neundorf.net               - http://www.neundorf.net





More information about the kde-core-devel mailing list