2009/12/4 Tom Ellis <span dir="ltr"><<a href="mailto:tom-lists-clug2@jaguarpaw.co.uk">tom-lists-clug2@jaguarpaw.co.uk</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thu, Dec 03, 2009 at 11:55:59PM +0000, Sam Kuper wrote:<br>
> Incidentally, we should probably agree on a license to use for the content<br>
> on the new wiki. I suggest CC-BY-SA<br>
</div>> 3.0<<a href="http://creativecommons.org/licenses/by-sa/3.0/" target="_blank">http://creativecommons.org/licenses/by-sa/3.0/</a>>,<br>
<div class="im">> same as Wikipedia. How does that sound?<br>
<br>
</div>I feel if we need to think about licences for the wiki we're doing something<br> wrong (i.e. there's too much import[ant] content on it that should be elsewhere)<br>
<div class="im"><br>
> Tom and Wawrzyniec, as the only other people who've contributed to the wiki<br>
> so far, would you both be willing to retroactively license your<br>
> contributions under CC-BY-SA-3.0?<br>
<br>
</div>The above notwithstanding, I hereby release everything I've written on the wiki so far into the public domain.<br></blockquote><div><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
</blockquote></div><div>Fair points. I tend to favour copyleft over PD* but I'd be happy with either for the CLUG wiki. Basically, I just want to put a license declaration in place that will let people use the wiki without the law of implicit copyright casting a shadow over their contributions. All being well, once the license is in place, we won't have to think or talk about it again, ever :)</div>
<div><br></div><div>Sam</div><div><br></div><div>*Here's a decent articulation of the reasons why: <a href="http://www.zedshaw.com/blog/2009-07-13.html">http://www.zedshaw.com/blog/2009-07-13.html</a> . Admittedly, I doubt the CLUG wiki's going to produce anything quite as useful as Mongrel, which is why I'm not so fussed in this case :)</div>