<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>For our templates, I'm in favour of "CC-0 with a (polite, not
binding) request for attribution". I feel there will be
situations where enforcing attribution will be inappropriate.
E.g.: A tweet or elevator pitch where every word counts.</p>
<p>Cameron<br>
</p>
<div class="moz-cite-prefix">On 3/7/19 7:46 am, Jennifer Rondeau
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CADTkFMee=ReWL-B-N29HKu=aGsAV6Tn7QFYSuBPBqsby9xJs=Q@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">I'm fine with CC-0.
<div><br>
</div>
<div>FWIW, the Kubernetes docs license is CC-BY and the code
license is Apache 2.0. We do not have an explicit code license
in the docs repository, however, which has led to some
occasional confusion when people want to use the docs with the
example code. Example code isn't quite the same thing as what
we intend to provide as code/tools -- but it's analogous
enough that I offer the story as data to back the "let's be
careful to license everything appropriately" approach.</div>
<div><br>
</div>
<div>And +1000 to a "how to attribute" section in our now nicely
named metadocumentation. </div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Jul 2, 2019 at 4:51 PM
Erin McKean <<a href="mailto:emckean@google.com"
moz-do-not-send="true">emckean@google.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">Hi folks!
<div><br>
</div>
<div>One of our action items from the past meeting was to
discuss how to license any templates or other content
produced by the project.</div>
<div><br>
</div>
<div>For background, here's a list of CC licenses: <a
href="https://creativecommons.org/licenses/"
target="_blank" moz-do-not-send="true">https://creativecommons.org/licenses/</a></div>
<div>And here are software licenses (although I don't think
that software licenses are generally useful for templates
we should probably have the licensing discussion all in
one go and since we may release tools/code that would be
better served by software licenses ....) <a
href="https://opensource.org/licenses" target="_blank"
moz-do-not-send="true">https://opensource.org/licenses</a></div>
<div><br>
</div>
<div>For templates, I think the discussion is "what do we
want to enable?" rather than "what do we want to prevent?"
since bad actors are not noted for their scrupulous
attention to licensing details. :) <br>
</div>
<div><br>
</div>
<div>CC-0 or CC-BY would be the two most open licenses. I
like CC-BY but CC-0 with a (polite, not binding) request
for attribution would be fine by me, too. FWIW, it is
extremely difficult (to put it mildly) to use anything
AGPL-licensed at Google, so I would strongly prefer to use
Apache or MIT for any code/tools.</div>
<div><br>
</div>
<div>In any case, I think we should have a "how to
attribute" section in our metadocumentation and also
reach out to the CC people when we've got something we
want to share so that we can be included in their list of
open culture resources. </div>
<div><br>
</div>
<div>Other open questions: </div>
<div> * what do other similar projects use for their
licenses?</div>
<div> * any other licenses on the no-go list? (e.g. NC-type
licenses close off a lot of possible users/contributors)</div>
<div> * would we be incorporating content that would need
SA-type licenses? Would we SA individual tools/docs? </div>
<div><br>
</div>
<div>In responding, if you could please state either a clear
preference or a "anything's fine by me" we can try for a
rough consensus quickly -- since relicensing is
problematic we probably need to have this decided before
anything substantial gets published.</div>
<div><br>
</div>
<div>Also I am NOT A LAWYER, just a copyright geek, so I
would like to collect questions and then take them to A
Real Lawyer™️ for answers.</div>
<div><br>
</div>
<div>Thanks!<br>
</div>
<div><br>
Erin<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr"
class="gmail-m_8352398781800571782gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div
style="line-height:1.5em;padding-top:10px;margin-top:10px;color:rgb(85,85,85);font-family:sans-serif"><span
style="border-width:2px 0px
0px;border-style:solid;border-color:rgb(213,15,37);padding-top:2px;margin-top:2px">Erin
McKean |</span><span style="border-width:2px
0px
0px;border-style:solid;border-color:rgb(51,105,232);padding-top:2px;margin-top:2px"> Developer
Relations Program Manager, Open Source
Strategy |</span><span style="border-width:2px
0px
0px;border-style:solid;border-color:rgb(0,153,57);padding-top:2px;margin-top:2px"> <a
href="mailto:emckean@google.com"
target="_blank" moz-do-not-send="true">emckean@google.com</a> |</span><span
style="border-width:2px 0px
0px;border-style:solid;border-color:rgb(238,178,17);padding-top:2px;margin-top:2px"> she/her</span></div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
SeasonOfDocs mailing list<br>
<a href="mailto:SeasonOfDocs@lists.osgeo.org" target="_blank"
moz-do-not-send="true">SeasonOfDocs@lists.osgeo.org</a><br>
<a
href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
SeasonOfDocs mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SeasonOfDocs@lists.osgeo.org">SeasonOfDocs@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant
M +61 (0) 419 142 254</pre>
</body>
</html>