Defining "Philosophically Open-Source"?
This essay is unfinished, and I have no plans to finish it.
This essay was written by me, emsenn, and is released for the benefit of the public under the terms included in the "License" supplement. It was made possible with financial contributions from humans like you. Please direct comments to my public inbox or, if necessary, my personal email.
This essay was written when the events it discusses were contemporary. Information in it may now be incorrect, and opinions presented may be out of date.
Defining "Philosophically Open-Source"
Whenever I go to tell someone about one of the many projects I'm working on at any given time, I almost certainly will toss out the phrase "philosophically open-source".
Defining what exactly that means is a bit trickier than just saying it. Let's look at what makes a project open-source, and see how that contrasts with one that is philosophically open-source.
The Open Source Initiative has a pretty good definition of open-source, which I'll excerpt from below:
1. Free Redistribution - The license shall not restrict any party from selling or giving away the software
So, the thing has to be free like "free drink with purchase".
…The program must… allow distribution in source code as well as compiled form…
The code behind the thing has to be available.
… The license must allow modifications and derived works…
Other folk are permitted to make a new thing out of your thing.
There's some more specifics in the actual definition, and some new additions about how you must not discriminate, either against individuals or certain fields. But what I want to highlight is the recurring little phrase "must allow".
To be open-source, a product must allow for free distribution & modification.
To be philosophically open-source, a product must encourage free distribution & modification.
It isn't just enough to allow someone to improve the source code - you should encourage it, by providing systems & channels to assist them. Which means that as a developer, releasing a philosophically open-source product means not just agreeing to release the source code, but agreeing to serve as the product's manager.
As with almost anything where the word "philosophy" is brought in, defining the difference between "allow" and "encourage" can be a bit tricky.
But there are a few things that I think can be stated pretty concretely, giving us a good working definition of philosophically open source:
"Philosophically Open-Source" Definition
- Encourage Free Distribution
- The license should be the most freeing available (currently the Unlicense), and the software should be packaged for distribution through common package repositories. https://unlicense.org/
- Encourage Collaboration
- The software must include guidelines for contributing bug reports & patches, and have provisions that work against discrimination.
- Encourage Derived Works
- The software must include instructions for creating a fork of itself.
- Open-Source Stack
- All dependencies of the software must be open-source as defined by the Open-Source Initiative. https://opensource.org/osd
This essay was made possible with contributions from humans like you. Thank you! I currently accept contributions through the following platforms:
If there is another service through which you'd like to contribute, please send an email. Please note that in accordance with my personal directives #003 and #018, I release all useful information I create for free, so financial contributions do not entitle you to access to any "exclusive content."
Copyright 2019 emsenn
Permission is hereby granted, free of charge, to any person obtaining a copy of this document and associated media files (the "Document"), to deal in the Doftware without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Doftware, and to permit persons to whom the Doftware is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
The Document is provided "as is," without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, or noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort, or otherwise, arising from, out of or in connection with the Document or the use or other dealings in the Document.