Hi,

Am Freitag, 18. April 2008, um 18:12 Uhr, schrieb Andras Mantia:
> On Friday 18 April 2008, Friedrich W. H. Kossebau wrote:
> > I guess we agree that every program should have some kind of active
> > maintainer, some people who feel responsible for it and have
> > sufficient knowledge about it, if it is included in a KDE module.
>
> This would be the ideal world. But even kdelibs has code that does not
> have any active maintainer, and I'm sure that is true for other code in
> other modules.
> If the application works, doesn't have any serious reported bug, there
> is not need to move to unmaintained. I'd actually be sad if such thing
> happens.
> Of course if it doesn't even compile, it is unusable or such and nobody
> cares about it, it can be moved away.

Alright. Yes. I overreacted perhaps. Felt responsible for any flaws as module 
coordinator. But that is wrong, am just coordinator, not maintainer, for 
sure. :)

So I learned:
I have to think we have some kind of passive anonymous maintainer 
collectives like all svn account holders. And especially the employees of 
distributions depending on KDE code who get paid to fix programs like Sweeper 
and KWalletManager, if there are serious flaws.
And this has proved to work. Because even a official maintainer might not be 
available if needed. So we just remove obvious bitrotten submodules, with 
grave bugs no one seems to care for.

Will do a call for maintainers on commit-digest or/and kde-devel, soon. And 
remove only klaptopdaemon, kdelirc, kmilo, and ksim, if noone takes over 
after the call.

Thanks
Friedrich
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team