this post was submitted on 13 Jul 2023
60 points (96.9% liked)

Linux

48331 readers
1137 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

A lot of debate today about "community" vs "corporate"-driven distributions. I (think I) understand the basic difference between the two, but what confuses me is when I read, for example:

...distro X is a community-driven distribution based on Ubuntu...

Now, from what I understand, Ubuntu is corporate-driven (Canonical). So in which sense is distro X above "community-driven", if it's based on Ubuntu? And more concretely: what would happen to distribution X if Canonical suddeny made Ubuntu closed-source? (Edit: from the nice explanations below, this example with Ubuntu is not fully realistic – but I hope you get my point.)

Possibly my question doesn't make full sense because I don't understand the whole topic. Apologies in that case – I'm here to learn. Cheers!

top 31 comments
sorted by: hot top controversial new old
[–] Raphael@lemmy.world 34 points 1 year ago* (last edited 1 year ago) (7 children)

You are correct, distributions like Kubuntu are not TRULY community-driven as they are still subject to Canonical's influence. Anyone saying otherwise is merely being pedantic.

However it's not Canonical who's running Kubuntu, it's the community, they have the power to revert Canonical's bad decisions, sadly by giving themselves an increasingly higher workload. Most distributions will simply give up at some point, for example VanillaOS' next release will be based on Debian as it was getting too tough to remove snap and all the bad things Canonical adds.

Kubuntu uses snaps which are largely disrespected by the community, that's the end result of being under Canonical's influence. They can't rebase on Debian without effectively killing their raison d'etre and they don't want to remove Snap, perhaps because it would be difficult but most likely because they're deep under Canonical's influence, they look up to Canonical to some extent.

This is, in fact, the very meaning of "influence". It's even worse, in fact, much, much worse for Fedora, they have been culturally enslaved by Red Hat, sorry for the strong word.

[–] pglpm@lemmy.ca 3 points 1 year ago

Thank you for the clarification! – And for the extra info about snaps, which was something else I was wondering about too (I use Kubuntu at the moment)!

load more comments (6 replies)
[–] lvxferre@lemmy.ml 18 points 1 year ago (1 children)

It boils down to who and why someone is distributing the software to you. A corporation expects to eventually get some profits out of its actions, so it'll sometimes do things against the best interests of the users, because they benefit itself; on the other hand you expect a community-driven distro to be made by a bunch of people who just want to use the software, and have a vision on how it's supposed to be.

Canonical suddeny made Ubuntu closed-source?

Canonical can't make Ubuntu closed-source. Most of the code in Ubuntu was not made by Canonical, but by third party developers; Canonical is just grabbing that code and gluing it together into a distro. And most of those third party devs released their code as open source, and under the condition that derivative works should be also open source (the GNU General Public License - note, I'm oversimplifying it).

What Canonical could do is to exploit some loophole of the license in the software from those third party devs; that's basically what Red Hat is trying to do. In the short term, people would likely shift to Linux Mint (itself an Ubuntu fork) or make their own forks; and in the long term, fork another Debian derivative to build their new distros from it. (Or adopt Linux Mint Debian Edition.)

[–] pglpm@lemmy.ca 4 points 1 year ago

Thank you – Canonical & Ubuntu's situation was unclear to me indeed, thank you for the clarification! My example was poorly chosen.

[–] poVoq@slrpnk.net 8 points 1 year ago* (last edited 1 year ago) (1 children)

Even in community driven distro there are often many contributors that do so because parts of their livelihood depend on it. So it is not quite fair to say that there are no financial incentives behind it.

Its basically a question of relative scale. If there are lots of smaller companies and some hobbiists contributing it is called community driven, but if a single large company or their employees run most of the show, it is not.

Large gray area to be honest.

[–] pglpm@lemmy.ca 4 points 1 year ago (1 children)

Absolutely fair point and warning. In the end we all need to earn money somewhere in order to live. I think the real greyscale distinction is not between "corporate" vs "community", but on whether there's some actor that can act whimsically while remaining unchecked. I believe that the two terms are being used in an oversimplified way in that sense.

[–] nan@lemmy.blahaj.zone 4 points 1 year ago* (last edited 1 year ago) (1 children)

I don’t think looking at the power of “some actor” is a good way either. Many community projects are led by benevolent dictators, they are even in the history of projects like Debian (Ian Murdock) and Gentoo (Daniel Robbins). Many forks of things happen because people disagree with that leader or they go missing.

I think the easiest distinction is to look at who actually builds the product that is released. RHEL development happens in the open in CentOS Stream, but package selection, stabilization, release engineering, etc are done by employees within the corporation. In Fedora this is accomplished by committees and contributors who work the role. Even though Red Hat financially sponsors Fedora these are usually not employees. In something like Arch or Debian this is even more the case.

[–] pglpm@lemmy.ca 2 points 1 year ago

True that too. I'm realizing it's really a matter and situation with many diverse important factors and degrees. As always, categorization only goes so far...

[–] Gsus4@lemmy.one 7 points 1 year ago* (last edited 1 year ago) (2 children)

E.g. Wikipedia is community-driven because people contribute individually without a lot of coordination and without anybody telling contributors what to do, same for game mods. I guess by "corporate-driven" you mean there is a hierarchy and people whose job it is to do what management says e.g. Wikipedia foundation runs the infrastructure that hosts the community content and the same for most games. I'm not sure I'd call it "corporate driven" unless it has board members and investors demanding a profit such that they influence the decisions downstream, like reddit.

[–] nan@lemmy.blahaj.zone 7 points 1 year ago* (last edited 1 year ago) (1 children)

Community vs corporate comes down to profit and legal organization, but not so much a lack of organization or hierarchy. Debian is very organized and has leadership, elected in Debian but that is not always the case (Theo de Raadt at OpenBSD, Clément Lefèbvre at Linux Mint). There are still people who are paid to work on community projects even.

Then you sometimes also have weird ones, like Mozilla, where the product (Firefox) is made by a for-profit Corporation that is owned by the non-profit Foundation.

[–] Gsus4@lemmy.one 4 points 1 year ago

Great examples there, particularly firefox. The moral here is that there is no black-and-white or even a spectrum from community to corporate, but a set of incentive structures from the bottom to the top that are set up to maximize the likelihood that a product will reach its originally desired behaviour towards the community or the investors.

[–] pglpm@lemmy.ca 2 points 1 year ago

Indeed I didn't really mean to use these terms in a precise way, since my understanding of the matter is very supericial. I was using terms that I read around posts and net. With all these replies I see that there are a lot of grey areas, and a strict dichotomy or classification is meaningless...

[–] theTrainMan932@infosec.pub 5 points 1 year ago (2 children)

From what I understand and to continue your example of Ubuntu-based distros:

As you say, Ubuntu itself is corporate-driven, so there are things in there that exist pretty much solely to benefit Canonical (e.g the telemetry they recently introduced if i recall correctly)

Most of the time when basing distros off of others, I think it's to keep a lot of features - either to save dev time or because they only want to tweak a small portion of the distro and not write a new one from scratch.

Because devs can modify the entire codebase, they can remove features that are corporate-driven (telemetry and such) and effectively create something fully (or mostly) compatible yet without such features.

Another major example imo is the removal of snaps, which most people (myself included) strongly dislike - as far as I'm aware removing them in Ubuntu itself is quite a difficult process as it's baked into the distro itself. I imagine a lot of people want something like Ubuntu as it is quite friendly and has one of the lower bars of entry for Linux, but object to corporate things like telemetry and the overall monstrosity that is snaps.

Apologies, i went down a bit of a tangent, but I hope that roughly answers your question!

[–] pglpm@lemmy.ca 5 points 1 year ago (1 children)

Cheers – the "snap tangent" is something I wanted to understand as well.

[–] Raphael@lemmy.world 4 points 1 year ago (3 children)

This is something I posted in another thread, it works under the assumption snaps are a far inferior technology when compared to flatpak, it leaves implicit Canonical's unreasonable approach at pushing snap and doesn't even mention the fact snap has a proprietary server component. Really? Why? Why would a linux corporation NOT publish server code? It's ridiculous, isn't it?

Now on to the post:

Companies like Red Hat, OpenSUSE and Canonical are not only trying to sell support but also convince others that they are innovating. Red Hat kickstarted Flatpak and then Canonical, who didn’t want to “lose” decided to push their own thing, Snap with the strength of ten thousand suns. Naturally, this is a simplified explanation, Snap already was in development at the time but if we truly followed the spirit of open source, Canonical would have dropped it and adopted Flatpak instead.

OpenSUSE has quite a few products in the kubernetes sector, even Oracle has its own things they can brag about. Canonical has basically nothing and this is why they’re pushing snap as if their lives depended on it.

Remember, Linus didn’t write an OS because the GNU folks were writing one, GNU didn’t write a new kernel after theirs failed, because Linus had a working one. This is the nature of free software, Canonical has completely forgotten about it. Red Hat now too.

[–] nan@lemmy.blahaj.zone 4 points 1 year ago (1 children)

I know it’s an oversight, but openSUSE and SUSE are not the same entity. openSUSE is a community project, they are sponsored by multiple corporations and individuals including SUSE (somewhat different than Fedora which is only sponsored by Red Hat).

[–] Raphael@lemmy.world 2 points 1 year ago

Oversight indeed, habits.

[–] stsquad@lemmy.ml 2 points 1 year ago (1 children)

I don't think it's quite as simple as that. Both flatpak and snaps use similar technologies but have divergent visions on the user experience. It's not like RedHat fell in line and adopted upstart rather than developing systemd. There has to be space for competing approaches to the same problems rather than forcing everyone into an open source monoculture. I know people decry the wasted effort but it's not like you can force open source developers to work on your preferred solution.

[–] Raphael@lemmy.world 0 points 1 year ago

Open source developers? I'm talking about Canonical Ltd. employees.

[–] pglpm@lemmy.ca 1 points 1 year ago

Cheers, I had absolutely no idea about these marketing/competition sides of snaps and flatpaks...

[–] Unaware7013@kbin.social 4 points 1 year ago (1 children)

Would you be able to keep going on your snap tanget? I'm mainly a windows dude and only dabble in Linux, so I'm curious as to the strong feelings there.

[–] theTrainMan932@infosec.pub 3 points 1 year ago

Motivations by the company have been explained far better than I could by the other replies, but from both mine and other people's experience, some software when installed via snaps seems to perform badly compared to any other method of installation (notably chrome and firefox i think). Also snap isn't really bringing anything special to the table whereas flatpak has a more interesting containerised approach from what I'm aware.

In any case with the way ubuntu's going I'm really not over the moon with anything canonical (and i don't think I'm alone)

[–] Animortis@kbin.social 4 points 1 year ago

Additional community distros not mentioned: OpenMandriva, PCLinuxOS, Mageia, NixOS.

[–] QuazarOmega@lemmy.world 3 points 1 year ago* (last edited 1 year ago) (1 children)

It still qualifies as community driven since they have no financial incentive to keep maintaining their version of the distribution, but they would certainly be affected by the upstream messing with how the source is provided. What they could ultimately do would be "hard forking", i.e. taking the available state of the original project and keep developing their own version on top without ever keeping in sync with, say, Ubuntu anymore. Instead they will become their own thing that at some point will have strayed from the original significantly enough to be fundamentally different in their packages, configurations, repositories, etc.

[–] pglpm@lemmy.ca 1 points 1 year ago

Thank you. So in theory the community-driven derivatives are always free, at least in theory, not to depend from the upstream corporation-driven ones. So it's more a matter of possible implications in the workflow, than in not being really community-driven.

[–] milicent_bystandr@lemmy.ml 1 points 1 year ago

what would happen to distribution X if Canonical suddeny made Ubuntu closed-source?

I believe Linux Mint has done some planning for if Ubuntu does something like that - probably to rebase off Debian in that case

[–] Raphael@lemmy.world 0 points 1 year ago* (last edited 1 year ago)

You are correct, distributions like Kubuntu are not TRULY community-driven as they are still subject to Canonical's influence. Anyone saying otherwise is merely being pedantic.

However it's not Canonical who's running Kubuntu, it's the community, they have the power to revert Canonical's bad decisions, sadly by giving themselves an increasingly higher workload. Most distributions will simply give up at some point, for example VanillaOS' next release will be based on Debian as it was getting too tough to remove snap and all the bad things Canonical adds.

Kubuntu uses snaps which are largely disrespected by the community, that's the end result of being under Canonical's influence. They can't rebase on Debian without effectively killing their raison d'etre and they don't want to remove Snap, perhaps because it would be difficult but most likely because they're deep under Canonical's influence, they look up to Canonical to some extent.

This is, in fact, the very meaning of "influence". It's even worse, in fact, much, much worse for Fedora, they have been culturally enslaved by Red Hat, sorry for the strong word.

load more comments
view more: next ›