4 ms·
most developers won’t release the source anyway while they develop for many possible reasons: It’s not working yet, they are not proud of their code yet, they d
by rmc 14y ago
most developers won’t release the source anyway while they develop for many possible reasons: It’s not working yet, they are not proud of their code yet, they don’t know what to do with it yet, etc.
Well under the AGPL they are required to release the code… Sorry, but that's copyright law and that's the copyleft licence.
- hbbio 14y agoWhat I meant is: while they develop. The AGPL does not require you to publish your code before you either distribute it or run it online.
- mikeash 14y agoNo, they are only required to release the code when the distribute the result. The license does not compel a developer to release the code before they've started distributing it.
- emillon 14y agoIn the context of the AGPL, serving an application is like distributing a binary, so they should distribute its sources too.
- mikeash 14y agoWhich probably doesn't apply while the stuff is still in development.
- rmc 14y agoThe license does not compel a developer to release the code before they've started distributing it. No that's the GPL you're thinking of. AGPL requires the source code be shared out to everyone once (roughly) people access it.
- jmillikin 14y agoThe AGPL is still a copyright license, and therefore still only matters if the work is being distributed in some way. If the work isn't being distributed, then copyright permission is not required, and the license is irrelevant.
- rmc 14y agoNot true. Copyright includes the right to control how a work may be performed publicly. I presume this allows the AGPL to enter a "You may only make this work available publically if you do X, Y and Z." Software that is no actually distributed externally, but is interacted by the public is the express target of the AGPL licence. They would have thought of how to cover the "non-distribution" case.
- jmillikin 14y ago> Not true. Copyright includes the right to control how a work > may be performed publicly. I presume this allows the AGPL to > enter a "You may only make this work available publically if > you do X, Y and Z." The thing is that if the work isn't being made available, then copyright just doesn't apply. Public performance applies to things like art and music, for which the work must be duplicated to be performed. But software does not have to be duplicated (excepting from disk->ram, etc, which is considered fair use). For example, if there was an AGPL'd binary which would render a PDF to a PNG, I could host it on my server and let people interact with it but not release the source. The reason I do not have to release the source is that I am not distributing the binary. The AGPL is designed for cases where interaction requires that part of the work itself be sent to the user -- examples are web pages, Java applets, and so on.
- rmc 14y agoif there was an AGPL'd binary which would render a PDF to a PNG, I could host it on my server and let people interact with it but not release the source. The reason I do not have to release the source is that I am not distributing the binary. These seems exactly like the use case of the AGPL, which I why I think they would have covered that. (Web Pages (of a web application) are the rendered output of programmes on the server side, so would be the same as "a binary that made a PDF into a PNG")