I am ccing this to kernel mailing list, cause in my point of view this at=20
least partly points at a failure of proper kernel management.
Am Sonntag 17 Juni 2007 schrieb Con Kolivas:
Hello Con!
Thank you very much!
ck patchset introduced to me the concept of seamless audio playback - no=20
matter what - and improved my desktop experience with KDE on a IBM=20
ThinkPad T23 quite considerably. I had the feeling that I have bought a=20
new machine actually ;-). I really enjoyed ck quite much - like suspend2=20
which still isn't in mainline either despite its technical superiority=20
(in my eyes).
However I agree with you that when you feel more frustration than fun with=
=20
developing the ck patchset it is time to stop doing it.
I think the way mainline management is done right now certainly needs some=
=20
improvements! When it comes to collect technical feedback before=20
summarizing it - as I told Linus -, but mainly on the side of=20
communication. Actually I believe that aside from technical aspects the=20
way of communication, the tone of it is really important, too. And I=20
perceived *lack of communication* where it actually from my point of view=20
was greatly needed. Maybe just a *friendly* word, a "thank you" would=20
have done so much of a difference at times.=20
I was trying to bring some communication in there by private mails to you=20
and Ingo - but maybe this was a mistake - not Linus or Andrew. It is a=20
pity that it didn't work out, but I at least hope it helped a bit.
Every communication has at least two partners. I believe that each of the=20
partners was involved in this outcome. And I believe that kernel=20
management can be improved by actually looking at what really went on=20
here.
At least in my eyes the kernel development involvement process should not=20
frustrate talented developers like you, Con, to a point where they do not=20
want to contribute anymore. Also here are at least two communication=20
partners involved: The developer who wants to contribute and the decision=20
makers and reviewers.
Since you made your decision I understand when you do not want to look=20
deeper into that. For Ingo, Linus, Andrew and everyone else involved it=20
IMHO still is worth to look at what happened here and what their part of=20
it was - in order to find a way to utilize the talent of talented=20
developers who want to contribute instead of letting frustration raise so=20
much as seen here.
Regards,
=2D-=20
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
Previous message: [thread] [date] [author] Next message: [thread] [date] [author]
Messages in current thread:
way of managing the kernel development involvement process ..., Martin Steigerwald, (Sun Jun 17, 3:38 am)