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

[Christian Loose]

Am Donnerstag, 5. Februar 2004 10:59 schrieb Stephan Kulow:
> On Thursday 05 February 2004 07:11, Frans Englich wrote:
> > Yeah, it's all about manpower, no question. But if we had a RD who said
> > "We will not release /until/ the count has dropped to X" I think people
> > would care in a whole another way. Just a wild idea.
>
> Read http://lists.kde.org/?l=kde-core-devel&m=104694433203080&w=2
>

Only partly related to this.....

I find it a little strange that we have bugs and wishes with patches in our 
database that seem to be ignored by the corresponding maintainer [1]. 

I think that this doesn't give the provider of the patch the feeling that his 
contribution is welcome and I'm pretty sure that we don't want that. How do 
we want to gain new developers when we ignore their first contributions?

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?

Well I just wanted to bring this up...

Bye,
Christian


[1]
a few examples:

http://bugs.kde.org/show_bug.cgi?id=63938
http://bugs.kde.org/show_bug.cgi?id=69760
http://bugs.kde.org/show_bug.cgi?id=72347