Red Hat Enterprise Linux 10 Dropping The X.Org Server Except For XWayland

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • oiaohm
    Senior Member
    • Mar 2017
    • 8469

    Originally posted by mSparks View Post
    For example?

    Because I only see Peter Hutterer - Senior Software Engineer - Red Hat and, Olivier Fourdan - Senior Software Engineer - Red Hat, José Expósito Red Hat consultant, Michel Dänzer – Principal Software Engineer – Red Hat

    making xwayland/ commits on that link.

    With some "special thanks" to Kenny Levinsen for their help in doing the things they couldn't.
    This you cherry picked again without making sure you were comparing apples with apples.


    Take both look at the commits from 1 Jan 2023 to 13 dec 2023.

    24 commits on the xserver branch vs over 200 in xwayland.

    There at least 8 times more commits into xwayland than xserver branch in the same time frame. So there is a lot more pages to read on the xwayland side to be sure you are getting the correct picture.

    mSparks you did not see any of the Sultan Alsawaf patches did you because you did not scroll back enough or you did not read the merge requests to see who in fact merged the items..
    TearFree with the modesetting driver suffers from inaccurate PresentCompleteNotify event timing, which leads to A/V de-synchronization with clients utilizing Present, among other problems. This turns out...

    Those merges Sultan Alsawaf into Xwayland that get interesting.
    Martin Roukala is not redhat instead is Valve. Yes it was Martin Roukala who is not Redhat who commited Sultan Alsawaf patches into xwayland. The more you look at that over 200 commits the more cases you find new code going into xwayland without going though Redhat staff.

    Yes redhat staff is faster at it most of the time than the alternative like Martin Roukala from Valve. So yes redhat is the dominate party approving merges because they are full time and can do it faster but they are not the only who are merge items into xwayland.

    Issue is xserver you are only seeing Redhat and Apple personal approving merges. Xwayland if you look you find Valve and other companies in the last 12 months approving merges without having to get Redhat rubber stamp..

    Lets say we say Redhat staff had to instant stop. Xwayland can progress forwards slower because there are source code maintainers who are not Redhat with authorization to merge items with the need skilled to review the items correctly. Xserver would in fact grind to a dead stop with only MacOS/Apple stuff getting in.

    Of course there is going to be other problems like at moment all CVE notices that is the 90 day heads up of a security problem in x.org xserver or xwayland in fact go to Redhat and nobody else. MacOS will get notified if CVE is directly about Xquartz.

    This is a big thing no Oracle/SUSE/CIO/Debian/distribution maintainer person get notified about new x11 protocol bugs found or x.org xserver source code issues from CVE. Only redhat core x.org/xwayland people get notified about this stuff.

    To get a reasonable idea what going on with open source project you normally have to look at 12 months worth of commits otherwise you will risk getting a very wrong idea.

    Yes 12 months of xserver commits vs 12 months of xwayland commits the xserver list is very short. xwayland list gets quite lot of reading to be sure you understand what is going on. Mostly due things like who was the party who merged the commit not being correctly shown at the overview.

    Comment

    • mSparks
      Senior Member
      • Oct 2007
      • 2102

      Originally posted by oiaohm View Post

      24 commits on the xserver branch vs over 200 in xwayland.

      And you think that is a "good thing" for xwayland?

      Originally posted by oiaohm View Post
      Lets say we say Redhat staff had to instant stop. Xwayland can progress forwards slower
      xorg-server will continue to work just fine, powering the worlds fastest supercomputers, and providing a flawless desktop experience.
      Wayland and Xwayland will continue to barely work at all, not be used for anything productive, and ignored by mostly everyone.

      Pretty much the same as if RH continue doing exactly what they have been doing.

      Originally posted by oiaohm View Post
      issue is xserver you are only seeing Redhat and Apple personal approving merges.
      The following people are in charge of directing changes
      https://www.x.org/wiki/BoardOfDirectors/
      ?Emma Anholt Google emma AT anholt DOT net Q1 2024
      ?Mark Filion Collabora mark DOT filion AT collabora DOT com Q1 2024
      ?Ricardo Garcia Igalia rgarcia AT igalia DOT com Q1 2024
      ?Arkadiusz Hiler CodeWeavers arek AT hiler DOT eu Q1 2025 Treasurer
      ?Christopher Michael Igalia cmichael AT igalia DOT com Q1 2025
      ?Lyude Paul Red Hat lyude AT redhat DOT com Q1 2025 Secretary
      Alyssa Rosenzweig Valve alyssa AT rosenzweig DOT io Q1 2024
      Daniel Vetter Intel daniel.vetter AT ffwll DOT ch Q1 2025
      Originally posted by oiaohm View Post
      like at moment all CVE notices that is the 90 day heads up of a security problem in x.org xserver or xwayland in fact go to Redhat and nobody else.
      Trend Micro Zero Day Initiative found the last few,



      RH maintain xwayland-server, why are you surprised they are the ones notified about it?



      But those fixes aren'y going in to any of the RedHat distros, only distros that keep their software up to date. FC39 is still on 1.20.14 with all those "CVEs" still active, RH10 will be based on FC40 with is 1.20.14.






      Comment

      Working...
      X