| |||||||||||||
The Journal - a proposed syslog replacementThe Journal - a proposed syslog replacementPosted Nov 19, 2011 12:17 UTC (Sat) by rahulsundaram (subscriber, #21946)In reply to: The Journal - a proposed syslog replacement by aleXXX Parent article: The Journal - a proposed syslog replacement
What makes your method better? First you were worried that he isn't going to be able to maintain all of it but when I point out he isn't doing that, you complain about that too. I wonder what outcome will be considered satisfactory according to you.
(Log in to post comments)
The Journal - a proposed syslog replacement Posted Nov 19, 2011 12:51 UTC (Sat) by aleXXX (subscriber, #2742) [Link]
That he maintains his stuff.
Writing something, and then leaving the rest to others is easy.
Other well known developers ?
I mean, I'm not aware of any other high-profile developer who started so many things in such a short time and doesn't maintain them anymore.
Alex
The Journal - a proposed syslog replacement Posted Nov 19, 2011 13:22 UTC (Sat) by rahulsundaram (subscriber, #21946) [Link]
Now, this is exactly what I meant by you trying too hard. Lennart is still involved in everything he has written. Doesn't mean, he has to be the primary maintainer. I see, your list includes KDE but doesn't mention GNOME. That's very convenient. Firefox? Apache? PHP? Exim? GTK? The list of projects that have new maintainers now is far longer than yours.
David Faure might be involved in KDE but what about all the different KDE modules? There is nothing to indicate that developers have to hang on to every project they start forever. Quite the opposite. Transitioning maintenance is a *very healthy* thing to do. Nobody has to worry about the bus factor much if every project had new maintainers from time to time.
The Journal - a proposed syslog replacement Posted Nov 19, 2011 14:16 UTC (Sat) by Wol (guest, #4433) [Link]
But what if Lennart's strength is in design, not maintenance? As I describe myself, people come to me if they need a problem solved. Once I've found the solution, looking after it gets taken away from me.
Why do you want to ignore Lennart's strengths, and harp on his weaknesses?
After all, take Linus for example, how much kernel code does he write nowadays? I understand the answer is "nothing".
Why SHOULD Lennart have to look after his stuff that he's designed, once others see its value and take it over? Or do you think that Linus should be using a large chunk of his time looking after git?
Cheers,
That's funny... Posted Nov 19, 2011 14:37 UTC (Sat) by khim (subscriber, #9252) [Link] I mean, I'm not aware of any other high-profile developer who started so many things in such a short time and doesn't maintain them anymore. Funny that you started with Linus. Who quite explicitly developed "new thing" (git) and quickly shuffled maintenance to others. The fact is: creation of new software and maintenance are both important but these are different skillsets. If Lennart can find good maintainers who will support his creations - then all is well. Linus is good in both creation and maintenance roles - but even does not support everything he wrote.
|
|||||||||||||