Announcement

Collapse
No announcement yet.

Martin Flöser Steps Down As Maintainer Of KDE's KWin

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #71
    Originally posted by ngraham View Post
    In no way, shape, or form are we unaware of the criticisms or ignoring the issues.
    you very much do. Maybe not or less so user originating criticism, but the current MO of the VDG seems to be: someone has an idea which is seen as the best thing since sliced bread and accepted without even thinking of possible implications, if that idea follows current applications and or guidelines and if it fits the big picture. You then propose it and go full steam ahead, ignoring all arguments against it or replying with disbelief or "but x and y of the VDG all think it's better", which simply does not invalidate a technical argument.
    You ignore anything against it and push things forward against criticism and maintainers, this is what happened here, this is what drove and will drive people away.
    And then, later on, you might notice that it wasn't the best idea but then you can't go back.

    That's the picture I get by only reading a few of the tickets linked or mentioned.

    So in addition to the comments already made on what specifically you should change: how the VDG works. Maybe reflect, sit back and wait a bit more, and be more open minded and accepting to arguments that do not fit your current view of the issue at hand.

    And to answer your previous question (got eaten by forum filters, so I reply to it rather late): Hi Nate, I'm Daniel, I am "only" a concerned user and I don't think we met or know each other, no.

    Comment


    • #72
      Originally posted by nuetzel View Post

      We had ages of UI (lab) research.
      Lab research from the age before touchscreens. Quite a lot has changed in the past 10 years in how people use interfaces.

      Originally posted by nuetzel View Post
      Konsole without 'status bar'. - Horror.
      Wtf is a terminal status bar? I spend my day in the terminal running tmux and vim and I have no idea what you're talking about.

      Originally posted by nuetzel View Post
      We have knobs. - Like knives & forks. Generations of people have learned how to use them...
      The newest generation using computers grew up on touchscreens. Many of them don't own a mouse yet alone know what a middle mouse button is.

      Originally posted by nuetzel View Post
      I want to decide myself. - Or leave.
      I get it, you're one of those people who just generally don't like change. Maybe you should leave and use something classic like Xfce. No hard feelings.

      Comment


      • #73
        ngraham I learned about it only through some links posted here, and I dearly hope the decision to allow root user access for Kate and Dolphin will be revisited again at some point.

        Most users (even some devs) don't have the technical knowledge to understand that what they are doing when they run GUI apps as root is really bad. Quoting Emmanuele Bassi from Gnome, where there has been a similar discussion:
        there are no *real*, substantiated, technological reasons why anybody should run a GUI application as root. By running GUI applications as an admin user you're literally running millions of lines of code that have not been audited properly to run under elevated privileges; you're also running code that will touch files inside your $HOME and may change their ownership on the file system; connect, via IPC, to even more running code, etc. You're opening up a massive, gaping security hole
        It is technically just wrong, and no "please be careful" warning will heal that. Wouldn't it have been enough to introduce a compile time flag, as a convenience for Kali to not having to maintain their patch? I don't see any other recipient of these changes.

        (the changes in question are unrelated to sudo, it's really only about root user)

        Comment


        • #74
          Can we perhaps now have EGLStreams compatibility on KWin?

          Not that I ever intend to use the proprietary Nvidia driver (I'm saving for a GT 1030 to use with Nouveau, because I only need it to draw my desktop, so the locked clockspeeds do not affect me significantly), but it's really nice to have the option there in case I would ever need to resort to the proprietary driver.

          Comment


          • #75
            Originally posted by darclide View Post

            you very much do. Maybe not or less so user originating criticism, but the current MO of the VDG seems to be: someone has an idea which is seen as the best thing since sliced bread and accepted without even thinking of possible implications, if that idea follows current applications and or guidelines and if it fits the big picture. You then propose it and go full steam ahead, ignoring all arguments against it or replying with disbelief or "but x and y of the VDG all think it's better", which simply does not invalidate a technical argument.
            You ignore anything against it and push things forward against criticism and maintainers, this is what happened here, this is what drove and will drive people away.
            And then, later on, you might notice that it wasn't the best idea but then you can't go back.

            That's the picture I get by only reading a few of the tickets linked or mentioned.

            So in addition to the comments already made on what specifically you should change: how the VDG works. Maybe reflect, sit back and wait a bit more, and be more open minded and accepting to arguments that do not fit your current view of the issue at hand.

            And to answer your previous question (got eaten by forum filters, so I reply to it rather late): Hi Nate, I'm Daniel, I am "only" a concerned user and I don't think we met or know each other, no.
            I'd like to mention that if you're not actually involved as a KDE contributor, you're not getting the full picture. There's a lot of context that's not encapsulated by what's publicly visible--as always, when an institution's dirty laundry gets aired. Maintainers are not dictators, and it's especially unfair when people try to block changes in projects that they don't even contribute to. There's some history here that you may not be aware of.

            Nonetheless, we are working to improve the situation in several specific ways, including bringing stakeholders to the table earlier, formalizing our communication process, and working towards a unified vision again. I think we can find a way to advocate for the users without upsetting our developers (and to be fair to us, most are very engaged with us and we have great relationships; it was only a few who were complaining).

            Comment


            • #76
              the same guy who make a flame war because mir now gives up from wayland too, linux desktop is dead

              Comment


              • #77
                Originally posted by msotirov View Post
                Lab research from the age before touchscreens. Quite a lot has changed in the past 10 years in how people use interfaces.
                [-]
                Oh, I see your _desktop_ has a touch...

                Stop this stupid 'modern' is better attitude.
                It's so short jumping.

                Comment


                • #78
                  Originally posted by phoronix View Post
                  Phoronix: Martin Flöser Steps Down As Maintainer Of KDE's KWin

                  Martin Flöser (nee Gräßlin) who has been the maintainer of KDE's KWin since 2010 is leaving his post...

                  http://www.phoronix.com/scan.php?pag...aves-KWin-Post
                  Just a hunch, but I think this was in the making ever since he got married and changed his last name to Floser.. which is kind of strange, usually the bride takes the groom's last name, unless it's a cultural thing where he's from (Germany?). Maybe his family demands aren't leaving time for him to focus on KDE.

                  Comment


                  • #79
                    Originally posted by Fuchs View Post
                    My 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.
                    Hmm... I've got no horse in this race – haven't used KDE in years – but reading those threads, I definitely get a sense of designers saying "do this, it'll be easy", and expecting the developers to agree.

                    Design is *hard*, and one of the most critical bits of the job is to make sure you're on the same page as the technical experts... things which sound easy are often all but impossible, and difficult-sounding things can often be easier than you'd think. They *are* a pain in the neck some times... but all the design in the world ain't worth crap if nobody can implement it.

                    Comment


                    • #80
                      Originally posted by MartinN View Post

                      Just a hunch, but I think this was in the making ever since he got married and changed his last name to Floser.. which is kind of strange, usually the bride takes the groom's last name, unless it's a cultural thing where he's from (Germany?). Maybe his family demands aren't leaving time for him to focus on KDE.
                      I know many here in sweden that took the last name of the bride if they have a very common name then some take the less common name.

                      Comment

                      Working...
                      X