Announcement

Collapse
No announcement yet.

Canonical Is At Around 437 Employees, Pulled In $99M While Still Operating At A Loss

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

  • #21
    Originally posted by 144Hz View Post
    jacob or 3. Just nope out of something as unethical as CLA. And that’s how Canonical got shafted during their CLA year.

    Today Canonical are back on track working on neutral upstreams. So it’s really just a matter of standing your ground. Neutral ground.
    You've missed my point. There is no 3. No-one is going to say too bad, we can't have a CLA because such-and-such says so. By the way a CLA is not automatically unethical, the FSF has (or at least used to have) one too. The point being, an upstream project can institute a CLA if they wish, and they won't be going around asking everyone and their dog personally for permission. Within the established rules of the FOSS community, there are two and ONLY two possible avenues: either accept it, or fork it.

    Comment


    • #22
      airlied

      At least Canonical offers users a choice on what type of kernel they prefer, unlike RedHat...

      Comment


      • #23
        Originally posted by msotirov
        Stocks don't work that way. Shareholders don't get shit as long as they don't sell their stocks. Technically Red Hat can use the money to invest in buying Canonical if they want to.
        Buying a company that hasn't made a profit after 15 years and has no value would seem like a bad business decision.

        Originally posted by jacob View Post

        Frankly I don't get this obsession with Canonical's CLAs. They only ever come into play if you want your code to be merged by Canonical. You can still develop patches, fork, maintain your own version etc. without having to worry about a single CLA.
        Because it shows a lack of commitment to open source unless it benefits the company. The company at some point in future can relicense the project and make future improvements/fixes done by them closed-source.

        Comment


        • #24
          Originally posted by 144Hz View Post
          jacob. The Canonical case proves my point. They failed on all CLA project. Every single one. The rest of the community didn’t drink the koolaid.

          And you need to revisit the FSF case. They never asked for CLA.
          The FSF has a copyright assignment mechanism so it can make sure all code is under the GPL. That's probably where the confusion is, it's quite different to a contributor license agreement that Canonical has and still uses.

          Originally posted by Linuxxx View Post
          airlied

          At least Canonical offers users a choice on what type of kernel they prefer, unlike RedHat...
          What would Red Hat gain from offering different types of kernels?

          Comment


          • #25
            Originally posted by 144Hz View Post
            Britoid copyright assignment is not CLA. The difference becomes even more obvious when look at the different motivations. FSF wants to defend GLP. CLA project want to circumvent GPL.
            That's what I meant.

            Comment


            • #26
              Originally posted by msotirov
              Not all of them, Red Hat is still a publicly traded company. Technically 51% of shareholders must have sold to IBM for the takeover to be valid.
              You have no idea what you taking about, IBM paid cash to each shareholder directly, not IBM shares, Red Hat is a fully owned IBM entity, there are no Red Hat shareholders except IBM now. That is how stocks work.

              Comment


              • #27
                Originally posted by Britoid View Post

                What would Red Hat gain from offering different types of kernels?
                How about offering people who care about latency an appropiate kernel?

                You know, gamers, content creators, users who like to scroll websites without constant stutter; basically standard desktop users!

                All things RedHat obviously doesn't care about...

                Comment


                • #28
                  Originally posted by Linuxxx View Post

                  How about offering people who care about latency an appropiate kernel?

                  You know, gamers, content creators, users who like to scroll websites without constant stutter; basically standard desktop users!

                  All things RedHat obviously doesn't care about...
                  If that's not possible in the normal kernel then that's a bug that should be fixed, not worked around.

                  Comment


                  • #29
                    Originally posted by 144Hz View Post
                    jacob or 3. Just nope out of something as unethical as CLA. And that’s how Canonical got shafted during their CLA year.

                    Today Canonical are back on track working on neutral upstreams. So it’s really just a matter of standing your ground. Neutral ground.

                    Comment


                    • #30
                      Originally posted by Britoid View Post

                      If that's not possible in the normal kernel then that's a bug that should be fixed, not worked around.
                      Scheduler and governor settings, 1000/750/500/250hz timer frequency, etc. There are a lot of kernel dials to turn and tweak and some can only be done at compile time.

                      Basically, some things are in the normal kernel and it's on the distribution on whether they provide kernels with the dials turned to desktop and low-latency or if the users have to turn the dials themselves. Manjaro and Ubuntu are pretty good in that regard.

                      Comment

                      Working...
                      X