Quality of Kwin on Xorg wasn't really satisfying, bugs didn't get fixed...
Announcement
Collapse
No announcement yet.
Martin Flöser Steps Down As Maintainer Of KDE's KWin
Collapse
X
-
Originally posted by sa666666 View Post
Responding to a troll, obviously, but it's not the specific words, but the mindset of the individuals involved. Once SJW's infect a project, it's all downhill from there.
- Likes 2
Comment
-
Originally posted by Fuchs View PostMy best guesses would be https://phabricator.kde.org/D12732 and https://phabricator.kde.org/D12795 given security was mentioned, and potentially, given the timing, https://phabricator.kde.org/T8707 with https://phabricator.kde.org/D13276, but that's guesses, there might be more and others.
I for one find it irritating when Dolphin doesn't/didn't have root access, and I think a warning is plenty sufficient (even if it's an annoying one that you can't get rid of). I understand his concerns, but I don't think he's weighing the situation correctly - pretty much the only people using Dolphin under root are people who own the PC in the first place, and know what they're doing. A hacker is going to use command-line tools, and someone who doesn't own the PC won't (or shouldn't) know the root password. His rambling about catering to every user's wish sounds more like a scapegoat to deliberate negligence; you have to go out of your way to prevent a program from running in root, so he's not just denying what users request, he's going against it (and from what I can tell, partially out of spite). I don't disagree with the security issues, but he's taking it a little too seriously.
As for the window border thing, I don't get what the advantage is of Martin's proposal, and I think he's blowing the situation way out of proportion. From what I can tell, it seems he's mostly just upset over VDG stepping on his turf, and he's being deliberately difficult as a result. Kind of irritating, since it seems that resulted in requesting to remove borders, which I'm not fond of.
Perhaps VDG isn't doing their job correctly, but I also think his bureaucracy is counter-productive.Last edited by schmidtbag; 04 June 2018, 10:16 AM.
- Likes 4
Comment
-
Originally posted by aufkrawall View PostQuality of Kwin on Xorg wasn't really satisfying, bugs didn't get fixed...
Hmmm...
Martins rather exuberant hatred of Nvidia and dislike of "obsolete technologies", like X, were not ideal...
A more neutral developer (or set of developers) would be a pleasant change.
But sadly we're loosing Martin's expertise... Hopefuly KWin won't be hit by a bus now...
- Likes 2
Comment
-
Originally posted by bobwya View PostBut sadly we're loosing Martin's expertise... Hopefuly KWin won't be hit by a bus now...
- Likes 3
Comment
-
Originally posted by Sho_ View PostThis is completely false information, and I am flabbergasted how this editorial mistake could arise.
- Likes 1
Comment
-
Originally posted by Awesomeness View Post
Yeah, how could it… your mail https://mail.kde.org/pipermail/plasm...ne/086122.html just has "Stepping down as maintainer" as headline…
That's how mailing lists work, rest assured that at least some clients will break if you alter the subject.
With that logic everybody replying to that thread would be stepping down as a maintainer.
And from a "news outlet", even a one man show like phoronix, I expect a bit more research than just reading mail subjects before handing out false news that are quite the opposite of what actually happened. At least it was corrected quickly.
kr
Fuchs
- Likes 4
Comment
-
Originally posted by SpyroRyder View PostThen again sometimes even security changes should have more discussion before becoming final, like with the recent furore around Nautilus's ability to execute files.
Comment
-
Originally posted by ngraham View PostWait, what? What features did we remove?
Originally posted by ngraham View PostHalf of the goal of the Usability & Productivity initiative is to make KDE Plasma a good desktop for power users.
Originally posted by ngraham View PostWhat can we do better?
- Likes 4
Comment
-
I think this was the right decision. Reading through his explanation, it's clear that he was becoming frustrated by having to justify saying no as maintainer, but that's the most important part of it. Not just saying no - explaining why it's such a bad idea that it can't be accepted, and helping provide a way forward that works for everyone. Providing no explanation just spreads the frustration around to everyone else.
Having not worked with the VDG, I don't think anyone here can really properly evaluate if his criticisms are accurate or not. Certainly some of what he says sounds unfortunate, but it's difficult for an outsider to judge if he's overstating his case or not. I do think there is a valid argument to focus on making the majority of your userbase happy while ignoring the 1% who moan the loudest, but I also think that a focus on bug-fixing and polishing over core new features is absolutely needed as well.
Hopefully kwin as a project keeps humming along without too much disruption due to this.
- Likes 1
Comment
Comment