Give open-source developers a free license for my commercial software?
I am creating a software package that will be useful to programmers, engineers and scientists. List price will be in the region of $1,000 — way beyond the budget of most open-source developers, hobbyists and enthusiasts. So I am considering two things, the first generous, the second maybe a little greedy:
Is Java free/open source or not?
On November 13, 2006, Sun released much of Java as free and open source software, (FOSS), under the terms of the GNU General Public License (GPL). On May 8, 2007, Sun finished the process, making all of Java’s core code available under free software/open-source distribution terms, aside from a small portion of code to which Sun did not hold the copyright.
Anonymous software license
I am aware of some of the problems of the concept of “releasing a work to the public domain” (as mentioned here and here; I haven’t listened to this specific discussion yet). IANAL, but the main problems seem to be as follows:
How to license my closed source & freeware (donation ware) – using creative commons?
After doing a bit of research about licensing my free software, I reached this:
Sourcecode license: free for personal use and modification but no public distibution
For one of my apps, I want to make the source code “open source” so that others might adapt the code to their personal needs or even contribute improvements, but I don’t want anybody else to publish “my app”. Furthermore, I still want to be able to sell the app at some time in the future.
Isn’t GPL enough to make a software free as in free speech?
Doesn’t GPL explicitly mean you are free to re-distribute ?
License: free to use but not free to modify or redistribute
I am releasing an application at no cost, but I am not granting users the right to modify or redistribute the code. How should I call this?
License that grants the initial author all rights of derived/modified work?
Please note that I do not want to argue about the moral aspect of this question. I know that there are probably many different concerns.
If I try to monetize free software, what could possibly prevent someone from forking that software and creating a proprietary version? [duplicate]
This question already has answers here: What are the common revenue models for free-software companies? (6 answers) Closed 10 years ago. I’ve only recently begun to learn about the tensions between free and proprietary software, and I’ve been very confused by the way that free software can make money. I understand that free software is […]
Deferred Open Source licensing
Are there established models for releasing an initially proprietary piece of software under FLOSS conditions after a defined period or a certain point of time? The main problem here is that all parties involved must be able to trust that the Open Source licensing will actually take place at the defined time and no party can further defer or cancel this process.