On Thu, Jan 12, 2012 at 3:22 PM, Radomir Dopieralski <[email protected]>wrote:
> On Thu, Jan 12, 2012 at 11:22, anatoly techtonik <[email protected]> > wrote: > > >> > I'd unlicense all the content. If you need to share a licensed > material > >> > - > >> > place it on your site and provide a link from the wiki. > >> > >> Why would you want to remove licenses from it? Don't you want it to be > >> possible for people to use it? > > > > > > Quite the opposite - I want information sharing on the Python Wiki be > free > > of the bullshit of implied rights. > > > >> > >> When there is no permission to use it given in the license, the > >> default is "you can't use it". > > > > > > Right. The copyright law in most countries require permission _by > default_ > > for public stuff, that why the stuff needs to be explicitly unlicensed > > - http://unlicense.org/ > > Despite a cute name, that is, in fact, a license, and not a very good one. > Please see http://creativecommons.org/about/cc0 for explanation of the > problems with putting things in public domain. IMO the problems with the copyright law referred by this link are already summarized in my quote few lines above, and CC0 is another choice to solve these. Perhaps it would be more clear if we keep discussion focused on particular problems with content in Python wiki and in particular the question - Why CC0 dedication to public domain or unlicensing is not a very good choice? and If there is a better one? -- anatoly t.
_______________________________________________ pydotorg-www mailing list [email protected] http://mail.python.org/mailman/listinfo/pydotorg-www
