logo

drewdevault.com

[mirror] blog and personal website of Drew DeVault git clone https://hacktivis.me/git/mirror/drewdevault.com.git

FOSS-is-to-surrender-your-monopoly.md (5184B)

    

  1. ---
  2. title: Open source means surrendering your monopoly over commercial exploitation
  3. date: 2021-01-20
  4. outputs: [html, gemtext]
  5. ---
  7. Participation in open source requires you to surrender your monopoly over
  8. commercial exploitation. This is a profound point about free and open source
  9. software which seems to be causing a lot of companies to struggle with their
  10. understanding of the philosophy of FOSS, and it's worth addressing on its own.
  11. It has been apparent for some years now that FOSS is eating the software world,
  12. and corporations are trying to figure out their relationship with it. One fact
  13. that you will have to confront in this position is that you cannot monopolize
  14. the commercial potential of free and open source software.
  16. The term "open source" is broadly accepted as being defined by the [Open Source
  17. Definition][0], and its very first requirement is the following:
  19. [0]: https://opensource.org/osd
  21. > [The distribution terms of open-source software] shall not restrict any party
  22. > from selling or giving away the software as a component of an aggregate
  23. > software distribution containing programs from several different sources. The
  24. > license shall not require a royalty or other fee for such sale.
  26. That covers the "OSS" in "FOSS". The "F" refers to "free software", and is
  27. covered by [this Free Software Foundation resource][1]:
  29. [1]: https://www.gnu.org/philosophy/free-sw.html
  31. > [A program is free software if the program's users have] the freedom to run
  32. > the program as they wish, for any purpose, [... and to ...] redistribute
  33. > copies.
  35. It further clarifies the commercial aspect of this freedom explicitly:
  37. > “Free software” does not mean “noncommercial”. A free program must be
  38. > available for commercial use, commercial development, and commercial
  39. > distribution. [...] Regardless of how you got your copies, you always have the
  40. > freedom to copy and change the software, [and] to sell copies.
  42. This is an essential, non-negotiable requirement of free and open-source
  43. software, and a reality you must face if you want to reap the benefits of the
  44. FOSS ecosystem. *Anyone* can monetize your code. That includes you, and me, all
  45. of your contributors, your competitors, Amazon and Google, and everyone else.
  46. This is a rejection of how intellectual property typically works —
  47. copyright laws exist for the express purpose of creating an artificial monopoly
  48. for your business, and FOSS licenses exist for the express purpose of breaking
  49. it. If you're new to FOSS, it is going to be totally alien to your understanding
  50. of IP ownership.
  52. It's quite common for people other than you to make money from your free and
  53. open source software works. Some will incorporate them into their own products
  54. to sell, some will develop an expertise with it and sell their skills as a
  55. consultant, some will re-package it in an easy-to-use fashion and charge people
  56. for the service. Others might come up with even more creative ways to monetize
  57. the software, like writing books about it. It will create wealth for everyone,
  58. not just the original authors. And if you want it to create wealth for *you*,
  59. you are responsible for figuring out how. Building a business requires more work
  60. than just writing the software.
  62. This makes sense in terms of karmic justice, as it were. One of the most
  63. important advantages of making your software FOSS is that the global community
  64. can contribute improvements back to it. The software becomes more than your
  65. organization can make it alone, both through direct contributions to your code,
  66. and through the community which blossoms around it. If the sum of its value is
  67. no longer entirely accountable to your organization, is it not fair that the
  68. commercial exploitation of that value shouldn't be entirely captured by your
  69. organization, either? This is the deal that you make when you choose FOSS.
  71. There are ways that you can influence how others use your FOSS software, mainly
  72. having to do with making sure that everyone else keeps this same promise. You
  73. cannot stop someone from making money from your software, but you *can* obligate
  74. them to share their improvements with everyone else, which you can incorporate
  75. back into the original product to make it more compelling for everyone. The [GPL
  76. family of licenses][2] is designed for this purpose.[^1]
  78. [2]: https://www.gnu.org/licenses/
  79. [^1]: If you want a brief introduction to GPL licenses, I have written [a short guide for SourceHut users](https://man.sr.ht/license.md).
  81. Furthermore, if your business is a consumer of free and open source software,
  82. rather than a producer, you need to be aware that you may be subject to those
  83. obligations. It's not a free lunch: you may be required to return your
  84. improvements to the community. FOSS licenses are important, and you should make
  85. it your business to understand them, both as a user, contributor, and author of
  86. free and open source software.
  88. FOSS is eating the world, and it's a very attractive choice for businesses for a
  89. good reason. This is the reason. It increases wealth for everyone. Capitalism
  90. concerns itself with making monopolies — FOSS instead concerns itself with
  91. the socialized creation of software wealth.