<story><title>Open Source Bait and Switch</title><url>https://debugagent.com/open-source-bait-and-switch</url></story><parent_chain><item><author>sneak</author><text>Many people find the AGPL to be a nonfree license, myself included.</text></item><item><author>Y_Y</author><text>This is a good point and I&amp;#x27;d like to suggest (without being certain) that the AGPL is a good solution.&lt;p&gt;&amp;gt; The GNU Affero General Public License is designed specifically to ensure that ... the modified source code becomes available to the community. It requires the operator of a network server to provide the source code of the modified version running there to the users of that server. Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version.</text></item><item><author>bawolff</author><text>GPL is still a questionable choice for anything that can be turned into a SAAS app. Remember if you dont distribute the binary, you dont have to distribute sources.</text></item><item><author>systems_glitch</author><text>Been saying this privately for a long time. Agree on &amp;quot;GPL is the best choice,&amp;quot; as well. My personal experience with devs who don&amp;#x27;t want to GPL their code or contribute to GPL projects is that they&amp;#x27;re under the impression that having a permissive license on their own project will get $corp to use it and, somehow, they&amp;#x27;ll profit from $corp using it. Haven&amp;#x27;t personally seen it yet, but I &lt;i&gt;have&lt;/i&gt; seen a bunch of permissive licensed stuff get pulled into bigger projects and changes never contributed back.</text></item></parent_chain><comment><author>enriquto</author><text>&amp;gt; Many people find the AGPL to be a nonfree license, myself included.&lt;p&gt;I don&amp;#x27;t understand this stance.&lt;p&gt;From the point of view of the user, the AGPL offers the same freedoms as the regular GPL.  If you &lt;i&gt;use&lt;/i&gt; the program, you have the right to see and edit its source code, regardless if the program runs on your own computer or on another computer.&lt;p&gt;How can anybody call this feature &amp;quot;nonfree&amp;quot; is beyond me.</text></comment>
<story><title>Open Source Bait and Switch</title><url>https://debugagent.com/open-source-bait-and-switch</url></story><parent_chain><item><author>sneak</author><text>Many people find the AGPL to be a nonfree license, myself included.</text></item><item><author>Y_Y</author><text>This is a good point and I&amp;#x27;d like to suggest (without being certain) that the AGPL is a good solution.&lt;p&gt;&amp;gt; The GNU Affero General Public License is designed specifically to ensure that ... the modified source code becomes available to the community. It requires the operator of a network server to provide the source code of the modified version running there to the users of that server. Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version.</text></item><item><author>bawolff</author><text>GPL is still a questionable choice for anything that can be turned into a SAAS app. Remember if you dont distribute the binary, you dont have to distribute sources.</text></item><item><author>systems_glitch</author><text>Been saying this privately for a long time. Agree on &amp;quot;GPL is the best choice,&amp;quot; as well. My personal experience with devs who don&amp;#x27;t want to GPL their code or contribute to GPL projects is that they&amp;#x27;re under the impression that having a permissive license on their own project will get $corp to use it and, somehow, they&amp;#x27;ll profit from $corp using it. Haven&amp;#x27;t personally seen it yet, but I &lt;i&gt;have&lt;/i&gt; seen a bunch of permissive licensed stuff get pulled into bigger projects and changes never contributed back.</text></item></parent_chain><comment><author>ebiester</author><text>What isn&amp;#x27;t free about it?&lt;p&gt;As a corporation, I might not want to use it in conjunction with my code, but that&amp;#x27;s the point. You are free to do what you want, but you in turn must share your code.&lt;p&gt;Or you engage with the owner to make a financial arrangement for a separate license.</text></comment>