logo

drewdevault.com

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

2023-04-11-The-FSF-is-dying.md (6676B)


  1. ---
  2. title: The Free Software Foundation is dying
  3. date: 2023-04-11
  4. ---
  5. The Free Software Foundation is one of the longest-running missions in the
  6. free software movement, effectively defining it. It provides a legal foundation
  7. for the movement and organizes activism around software freedom. The GNU
  8. project, closely related, has its own long story in our movement as the coding
  9. arm of the Free Software Foundation, taking these principles and philosophy into
  10. practice by developing free software; notably the GNU operating system that
  11. famously rests atop GNU/Linux.
  12. Today, almost 40 years on, the FSF is dying.
  13. Their achievements are unmistakable: we must offer them our gratitude and
  14. admiration for decades of accomplishments in establishing and advancing our
  15. cause. The principles of software freedom are more important than ever, and the
  16. products of these institutions remain necessary and useful -- the GPL license
  17. family, GCC, GNU coreutils, and so on. Nevertheless, the organizations behind
  18. this work are floundering.
  19. The Free Software Foundation must concern itself with the following ahead of all
  20. else:
  21. 1. Disseminating free software philosophy
  22. 2. Developing, publishing, and promoting copyleft licenses
  23. 3. Overseeing the health of the free software movement
  24. It is failing in each of these regards, and as its core mission fails, the
  25. foundation is investing its resources into distractions.
  26. In its role as the thought-leaders of free software philosophy, the message of
  27. the FSF has a narrow reach. The organization's messaging is tone-deaf,
  28. ineffective, and myopic. Hammering on about "GNU/Linux" nomenclature, antagonism
  29. towards our allies in the open source movement, maligning the audience as
  30. "useds" rather than "users"; none of this aids the cause. The pages and pages of
  31. dense philosophical essays and poorly organized FAQs do not provide a useful
  32. entry point or reference for the community. The message cannot spread like this.
  33. As for copyleft, well, it's no coincidence that many people struggle with the
  34. FSF's approach. Do you, dear reader, know the difference between free software
  35. and copyleft? Many people assume that the MIT license is not free software
  36. because it's not viral. The GPL family of licenses are essential for our
  37. movement, but few people understand its dense and esoteric language, despite the
  38. 16,000-word FAQ which supplements it. And hip new software isn't using copyleft:
  39. over 1 million npm packages use a permissive license while fewer than 20,000 use
  40. the GPL; cargo sports a half-million permissive packages and another 20,000 or
  41. so GPL'd.
  42. And is the free software movement healthy? This one gets an emphatic "yes!" --
  43. thanks to the open source movement and the near-equivalence between free
  44. software and open source software. There's more free software than ever and
  45. virtually all new software contains free software components, and most people
  46. call it open source.
  47. The FOSS community is now dominated by people who are beyond the reach of the
  48. FSF's message. The broader community is enjoying a growth in the diversity of
  49. backgrounds and values represented, and the message does not reach these people.
  50. The FSF fails to understand its place in the world as a whole, or its
  51. relationship to the progressive movements taking place in the ecosystem and
  52. beyond. The foundation does not reach out to new leaders in the community,
  53. leaving them to form insular, weak institutions among themselves with no central
  54. leadership, and leaving us vulnerable to exploitation from growing movements
  55. like open core and commercial attacks on the free and open source software
  56. brand.
  57. Reforms are sorely needed for the FSF to fulfill it basic mission. In
  58. particular, I call for the following changes:
  59. 1. **Reform the leadership**. It's time for Richard Stallman to go. His polemeic
  60. rhetoric rivals even my own, and the demographics he represents -- to the
  61. exclusion of all others -- is becoming a minority within the free software
  62. movement. We need more leaders of color, women, LGBTQ representation, and
  63. others besides. The present leadership, particularly from RMS, creates an
  64. exclusionary environment in a place where inclusion and representation are
  65. important for the success of the movement.
  66. 1. **Reform the institution**. The FSF needs to correct its myopic view of the
  67. ecosystem, reach out to emerging leaders throughout the FOSS world, and ask
  68. them to take charge of the FSF's mission. It's these leaders who hold the
  69. reins of the free software movement today -- not the FSF. If the FSF still
  70. wants to be involved in the movement, they need to recognize and empower the
  71. leaders who are pushing the cause forward.
  72. 1. **Reform the message**. People depend on the FSF to establish a strong
  73. background in free software philosophy and practices within the community,
  74. and the FSF is not providing this. The message needs to be made much more
  75. accessible and level in tone, and the relationship between free software and
  76. open source needs to be reformed so that the FSF and OSI stand together as
  77. the pillars at the foundations of our ecosystem.
  78. 1. **Decouple the FSF from the GNU project**. FSF and GNU have worked
  79. hand-in-hand over decades to build the movement from scratch, but their
  80. privileged relationship has become obsolete. The GNU project represents a
  81. minute fraction of the free software ecosystem today, and it's necessary for
  82. the Free Software Foundation to stand independently of any particular project
  83. and focus on the health of the ecosystem as a whole.
  84. 1. **Develop new copyleft licenses**. The GPL family of licenses has served us
  85. well, but we need to do better. The best copyleft license today is the
  86. [MPL][1], whose terse form and accessible language outperforms the GPL in
  87. many respects. However, it does not provide a comprehensive answer to the
  88. needs of copyleft, and new licenses are required to fill other niches in the
  89. market -- the FSF should write these licenses. Furthermore, the FSF should
  90. present the community with a free software perspective on licenses as a
  91. resource that project leaders can depend on to understand the importance of
  92. their licensing choice such that they understand the appeal of copyleft
  93. licenses without feeling pushed away from permissive approaches.
  94. [1]: https://www.mozilla.org/en-US/MPL/
  95. The free software movement needs a strong force uniting it: we face challenges
  96. from many sides, and today's Free Software Foundation is not equal to the task.
  97. The FOSS ecosystem is flourishing, and it's time for the FSF to step up to the
  98. wheel and direct its coming successes in the name of software freedom.