[Grok-dev] Community docs: license and copyright?

Sebastian Ware sebastian at urbantalk.se
Tue Jan 11 11:43:28 EST 2011


This is probably what we want (allowing commercial derivatives, which might be useful if someone is writing a book):

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 88x31.png
Type: image/png
Size: 5083 bytes
Desc: not available
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20110111/1780e8d0/attachment-0001.png 
-------------- next part --------------

Attribution-ShareAlike
CC BY-SA

This license lets others remix, tweak, and build upon your work even for commercial purposes, as long as they credit you and license their new creations under the identical terms. This license is often compared to ?copyleft? free and open source software licenses. All new works based on yours will carry the same license, so any derivatives will also allow commercial use. This is the license used by Wikipedia, and is recommended for materials that would benefit from incorporating content from Wikipedia and similarly licensed projects.

http://creativecommons.org/licenses/by-sa/3.0

Mvh Sebastian


11 jan 2011 kl. 11.26 skrev Uli Fouquet:

> Hi there,
> 
> I noticed that the copyright and license links in the community docs do
> not work. We might want to discuss what should be presented there.
> 
> Contrary to the Zope repository stuff we're not bound to the "Zope
> Foundation and Contributors" copyright holder with the community docs.
> So, is it okay to say the copyright is owned by "Grok Community and
> Contributors"?
> 
> For the license it is similar. As we're not bound to ZPL (for the
> community docs), we could make everything for instance
> CreativeCommons-licensed. Would that be an option? And if so: which one
> of the various CCs would fit best? Or are there better options?
> 
> Best regards,
> 
> -- 
> Uli
> 
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev



More information about the Grok-dev mailing list