> -----Original Message----- > From: Hisham [mailto:h...@hisham.hm] > Sent: dinsdag 27 november 2012 19:55 > To: luarocks-developers@lists.sourceforge.net > Subject: Re: [Luarocks-developers] [ANN] bencode-2.0 > > On Tue, Nov 27, 2012 at 4:30 PM, Thijs Schreijer <th...@thijsschreijer.nl> > wrote: > >> > >> Project homepage: http://bitbucket.org/wilhelmy/lua-bencode/ > >> > > > > Minor remark; you mention "While not a license, all files in this > > repository have been placed in the public domain because the authors > > do not believe in intellectual property.", and while that may be a > > true statement, in practice it creates more problems than necessary. > > Just stamping it with MIT or similar provides the least legal hassle > > for anyone who wants to use your code. > > Well, as far as I know the only kinds of hassles that public domain causes are > for those who want explicit legal clearance to use them in proprietary > products. Given that their motivation for use of public domain is a statement > against intelectual property laws and not mere desire of universal availability, > I'd think that public domain is actually closer to their goal than the MIT > license. (Speaking as someone who has both GPL and MIT code out there, > and who has nothing against those licenses -- much to the contrary.) > > Of course, it's always good to play nice with the usual customs of the > community (I think it's the main reason why most Lua modules are licensed > with the same license as Lua, Perl modules with the same license as Perl, > etc.) but at the same time there's absolutely no problem in submitting > rockspecs to the main repo with other (freely > redistributable) licenses, or public domain (Lua team's own lhf tends to use > public domain a lot). > > -- Hisham > http://hisham.hm/ >
They are both "you can do whatever you want and get away with it licenses", but MIT is a clear legal statement, "public domain" is not. I think clear is better. If you don't want to provide "explicit legal clearance" so it can't be used in proprietary products, use GPL, same effect, but clear. I don't favor one license over the other, they all serve their purpose. But I do prefer clarity. Thijs PS. and I hate flame wars so let's stop here before we start one. ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: DESIGN Expert tips on starting your parallel project right. http://goparallel.sourceforge.net _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
