logo

drewdevault.com

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

Open-source-is-defined-by-the-OSD.md (8283B)


  1. ---
  2. title: Open Source is defined by the OSI's Open Source Definition
  3. date: 2022-03-01
  4. outputs: [html, gemtext]
  5. ---
  6. The [Open Source Initiative] (OSI) publishes a document called the [Open Source
  7. Definition] (OSD), which defines the term "open source". However, there is a
  8. small minority of viewpoints within the software community which wishes that
  9. this were not so. The most concerning among them are those who wish open source
  10. was more commercially favorable to *themselves*, and themselves alone, such as
  11. companies like Elastic.
  12. [Open Source Initiative]: https://opensource.org
  13. [Open Source Definition]: https://opensource.org/osd
  14. I disagree with this perspective, and I'd like take a few minutes today to
  15. explore several of the most common arguments in favor of this view, and explain
  16. why I don't agree with them. One of the most frustrating complications in this
  17. discussion is the context of [motivated reasoning] ([relevant xkcd]): most
  18. people arguing in favor of an unorthodox definition of "open source" have a
  19. vested interest in their alternative view.[^bias] This makes it difficult to
  20. presume good faith. For example, say someone wants to portray their software as
  21. open source even if it prohibits commercial use by third parties, which would
  22. normally disqualify it as such. Their interpretation serves to re-enforce their
  23. commercialization plans, providing a direct financial incentive not only for
  24. them to promote this definition of "open source", but also for them to convince
  25. you that their interpretation is valid.
  26. [motivated reasoning]: https://en.wikipedia.org/wiki/Motivated_reasoning
  27. [relevant xkcd]: https://xkcd.com/2167
  28. [^bias]: Am I similarly biased? I also make my living from open source software,
  29. but I take special care to place the community's interests above my own. I
  30. advocate for open source and free software principles in all software,
  31. including software I don't personally use or benefit from, and in my own
  32. software I don't ask contributors to sign a CLA — keeping the copyrights
  33. collectively held by the community at large, and limiting my access to
  34. commercialization to the same rules of open source that are granted to all
  35. contributors to and users of the software I use, write, and contribute to.
  36. I find this argument to be fundamentally dishonest. Let me illustrate this with
  37. an analogy. Consider [PostgreSQL]. If I were to develop a new program called
  38. Postgres which was similar to PostgreSQL, but different in some important ways
  39. — let's say it's a proprietary, paid, hosted database service — that
  40. would be problematic. The industry understands that "Postgres" refers to the
  41. popular open source database engine, and by re-using their name I am diluting
  42. the brand of Postgres. It can be inferred that my reasoning for this comes from
  43. the desire to utilize their brand power for personal commercial gain. The terms
  44. "Postgres" and "PostgreSQL" are trademarked, but even if they were not, this
  45. approach would be dishonest and ethically wrong.
  46. [PostgreSQL]: https://www.postgresql.org
  47. So too are the attempts to re-brand "open source" in a manner which is more
  48. commercially exploitable for an individual person or organization equally
  49. dishonest. The industry has an orthodox understanding of the meaning of "open
  50. source", i.e. that defined by the Open Source Initiative, which is generally
  51. well-understood through the proliferation of software licenses which are
  52. compatible with the OSD. When a project describes itself as "open source",
  53. this is a useful short-hand for understanding that the project adheres to a
  54. specific set of values and offers a specific set of rights to its users and
  55. contributors. When those rights are denied or limited, the OSD no longer applies
  56. and thus neither does the term "open source". To disregard this in the interests
  57. of a financial incentive is dishonest, much like I would be dishonest for
  58. selling "cakes" and fulfilling orders with used car tires with "cake" written on
  59. them instead.
  60. Critics of the OSD frequently point out that the OSI failed to register a
  61. trademark on the term "open source", but a trademark is not necessary for this
  62. argument to hold. Language is defined by its usage, and the OSD is the popular
  63. usage of the term "open source", without relying on the trademark system. The
  64. existence of a trademark on a specific term is not required for language which
  65. misuses that term to be dishonest.
  66. As language is defined by its usage, some may argue that they are as entitled as
  67. anyone else to put forward an alternative usage. This is how language evolves.
  68. They are not wrong, though I might suggest that their alternative usage of "open
  69. source" requires a substantial leap in understanding which might not be as
  70. agreeable to those who don't stand to benefit financially from that leap. Even
  71. so, I argue that the mainstream definition of open source, that forwarded by the
  72. OSI, is a *useful* term that is worth preserving in its current form. It is
  73. useful to quickly understand the essential values and rights associated with a
  74. piece of software as easily as stating that it is "open source". I am not
  75. prepared to accept a new definition which removes or reduces important rights in
  76. service of your private financial interests.
  77. The mainstream usage of "open source" under the OSD is also, in my opinion,
  78. morally just. You may feel a special relationship with the projects you start
  79. and invest into, and a sense of ownership with them, but they are not rightfully
  80. yours once you receive outside contributions. The benefit of open source is in
  81. the ability for the community to contribute directly to its improvements —
  82. and once they do, the project is the sum of your efforts *and* the efforts of
  83. the community. Thus, is it not right that the right to commercial exploitation
  84. of the software is shared with that community? In the absence of a CLA,[^cla]
  85. contributors retain their copyright as well, and the software is legally jointly
  86. owned by the sum of its contributors. And beyond copyright, the success of the
  87. software is the sum of its code along with the community who learns about and
  88. deploys it, offers each other support, writes blog posts and books about it,
  89. sells consulting services for it, and together helps to popularize it. If you
  90. wish to access all of these benefits of the open source model, you must play by
  91. the open source rules.
  92. [^cla]: Such CLAs are also unjust in my view. Tools like the [Developer
  93. Certificate of Origin] are better for meeting the need to establish the
  94. legitimate copyright of open source software without denying rights to its
  95. community.
  96. [Developer Certificate of Origin]: https://developercertificate.org
  97. It's not surprising that this would become a matter of contention among certain
  98. groups within the industry. Open source is not just eating the world, but *has
  99. eaten* the world. Almost all software developed today includes substantial open
  100. source components. The open source brand is very strong, and there are many
  101. interests who would like to leverage that brand without meeting its obligations.
  102. But the constraints of the open source definition are *important*, played a
  103. critical role in the ascension of open source in the software market, and worth
  104. preserving into the future.
  105. That's not to say that there isn't room for competing ideologies. If you feel
  106. that the open source model does not work for you, then that's a valid opinion to
  107. hold. I only ask that you market your alternative model honestly by using a
  108. different name for it. Software for which the source code is available, but
  109. which does not meet the requirements of the open source definition, is
  110. rightfully called "source available". If you want a sexier brand for it, make
  111. one! "Open core" is also popular, though not exactly the same. Your movement has
  112. as much right to success as the open source movement, but you need to earn that
  113. success independently of the open source movement. Perhaps someday your
  114. alternative model will supplant open source! I wish you the best of luck in this
  115. endeavour.
  116. *A previous version of this blog post announced that I had submitted my
  117. candidacy for the OSI board. Due to unforseen circumstances, I will be
  118. postponing my candidacy until the next election. I apologise for the confusion.*