Am Dienstag, 4. Oktober 2011, 16:25:50 schrieb Aaron J. Seigo: > On Saturday, October 1, 2011 09:24:25 Sven Burmeister wrote: > > thread and true for devs and users likewise. The dangerous thing about > > it is that users' and devs' frustration amplify each other. > > the truly dangerous thing is nobody doing anything.
[snip] > if there is interest in doing the above (which i have seen little evidence > for in this thread, which has been more about prose writing and sharing > disonnance so far), perhaps a restart would be useful. a team can > self-organize which takes on this issue as an actual project like any other > with goals and methods (tbd) and time commitments. those who will not > actually do the work required can sit it out and in time we'll have > improvement. > > otherwise, this is a waste of time, patience and community good will. Indeed. There are people involved in KDE for more or less time. Payed and unpayed positions, postitions with a lot of influence and such with less, people with more abilities and people with less regarding programming etc. So is this the first time you suggest that approach? If not why did it not work last time? I mean it's not like (and I only mean this very topic) if there was a lot more than prose by those involved last time it would keep creeping up every now and then. And of course it does not make sense to mix topics. There are things that are plain wrong, not necessarily bound to KDE but on a community level. Those have to be named and straightened out. And then there are a lot of things with two sides to them which one should not just see one-sided, be it the user or dev's side. Martin brought-up the issue of useless bug-reports. a) because they are about a version that is too old and b) because they lack information. All needed to solve a) is to disable reporting of bugs for all but the current major and maybe even minor version at bko. According to Martin this would save a lot of time for KDE developers. However this means that downstream has to take care of those bugs that cannot be reported upstream anymore or simply update their users to the latest minor version of the major version they shipped. It would be up to the KDE devs to provide some "guarantee" that distros can rely on in order to lose their angst about regressions and being left alone with them. Since we have to start somewhere, as a plasma dev, how do you feel about prioritising regressions as soon as they are reported and fixing them ASAP, i.e. before the next minor release at latest? Sven >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
