Announcement

Collapse
No announcement yet.

GNOME & Intel Developers Plan The Wayland Future

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

  • Originally posted by Honton View Post
    Are you saying Gnome should bend because some KDE feel like they are bending too much? That is wrong on so many levels.
    What you call ?bending? normal people refer to as compromise.

    Comment


    • Originally posted by danielnez1 View Post
      Why don't you have a whinge about Red Hat's CLA while you are at it then?
      As crappy as Gnome's mindset is, RH's CLA simply states that any software contributed to Fedora that has no license defined automatically falls under MIT License. Source code with no license specified is proprietary as international copyright law states.

      Comment


      • oh great... gnome is involved. That translates to:
        mandatory depending on systemd
        breaking abis and apis every odd week
        trying to force something like gconf
        and abandom it, as soon as it starts working reliabely.

        Oh, and:
        remove as much options and functionality as possible, while gobbling down RAM like there is no tomorrow.

        Did I forget something?

        Comment


        • Originally posted by TheBlackCat View Post
          Not really. With copyright assignment, they own the copyright, meaning you no longer have any rights to it at all. With a license agreement, it gives them additional rights, but does not take away any of your existing rights. You can still do whatever you want with the code.
          Digia is a Finnish company. Within the EU it's simply impossible to assign copyrights (German ?Urheberrecht? vs. ?Verwertungsrecht? is a more clear distinction in this case). However, that's not the point, even though Gnome fanboys tend to concentrate on it and try to get others into irrelevant details and lose the overal picture. Gnome does not need to contribute to upstream Qt to use it or allow it as external dependency, just as Gnome-DB supports MySQL and MariaDB despite CLAs.
          Gnome simply treats Mono and Qt different just because Mono was developed by Gnome's founder whereas hostility towards Qt is the whole reason Gnome even exists.

          Comment


          • Originally posted by energyman View Post
            oh great... gnome is involved.[?]
            Did I forget something?
            Gnome fanboys overstate their involvement with Wayland. Most Code in Wayland so far was produced by Intel and Collabora.

            Comment


            • Originally posted by energyman View Post
              oh great... gnome is involved. That translates to:
              mandatory depending on systemd
              Yet another myth. GNOME has no dependency on systemd at all. It depends on a D-Bus layer, one implementation is systemd but Ubuntu for instance has implemented the same D-Bus API without using systemd. Arch before switching to systemd itself used to do the same thing as well. You can find the documentation about the API and alternative implementations at

              Comment


              • Originally posted by energyman View Post
                breaking abis and apis every odd week
                trying to force something like gconf
                and abandom it, as soon as it starts working reliabely.
                ABI and API compatibility is very well maintained by the core libraries. If you are talking about something like theming, that isn't part of ABI or API. gconf was maintained upstreamfor atleast a decade and continues to maintained by distributions such as RHEL. The problems observed over that maintenance period was fixed using dconf in GNOME 3, which allows for a ABI break because it is a new major release.

                Comment


                • Originally posted by Awesomeness View Post
                  Gnome does not need to contribute to upstream Qt to use it or allow it as external dependency, just as Gnome-DB supports MySQL and MariaDB despite CLAs
                  GNOME DB itself is not part of the official release. What it depends on isn't very relevant to a conversation about CLA. GNOME as a project wouldn't use Qt as a dependency just like KDE as a project wouldn't depend on GTK. I wouldn't expect anything else from either projects.

                  Comment


                  • Originally posted by energyman View Post
                    oh great... gnome is involved. That translates to:
                    mandatory depending on systemd
                    breaking abis and apis every odd week
                    trying to force something like gconf
                    and abandom it, as soon as it starts working reliabely.

                    Oh, and:
                    remove as much options and functionality as possible, while gobbling down RAM like there is no tomorrow.

                    Did I forget something?
                    No, I think you got it spot on .

                    Comment


                    • Originally posted by RahulSundaram View Post
                      GNOME as a project wouldn't use Qt as a dependency just like KDE as a project wouldn't depend on GTK.
                      Plenty of KDE subprojects depend on glib which represents back-end stuff of GTK just as Qt has non-GUI modules but Gnome would never ever depend on them because Gnome people are arrogant NIH pricks.

                      Comment

                      Working...
                      X