Open JYamihud opened 3 years ago
For now I gonna treat this software as proprietary.
I agree, that treating the software for which the license is unknown as proprietary/non-free is the most reasonable and safe approach.
However, one may find the license preambles in the source files to which they apply one by one:
It may be tempting to just add a license file to the main directory, licensing the entire project is not as simple. Whereas I may alter in any way I see fit my contributions to the codebase and their respective license conditions, I cannot do the same for code that was added by other contributors. If the changes were made to previously non-explicitly-licensed files, I may need their explicit permission to relicense their contributions from previously non-free/proprietary license to the license of my choosing. Tracking all contributors for a project that is 10 years old is tricky.
@syohex @tkf i'll defer to your judgement here, as you have been around for much longer than me.
I cannot do the same for code that was added by other contributors
GPL is good since if somebody contributes. Now the software is secured from YOU, the main developer, turning it into proprietary. Anyway, good to know that the file you showed is under GPL.
Well the very text you quoted says
You should have received a copy of the GNU General Public License along with Jedi EPC server.
meaning the GPLv3 license should be actually included in the distribution (i.e., as a LICENSE
or COPYING
file in the repo).
Also, I seriously doubt any contributor ever expected their contributions to be anything other than GPLv3.
What is the license? I can't find a single mention of a license. Please add a license file in the main directory. For now I gonna treat this software as proprietary. Until you add a license.