Topic summary

High Priority Free Software Projects

High Priority Free Software Projects

Extracted from the Wikipedia article Free Software Foundation.

References

  1. ^ 2026.
  2. ^ 2024.
  3. ^ 2025.
  4. ^ 2022.
  5. ^ 2022.
  6. ^ 2022.
  7. ^ . Technical Services Quarterly. 35 (3): 269–279. doi:10.1080/07317131.2018.1456849. ISSN 0731-7131. S2CID 196159979. Archived from the original on July 10, 2023 2022.
  8. ^
  9. ^ 2012.
  10. ^ 2012.
  11. ^ 2020.
  12. ^
  13. ^ 2024.
  14. ^ 2006.
  15. ^
  16. ^ 2012.
  17. ^ 2012.
  18. ^
  19. ^
  20. ^
  21. ^ 2007. Hosted on the Wayback Machine.
  22. ^ 2007.
  23. ^ 2007.
  24. ^
  25. ^
  26. ^ 2007.
  27. ^ . Free Software Foundation. Archived(PDF) from the original on September 25, 2007 2007.
  28. ^ 2007.
  29. ^ 2011.
  30. ^ 2008.
  31. ^ 2008. On Friday 8 August 2003, we will hold a seminar on the GNU GPL. The seminar, titled "Free Software Licensing and the GNU GPL", will be co-led by Daniel Ravicher, Outside Counsel to FSF from Patterson Belknap Webb & Tyler, and Bradley M. Kuhn, Executive Director of FSF.
  32. ^ 2008.
  33. ^ 2012.
  34. ^ 2012.
  35. ^ 2008.
  36. ^ 2009.
  37. ^ 2020.
  38. ^ 2021.
  39. ^ 2021. I continue to be the Chief GNUisance of the GNU Project. I do not intend to stop any time soon.
  40. ^ 2021.
  41. ^ 2021.
  42. ^
  43. ^
  44. ^ 2019.
  45. ^ 2019.
  46. ^ 2019.
  47. ^ 2014.
  48. ^ 2007.
  49. ^ 2023.
  50. ^ 2017.
  51. ^ 2017.
  52. ^ 2014. Long story short, being on the Free Software Foundation's high priority list really doesn't mean much with some of these "important" projects not even being actively developed or even discussed.
  53. ^ 2014. Most of the projects are basically not going anywhere. Many of them at the time were not really advancing in their goals, haven't had releases in a while, or coding hasn't even started. It's been more than a half-year and still there's no significant work towards clearing many of projects from the FSF list.
  54. ^ 2021.
  55. ^ ". PCWorld. Archived from the original on June 6, 2023 2023.
  56. ^ 2014.
  57. ^ 2024.
  58. ^ 2019.
  59. ^ 2007.), indicates this list of people as round[ing] out FSF's board of directors.
  60. ^ . The Commonwealth of Massachusetts. December 17, 2002. Archived(PDF) from the original on September 25, 2007 2007.) show that De Icaza has left the board. Changes to board composition are usually made at the annual meeting; which occurred on February 25, 2002.
  61. ^ 2025.
  62. ^ 2015.
  63. ^ 2010.
  64. ^ 2019.
  65. ^ 2007.). The resignation likely occurred at the 2007 annual meeting of the directors; the exact date of that meeting is unknown.
  66. ^ 2015.
  67. ^ 2022.
  68. ^ 2020.
  69. ^ 2020.
  70. ^ 2024.
  71. ^

  • ^

  • ^ 2023.
  • ^ 2015.
  • ^
  • ^ . The Commonwealth of Massachusetts. May 26, 2005. Archived(PDF) from the original on August 26, 2008 2008.
  • ^
  • ^ 2008.
  • ^ 2017.
  • ^ 2014.
  • ^ 2022.
  • ^ 2024.
  • ^ 2024.
  • ^ 2024.
  • ^ 2024.
  • ^ 2024.
  • ^ 2019.
  • ^ 2010.
  • ^ 2019.
  • ^ 2013. Both LibreCAD and FreeCAD both want to use LibreDWG and have patches available for supporting the DWG file format library, but can't integrate them. The programs have dependencies on the popular GPLv2 license while the Free Software Foundation will only let LibreDWG be licensed for GPLv3 use, not GPLv2.
  • ^ 2025. [Assimp's Alexander Gessler:] "Personally, I'm extremely unhappy with their [LibreDWG's — LGW] GPL licensing. It prohibits its use in Assimp and for many other applications as well. I don't like dogmatic ideologies, and freeing software by force (as GPL/GNU does) is something I dislike in particular. It's fine for applications, because it doesn't hurt at this point, but, in my opinion, not for libraries that are designed to be used as freely as possible." [Blender's Toni Roosendaal:] "Blender is also still "GPLv2 or later". For the time being we stick to that, moving to GPL 3 has no evident benefits I know of. My advice for LibreDWG: if you make a library, choosing a widely compatible license (MIT, BSD, or LGPL) is a very positive choice."
  • ^ 2025. [...]the unfortunate situation with support for DWG files in free CAD software via LibreDWG. We feel, by now it ought to be closed. We have the final answer from FSF. [...] "We are not going to change the license."
  • ^ 2025. GPLv3 license. It doesn't work for end-user software, because they tend to use 3rd party components under different licenses that impose restrictions. FSF who are sole copyright holders of LibreDWG objected to relicensing. With regards to FreeCAD project and Yorik van Havre, its contributor, Richard Stallman stated:" You should not change the license of your library. Rather, it is best to make it clear to him what the conditions are." [...] Personally, I'm extremely unhappy with their [LibreDWG's — LGW] GPL licensing. It prohibits its use in Assimp and for many other applications as well. I don't like dogmatic ideologies, and freeing software by force (as GPL/GNU does) is something I dislike in particular. It's fine for applications, because it doesn't hurt at this point, but, in my opinion, not for libraries that are designed to be used as freely as possible.
  • ^ 2021.
  • ^ 2021.
  • ^ 2021.
  • ^ 2021.
  • ^ 2007.
  • ^ 2006.
  • Wikipedia source