a good "license your software" how-to for upstream developers ?
On Wed, Mar 21, 2012 at 11:39:26PM +0100, Jérémy Lal wrote:
> i find it difficult and time-consuming to explain, with limited vocabulary
> (english is not my mother tongue), to an upstream developer that his tarball
> is not properly licensed.
> For example i've seen software that was intended to be free, released without
> any license, or with missing license on some files, bundled dependencies, or
> pictures, or even worse with a modified adhoc license.
> I find it very very hard to find the right words to explain whatever is wrong
> with those, and so, i wonder if there is some clear and concise documentation
> about how to properly license a free software, targeted at upstream developers.
Maybe http://wiki.debian.org/UpstreamGuide#Licenses ?
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com