[RFC] Moving Wishlist Items to Brainstorm

[Myriam Schweingruber]

Hi Martin,

On Sat, May 25, 2013 at 10:51 AM, Martin Graesslin <mgraesslin at kde.org> wrote:
> On Saturday 25 May 2013 10:03:16 Luca Beltrame wrote:
>> That said, voting etc might be useful to do some pre-screening on feature.
>> Although votes are not a useful metric per se, my last experiment with
>> scoring Brainstorm ideas put genuinely useful ideas at top.
> For me the feature of down voting is the most important one as that
> automatically removes the stupid ideas. And out of experience: those are the
> most annoying ones. The users don't accept a "sorry, this doesn't make sense
> because a, b, c". They start to argue and that's binding time. Getting this to
> be downvoted by users helps solving the problem.
>>
>> But keep in mind point 2 from above: if it's just a dumping ground, you'll
>> get rid of a frustration to get another one in.
> It doesn't have to be a dumping ground. If the voting and discussions work,
> the system should produce high quality ideas. Whether they get implemented is
> then a different question (c.f. shutdown of Ubuntu brainstorm). But if it
> really a good idea and not dream concert (e.g. Plasmoids in own processes) I
> don't see a reason why someone would not want to get a good idea into the
> product. And that could be crowed sourced ,too - doesn't have to be the main
> developers to implement ideas.
>>
>> Also, if there is a plan on using Brainstorm as is, perhaps some pubicity
>> might be needed (currently it's very low on the radar).
> Yeah that could be a good idea to do it in the same step and e.g. announce on
> the dot that Plasma moves over to brainstorm for feature suggestions.

While I salute your idea I fear it will not work, as it needs Plasma
people to actively work on Brainstorm, and that is already not the
case on bugzilla. Moving the wishes elsewhere is just moving the
problem elsewhere.

As long as the Plasma Team doesn't really, really do what they boost
they do ( as in maintaining a codebase which implies also maintaining
a bugs list like we do in Amarok and many other projects) and really
look at the bugs list and work on the existing bugs that will simply
not work.

IMHO a good Project Management also means they take care of their bug
list themselves. Currently they leave it to the bugsquad to clean up
what they should handle themselves. No dedicated Plasma person to
maintain the bugs list and no Plasma devs working on existing bugs,
and then pretending they "will maintain the existing codebase for 2
years" when de facto it already is unmaintained since over a year,
maybe even more judging by the age of some bugs... I have cleaned up
the Plasma bugs list once, and everybody was happy and oh thank you,
but they didn't follow and the mess is now exactly the same as when I
started to clean up. So much for really taking Quality efforts
seriously...

Michael's comment in the other RFC thread is so true, unfortunately.

So please, Plasma people: do manage your project , and I mean really
manage it, and that also means you handle your bugs yourself and
maintain your bug list actively yourself! Else you will for ever
remain a bad example on how not to manage a project, sorry. Moving the
wishlist to Brainstorm just means moving it even more out of sight, as
there are less devs on the forum than on bugzilla.

Martin: I thank you for your energy to help the Plasma team to do
their work, but you are actually the only one taking care of this and
even bother to see the problem, I hope you are aware of this. I for
sure have no time nor energy in helping them, as I have done and the
work was ultimately for nothing.


Regards, Myriam
-- 
Proud member of the Amarok and KDE Community
Protect your freedom and join the Fellowship of FSFE:
http://www.fsfe.org
Please don't send me proprietary file formats,
use ISO standard ODF instead (ISO/IEC 26300)