Driven by the success of the GNU/Linux operating system, the GNU General Public License (GPL) has become popular to the point of becoming the default license for alternative software development. Actually, the question as to why this project does not release its code under the terms of the GPL is probably the most frequently asked question of all.
This is our answer.
One word up front: As an evangelist of the GPL, you have probably heard the term "freedom as in free speech". Please accept that we do excercise this right as well, speaking our minds about the GPL. Freedom of opinion always includes the opinion you do not share or like.
The agenda of the GPL
For the Open Source movement, the issue of whether software should be open source is a practical question, not an ethical one. As one person put it, "Open source is a development methodology; free software is a social movement." For the Open Source movement, non-free software is a suboptimal solution. For the Free Software movement, non-free software is a social problem and free software is the solution.
--http://www.gnu.org/philosophy/free-software-for-freedom.html
To put it blunt: Pro-POS is about technology, not about "social problems", whether real or perceived. Computers are used by people to achieve a means that ultimately has nothing to do with computers themselves. Computers are not important, and the software they run is not important either. What is important is the task at hand, for which you happen to need a computer as a tool.
The only "social problem" today is that the available tools - whether proprietary or "free" - do get in the way instead of enabling Joe Average to do his job.
Four Kinds Of Freedom
Free software is a matter of the users' freedom to run, copy, distribute, study, change and improve the software. More precisely, it refers to four kinds of freedom, for the users of the software...
--
In this chapter, we will have a look at those four freedoms, and voice our opinion on them.
- The freedom to run the program, for any purpose (freedom 0).
Little to argue here. The other three are what makes the FSF's definition tricky.
- "The freedom to study how the program works, and adapt it to your needs (freedom 1)."
Let's call this "the freedom of GPL lock-in".
It is not unheard-of that hardcore GPL evangelists would claim your work to be "a derivative work based on the product" if you looked at the inner workings of a similar such (GPL'ed) product before. You're wellcome to educate yourself, if you release the work based on that self-education under the GPL.
We consider "freedom of choice" to include choice of license. Tutorials and Basics belong into the Public Domain, period, and that's what we're doing with the PDCLib and FirstStep.
- "The freedom to redistribute copies so you can help your neighbor (freedom 2)."
Let's call this "the freedom of a project not paying for itself".
Our long-term aim for "Perfection" is to release a shrink-wrapped box including printed manual for Joe Average, providing a server offering up-to-date security advisories and online update functionality for Toni Administrati, and an all-inclusive web community including free up-/download of tools, demos, tutorials and what-not for our user base. Advertising certainly wouldn't hurt, and sending out evaluation versions to software companies to get them interested.
This will cost money.
Yes, the FSF goes on at length about how you could make money with GPL'ed software - or rather, how to make money despite releasing software under GPL. Selling services ranks highly on that list.
Everyone from the CoreTeam either has a full-time job, or studies to attend. We're not looking for an opportunity to make a full-time job out of this project - and if we would, we'd rather spend the time removing obstacles, instead of showing customers how to avoid them.
We could ask for donations. But with children dying of starvation, still no cure for cancer and AIDS, and global warming endangering our species, that just feels wrong. Donate those requiring charity; we would rather sell our handiwork like crafters have done since ancient times.
Of course pre-release versions of our product are hardly worth your money, so we won't charge for any version 0.x of anything. And those who contribute, in words or code, are considered having payed their share already. The LicenseAgreement will reflect this.
All this being said, we believe your neighbour is best served if the tool you provide him with will be maintained and supported for days to come.
- The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3).
...to be continued.
ThreeKindsOfSoftware
Basics
The implementation of standards, tutorials and example code could be considered a "basic": A C Standard Library, or a SSL library are good examples. Everybody needs these basics, and there is very little "competitive advantage" to be had. Open up this stuff to everyone, so everyone may benefit - be it by free software, or a cheaper commercial product!
Tools
A tool is an executable or a library with a limited feature set.
...to be continued.
Products
...to be continued.