Announcement

Collapse
No announcement yet.

GNOME OS Is Taking Shape But Its To Serve For Testing The Desktop

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

  • #81
    Originally posted by 144Hz View Post
    Canonical devs also work on upstream projects like GNOME and Debian. It’s not Canonical vs the world. In fact they do awesome things.

    Canonical made mistakes when managers saw an opportunity to go CLA. Don’t blame the devs.

    TLDR; CLA is bad, mmmmmkay..
    TL/DR get lost troll. without Canonical gnome would be abandonware today. DdV had to fix 10 years of gnome devs incompetence and he is barely halfway to getting it to a usable state

    Comment


    • #82
      Originally posted by Giovanni Fabbro View Post

      Where is Flathub's server source code for their back-end build services? All I see is a manual review process by the admins, and a manifest is created that builds it automatically. Do THEY have a manifest and source code tree of what the service does to build those packages? All I see is references to them linking to your own github repo once you put a request in.
      Really you are being a fool who has not done homework.
      https://github.com/flathub/buildbot and there is the buildbot-config that contains the configuration files.

      Flathub for their back end build services is using buildbot with a few custom patches. This is being used todo so much automatic CI.
      The section on Flatpak Builder describes how to generate repositories. The resulting repository can be hosted on a web server for consumption by users. Important details: Flatpak repositories use a...


      The flathub repos themselves are run by upstream flat-manager.

      Even the flathub website is up in the flathub github account under linux-store-frontend.

      All the parts are there to setup up your own clone of flathub just there is not a nice unified instruction manual todo it.

      The core server stuff mostly does not have manifest because flatpak is not really for services.

      Comment


      • #83
        Originally posted by tildearrow View Post

        I'm doing exactly what 144Hz did to us in the KDE thread: invade territory.
        Like this is unfair, how come he and his whole clan (uid313 and Alexmitter) party and pee over the KDE thread and we can't?
        Writing about KDE Problems? Welcome to the 144Hz clan, whoever that is.
        Really, Why are KDE people so childish. Why do you take criticism of valid issues like someone insults your wife.

        If you don't like people writing about bad things like the poor code quality, bugs, How KDE gets threaten by the Qt Company, CLAs and the attitude of its Fanboys, then stop do bad things as a community. You just try to kill the messenger.

        Comment


        • #84
          Originally posted by Giovanni Fabbro View Post

          Many of the GNOME devs are RedHatters. Red Hat employees do more projects that benefit the entire Linux ecosystem than any other company. Canonical does their own projects to benefit themselves and their position more than anything else.
          I disagree.
          Red Hat employees do their own projects to benefit themselves and their position more than anything else. They don't care if the community picks it or not. It's just a happenstance, not an intention.
          They usually have debatable benefit (at best) for the users. Which is why they might benefit the community but not necessarily the Linux ecosystem as a whole.
          Canonical do their own projects to benefit users, which is why they greatly contribute to the Linux ecosystem in a very different way.

          In the end, there could be a balance and mutual benefits if Red Hat wasn't so arrogant and narrow minded. Red Hat could bring their dev-centric expertise and Canonical their understanding of the users. If Red Hat could be more pragmatic about users, and listen to Canonical (which has a proven track of successfully breaking entry barriers to Linux), Canonical would probably have no reason to develop their own thing as they could satisfy their users without going their own way.

          When you clearly understand the users better, but are not listened to, why would you take the path that is not focused towards users at the risk of pushing them away? It makes no sense. Canonical have valid reasons to follow their ideas.

          Comment


          • #85
            Gnome, Meh.

            Comment


            • #86
              Gnome is the only Wayland stacking DE that runs just about everything right now. And that is reason enough for me to keep using it.

              KDE on Wayland still refuses to run Firefox Wayland, Chromium Ozone on Wayland backend, and a bunch of other stuff juust to name a few.

              Comment


              • #87
                Originally posted by Alexmitter View Post
                Really, Why is 144Hz clan so childish. Why do you take criticism of valid issues like someone insults your wife.

                If you don't like people writing about bad things like the poor usability, annoyances, How GNOME gets threaten by the SJWs, waste of time (rather than using it in fixing aforementioned issues) and the attitude of The Crusade, then stop do bad things as a community. You just try to kill the messenger.
                Fixed.

                Comment


                • #88
                  Originally posted by Sonadow View Post

                  KDE on Wayland still refuses to run Firefox Wayland, Chromium Ozone on Wayland backend, and a bunch of other stuff juust to name a few.
                  ???
                  What on earth are you talking about? All these things run fine on KDE wayland.

                  Comment


                  • #89
                    Originally posted by RahulSundaram View Post

                    I do read it regularly and you still haven't provided a single link to validate your claims
                    Try looking up the build process for Silverblue. The discussion started around that.

                    Comment


                    • #90
                      Originally posted by bregma View Post
                      You have it completely backwards. BSD and other licenses care about maximizing the freedom of the developer. The intent of the GPL is to maximize the freedom of the user of the software.
                      Absolute 100% BALDERDASH.

                      BSD gives the user the freedom to do whatever the hell they want with the software, including being able to make modifications closed-source as they see fit. GPL limits what a user can and can't do with the software, thus maintaining credit to the original developer under the same source code, including modifications as per GPLv3. That's IS NOT a freedom unto the user. This is why BSD is known as a "permissive" open source license, while GPL is known as restrictive. It's right there on Wikipedia.

                      Comment

                      Working...
                      X