https://bugs.kde.org/show_bug.cgi?id=481069

--- Comment #19 from Flossy Cat <flossy-...@online.de> ---
(In reply to Nate Graham from comment #7)
> (In reply to Flossy Cat from comment #6)
> > …
> > How does KDE know which features are unused and how is removal decided?
> We largely have no idea. 

The reactions of users in this discussion clearly show, how ill advised the
removal of this feature was.

This clearly demonstrate a serious bug in the KDE decision processes.

Further your answer in comment #13 demonstrates more crucial bugs:
There seems no onboarding process for new volunteers, no mentoring, not even
introductive documentation …

Where to discuss this bugs and proposals for solution?

> It's an unfortunate side effect of our commitment
> to not spy on our users. It means we're in the dark about what they actually
> do with our software when they're not somehow making noise about it
> publicly. Features that get bug reports and that people are talking about in
> public (on social media, in our forum, in reviews of our software, etc) are
> features that we know people use. Other ones... well, we don't. We try not
> to remove stuff for no reason, but when a feature's code is old and flawed
> at a fundamental level and it seems like it's blocking an effort to do
> something new, that's when the feature is going to end up on the chopping
> block rather than getting fixed if no one can find anyone who uses it.
> 
> This is obviously pretty flawed but I don't know how we can do any better
> without turning to the dark side and spying on our users.

I'm not as pessimistic, but this is not the proper place to propose solutions …

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to