Language Selection

English French German Italian Portuguese Spanish

A cure for unfair competition in open source

Filed under
OSS
Drupal

In many ways, open source has won. Most people know that open source provides better quality software, at a lower cost, without vendor lock-in. But despite open source being widely adopted and more than 30 years old, scaling and sustaining open source projects remain challenging.

Not a week goes by that I don’t get asked a question about open source sustainability. How do you get others to contribute? How do you get funding for open source work? But also, how do you protect against others monetizing your open source work without contributing back? And what do you think of MongoDB, Cockroach Labs, or Elastic changing their license away from open source?

This article (in five parts) talks about how we can make it easier to scale and sustain open source projects, open source companies, and open source ecosystems.

Read more

Part 2 From Dries Buytaert on Parasites That Hurt FOSS

  • How takers hurt makers in open source

    In part 1 of this article, I introduced the concept of open source Makers and Takers, and explained why it is important to find new ways to scale and sustain open source communities. Here in part 2, I’ll dive into why Takers hurt Makers, as well as how the “prisoner’s dilemma” affects the behavior of takers.

    To be financially successful, many Makers mix open source contributions with commercial offerings. Their commercial offerings usually take the form of proprietary or closed source IP, which may include a combination of premium features and hosted services that offer performance, scalability, availability, productivity, and security assurances. This is known as the open core business model. Some Makers offer professional services, including maintenance and support assurances.

    When Makers start to grow and demonstrate financial success, the open source project that they are associated with begins to attract Takers. Takers will usually enter the ecosystem with a commercial offering comparable to the Makers’ but without making a similar investment in open source contribution. Because Takers don’t contribute back meaningfully to the open source project that they take from, they can focus disproportionately on their own commercial growth.

Last part of the series in which Drupal's founder explains FOSS

  • 3 suggestions for stronger open source projects

    If, like most economic theorists, you believe that organizations act in their own self-interest, we should appeal to that self-interest and better explain the benefits of contributing to open source.

    Despite the fact that hundreds of articles have been written about the benefits of contributing to open source—highlighting speed of innovation, recruiting advantages, market credibility, and more—many organizations still miss these larger points.
    It’s important to keep sharing open source success stories. One thing that we have not done enough is appeal to organizations’ fairness principles.

    While a lot of economic theories correctly assume that most organizations are self-interested, I believe some organizations are also driven by fairness considerations.

    Despite the term Takers having a negative connotation, it does not assume malice. For many organizations, it is not apparent if an open source project needs help with maintenance, or how one’s actions, or inactions, might negatively affect an open source project.

    As mentioned, Acquia is a heavy user of Varnish Cache. But as Acquia’s chief technology officer, I don’t know if Varnish needs maintenance help, or how our lack of contribution negatively affects Makers in the Varnish community.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

7 Linux Distros to Look Forward in 2021

Here is a list of most anticipated Linux distributions you should keep an eye on in the year 2021. Read more

Games Leftovers

  • Gaming Like It's 1925: Last Week To Join The Public Domain Game Jam!

    Sign up for the Public Domain Game Jam on itch.io »

  • ujoy(4) added to -current

    With the following commit, Thomas Frohwein (thfr@) added a joystick/gamecontroller driver to -current: [...]

  • The First Online Conference Is Happening Today For The Godot Game Engine - Phoronix

    For those interested in Godot as the premiere open-source 2D/3D game engine or just looking for some interesting technical talks to enjoy this weekend, the first GodotCon Online is today. GodotCon 2021 is the open-source game engine's first entirely online conference for developers, users, and other contributors to this promising open-source project. The YouTube-based event has been running from 8:45 UTC today until 16:00 UTC, but fear not if you missed out as you can already go back and listen to the prior talks in the stream. The recordings will remain available for those wanting to enjoy it in the days ahead. All of the content is free of charge.

Programming Leftovers

  • How to test PHP code using PHPUnit - Anto ./ Online

    PHPUnit automatically executable tests that verify your application’s behavior. Thus – you can ensure that your changes don’t break existing functionality. This post will show you how to test your PHP code using PHPUnit.

  • Latency Numbers Every Team Should Know

    We design systems around the size of delays that are expected. You may have seen the popular table “latency numbers every programmer should know” which lists some delays that are significant in technology systems we build. Teams are systems too. Delays in operations that teams need to perform regularly are significant to their effectiveness. We should know what they are. Ssh to a server on the other side of the world and you will feel frustration; delay in the feedback loop from keypress to that character displayed on the screen. Here’s some important feedback loops for a team, with feasible delays. I’d consider these delays tolerable by a team doing their best work (in contexts I’ve worked in). Some teams can do better, lots do worse. [...] In recent times you may have experienced the challenge of having conversations over video links with significant delays. This is even harder when the delay is variable. It’s hard to avoid talking over each other. Similarly, it’s pretty bad if we know it’s going to take all day to deploy a change to production. But it’s so worse if we think we can do it in 10 minutes, when it actually ends up taking all day. Flaky deployment checks, environment problems, change conflicts create unpredictable delays. It’s hard to get anything done when we don’t know what to expect. Like trying to hold a video conversation with someone on a train that’s passing through the occasional tunnel.

  • How I programmed a virtual gift exchange

    Every year, my wife's book club has a book exchange during the holidays. Due to the need to maintain physical distance in 2020, I created an online gift exchange for them to use during a book club videoconference. Apparently, the virtual book exchange worked out (at least, I received kind compliments from the book club members), so I decided to share this simple little hack.

  • Dirk Eddelbuettel: prrd 0.0.4: More tweaks

    The key idea of prrd is simple, and described in some more detail on its webpage and its GitHub repo. Reverse dependency checks are an important part of package development that is easily done in a (serial) loop. But these checks are also generally embarassingly parallel as there is no or little interdependency between them (besides maybe shared build depedencies). See the (dated) screenshot (running six parallel workers, arranged in split byobu session). This release brings several smaller tweaks and improvements to the summary report that had accumulated in my use since the last release last April. We also updated the CI runners as one does these days.

  • vrurg: A New Release Of Cro::RPC::JSON

    I don’t usually announce regular releases of my modules. But not this time. I start this new year with the new v0.1 branch of Cro::RPC::JSON. Version 0.1.1 is currently available on CPAN (will likely be replaced with fez as soon as it is ready). The release is a result of so extensive changes in the module that I had to bump its :api version to 2.

  • gfldex: Anonymous slurpers

    I have a script where I’m only interested in the last two lines of its output.

Nouveau X.Org Driver Sees First Release In Two Years

Two years and nine patches later, xf86-video-nouveau 1.0.17 is out as the latest X.Org driver update for this open-source NVIDIA driver component. Like the other DDX drivers with the exception of the generic xf86-video-modesetting driver that is quite common now to those still running on X.Org with the open-source stack, xf86-video-nouveau seldom sees new activity. Since the prior v1.0.16 release two years ago there has been less than a dozen patches for it. The interesting activity happens in DRM/KMS kernel space and an increasing number of users are just relying upon xf86-video-modesetting over these hardware-specific X.Org user-space drivers. Read more