Not to drag this on, but I wanted to say that agree with your sentiment;
that's why I stick with MIT:
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following conditions
MIT gets rid of the ambiguity that *not* having a license causes,
while providing that anyone can use the software with no restrictions.
You're correct that CC0 is more for arts; it kind of works, but MIT
provides restriction-free usage while being written towards technical
implementation. Hopefully that information helps your decision, regardless
of what you choose!
On Tue, Nov 27, 2012 at 11:12 AM, Moritz Wilhelmy <mor...@wzff.de> wrote:
> Hi,
>
> On Tue, Nov 27, 2012 at 19:30:19 +0100, Thijs Schreijer wrote:
> > 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, I know. I am looking for a solution or rather a compromise for
> this problem, because the notion of withdrawing the copyright to the
> files I myself orignially created is legally impossible in many parts of
> the world. (Essentially, at least in my understanding, this makes
> "copyright" a duty, not a right, because I'm not left the choice to
> opt-out of it, except by not creating. As silly as it sounds, I feel
> repressed by the idea of not being capable of granting my code as a gift
> to the public, no matter how questionable it's usefulness ;)
>
> On the other hand, I don't want the copyright. The plain idea that
> someone can have the copyright for some piece of data is - in my view
> - so fundamentally flawed that I would prefer not to use it.
>
> Personally, I abhor licenses (and much more, debates about them, because
> this email is already almost as long as the entire content of the
> distribution archive for lua-bencode). They are boilerplate that is
> copied around but rarely read or understood, and they get on my nerves
> by being mutually incompatible with every other version of every other
> license (GPL, I'm looking at you) which is a harmful thing for the
> advancement of the open source movement. (Note, I don't have anything
> against any particular license, neither GPLvX nor MIT, I hate them all
> equally :)
>
> Sorry about taking this too much into offtopic. Perhaps CC0 is a real
> alternative to the public domain, even though CC is mostly associated
> with arts rather than source code (although CC0 in particular is
> classified as suitable for source code).
>
> Unfortunately, I am not a lawyer, and I have no means to consult one.
> I'll see what license emerges in the future, but I'm certain it will not
> be more restrictive than 2-clause BSD.
>
> I hope you are not offended by this mail (don't take it (or me)
> seriously), I hear some people are very attached to licenses, and I
> welcome your input, although I'd be happier to see technical gripes
> instead, because those tend to be easier to fix, and I'm sure there are
> enough real issues to worry about, like the n+1 bugs I introduced while
> creating the distribution tarball ;)
>
> Hisham: Thanks for adding it to the repository!
>
>
> Best regards,
>
> Moritz
>
>
> ------------------------------------------------------------------------------
> 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
>
------------------------------------------------------------------------------
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
