New answers tagged open-source
With internal libraries, you don't need to distribute them at all. The end user will have their own copy in their JRE. You only distribute code you own so you doesn't have any constraints. If you distribute code using GPL libraries, your code would need to be compatible with the GPL license which includes making all the code of the combined work available. ...
You should have continuous deployment procedure to some sort of library repository which has unit tests integration tests maybe a review for the release
You should keep a "software migration document" describing the new design and teaching how to migrate existing software. It should answer these questions: what changed? how do I update my code? why did this change happen? [optional] where can I learn more? Possibly it should be short, friendly, informative (with references to further documentation). ...
It is a bit more nuanced than a straight up yes or no. In general, it is correct that you must be able (and legally allowed) to distribute the source code of all libraries that are used in a program that contains GPL licensed code. The nuance comes when dealing with GPL licensed code and libraries that are part of the core infrastructure of a computer (OS ...
It's part of your private environment. Most people want; some random tool like guard is not something I know or care about, nor want to use if for some reason it managed to be installed. I build projects by typing make, not automatically in the background. However, I disagree that privately useful files should never be part of the repo. Many projects ship a ...
GPLv1 §7 states: …Each version is given a distinguishing version number. If the Program specifies a version number of the license which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not ...
If no version is mentioned, you can use it under any version of the GPL, including version 1. It is for this reason that "any version" is not recommended, because the GPLv1 is much weaker than GPLv2 or GPLv3.
The first couple projects that I did that were open source never got off the ground. The mistake I made is that I kept my coworkers, as well as friends and family, completely separate from the work I was doing, and I only talked about these projects on my rarely-visited blog. I did the opposite of what I should have done. Now, I have a few projects I've ...
Following the links on this page i found nothing up-to-date and available, neither the mentioned modified GPL nor the PeaceOSL. But you can read the latter here. And I wouldn't be sure how well defined the term any harm, which is their criteria, is in legal systems. Maybe you want to contact the authors.
Top 50 recent answers are included