<div dir="ltr">I did a little digging -- I think we could get a lightweight CLA with <a href="https://github.com/cla-assistant/cla-assistant">https://github.com/cla-assistant/cla-assistant</a> which allows for signing CLAs right inside pull requests. I'm happy to volunteer to set it up if we decide to go this way.<div><br></div><div>Cameron has an excellent point about us already having the most permissive license. :) </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 30, 2019 at 1:05 PM Jo Cook <<a href="mailto:jo.k.cook@gmail.com">jo.k.cook@gmail.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"><div>I'm in favour of 4, which could be made even better by adding it to a pull request template. That way even people who contribute by editing a file in the github interface will see it, whether they like it or not!</div><div><br></div><div>Jo<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 30, 2019 at 7:24 PM Sanket Totewar <<a href="mailto:sanket@totewar.com" target="_blank">sanket@totewar.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><div dir="auto">I like 3. Seamless... But happy with 4 or 5 too.</div></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 30 Jul 2019 at 22:37, Jared Morgan <<a href="mailto:jaredleonmorgan@gmail.com" target="_blank">jaredleonmorgan@gmail.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="auto">I'd be OK with 4 if necessary and definitely 5. </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue., 30 Jul. 2019, 21:28 Cameron Shorter, <<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.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">From my recent reading:<div>There are a few variants of CLAs.</div><div>1. Developers/Employers assign their code ownership to an entity - typically a trusted not-for-profit. The not-for-profit can later relicense as required. This appears to be the option that Google legal explained to Erin.</div><div>2. Developers/Employers own their code, but provide a statement saying they confirm that the not-for-profit can use under license provided. </div><div><br></div><div>Both these options require a legal entity (which we haven't sourced yet). Both require a system for processing CLA statements (such as accepting signed statements). Both are a pain to manage.</div><div>For 1. having the ability to relicense can be both a positive and negative, more likely a negative as you will need to get a CLA for any library you depend upon.</div><div>Being able to relicense is important if you want to make the license more permissive (eg from GPL to MIT license).</div><div>By selecting the CC0 licence (for templates) we are proposing to be as permissive as possible, so anyone can relicense to any other license. So the value of relicensing is not an issue in that case.</div><div><br></div><div>3. The DCO is lighter as usually implemented is lower overhead. All developers need do is add a "--signoff" argument to a git commit message. This effectively acknowledges that in the commit you agree to the DCO statement.</div><div><br></div><div>4. We could go for a lighter version of this, by making a statement in our CONTRIBUTOR.md doc stating. If you submit a commit to our repository, then we assume that you are abiding by our DCO (which we reference and include on our site). This would be the easiest option, and has the same effort for contributors as 5.</div><div><br></div><div>5. Do nothing.</div><div><br></div><div>My preference is 3 or 4. (I haven't seen an implementation of 4 yet and would like to confirm it is a legitimate option, but there appears to be plenty of 5.)</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 30 Jul 2019 at 09:06, Erin McKean <<a href="mailto:emckean@google.com" rel="noreferrer" target="_blank">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">More answers: fwiw, turns out that the strongest argument for a CLA (over a DCO or nothing) is relicensing rights: <div><br></div><div>"Let's say the project has code samples under Apache, and</div>documentation under CC 4 (common licensing scheme). If they accept a<br>patch to the docs under DCO, that patch is CC4 forever, and they don't<br>have the right to put it in the Apache code section! And vice-versa;<br>they'd have to ask each contribution author every single time.<br><br>With CLA you have relicense rights."<div><br></div><div>Also it turns out they will review a CLA (and fairly quickly) from projects not already on the approved list. :) </div><div><br>Erin</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jul 29, 2019 at 3:54 PM Erin McKean <<a href="mailto:emckean@google.com" rel="noreferrer" target="_blank">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">I heard back that given a choice between CLA/DCO, they strongly suggest an Apache-style CLA. <div><br></div><div>Am now asking about the choice between CLA and nothing. ;) </div><div><br>Thanks!</div><div><br>Erin</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jul 29, 2019 at 3:36 PM Jennifer Rondeau <<a href="mailto:jennifer.rondeau@gmail.com" rel="noreferrer" target="_blank">jennifer.rondeau@gmail.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">More reasons not to require a CLA. Google undoubtedly not the only employer with this kind of limitation.<div><br></div><div>Note that although I said I'd support a DCO, my strong recommendation is against neither CLA nor DCO.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jul 29, 2019 at 6:18 PM Erin McKean <<a href="mailto:emckean@google.com" rel="noreferrer" target="_blank">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">From the "big company" POV, I'm not allowed to sign a CLA that isn't on a (SHORT) approved list of CLAs. So it would likely be a barrier for a new/small project to get on that list.<div><br></div><div>I am asking about DCOs, will report back!</div><div><br>Erin </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jul 29, 2019 at 2:33 PM Jennifer Rondeau <<a href="mailto:jennifer.rondeau@gmail.com" rel="noreferrer" target="_blank">jennifer.rondeau@gmail.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">A CLA involves signing and in the case of the CLAs I've needed to sign review by the governing board before you're good to go. Typically automated, but a multi-step process and more complicated if you need to sign an org-based CLA (as opposed to a CLA for an individual).<div><br></div><div>A DCO is integrated with Git (GitHub and I assume other Git servers), so you provide a `--signoff` argument to your git commits. Or add it to your git alias.</div><div><br></div><div>Either way it's an extra step of some sort, not implicit.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jul 29, 2019 at 5:18 PM Jared Morgan <<a href="mailto:jaredleonmorgan@gmail.com" rel="noreferrer" target="_blank">jaredleonmorgan@gmail.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="auto">With these agreements, does anyone have to actually sign and return the agreement? Or do they take the form of "submitting your change is like signing the agreement"?<div dir="auto"><br></div><div dir="auto">I'm just following along with this thread for now because (as you can probably tell) I have never heard of this before in open source projects.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon., 29 Jul. 2019, 07:21 Jennifer Rondeau, <<a href="mailto:jennifer.rondeau@gmail.com" rel="noreferrer" target="_blank">jennifer.rondeau@gmail.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">It's been my experience working with the Kubernetes community that a CLA can pose a non-insignificant barrier to entry for new contributors, especially if they aren't already familiar with FOSS. And it's my observation from working with a range of Write the Docs communities that technical writers tend to be less familiar with FOSS norms and practices than coders -- this includes writers from large companies.<div><br></div><div>If we want to maintain a project that's an open and welcoming for all as possible, I'd support a DCO, but I also wonder whether we need or want even that much. My guess is that it would be enough to drive away at least some otherwise valuable contributors. I don't have data about how many potential contributors lack of a DCO would keep away -- anyone else?</div><div><br></div><div>Related but not quite on topic: how do we want to solicit and encourage contributions? Are we assuming only contributors who are already familiar with a Git workflow? That would definitely keep some good work away, based on my experience with writing day sessions for the Write the Docs guide at WtD conferences.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jul 28, 2019 at 2:25 PM Jo Cook <<a href="mailto:jo.k.cook@gmail.com" rel="noreferrer noreferrer" target="_blank">jo.k.cook@gmail.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"><div>Personally I'm fine with the light tough DCO but happy to go with whatever works for people contributing from large companies.</div><div><br></div><div>All the best</div><div><br></div><div>Jo<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jul 28, 2019 at 1:15 PM Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" rel="noreferrer noreferrer" target="_blank">cameron.shorter@gmail.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">It has been ~ 10 years since I last looked into open source contributor <br>
agreements, so I've been doing some research. I feel this is an <br>
important consideration for a project which is hopefully to be as <br>
central as ours will become.<br>
<br>
It is about having contributors confirm they are allowed to give to our <br>
project and to agree we can distribute contributions under our open <br>
licenses.<br>
We have a few options: do nothing, old heavy weight Contributor License <br>
Agreement (CLA), or lightweight Developer Certificate of Origin (DCO)<br>
Pros and cons are explained in Producing Open Source Software: <br>
<a href="https://producingoss.com/en/contributor-agreements.html#developer-certificate-of-origin" rel="noreferrer noreferrer noreferrer" target="_blank">https://producingoss.com/en/contributor-agreements.html#developer-certificate-of-origin</a><br>
I propose we adopt the light DCO: <a href="https://developercertificate.org/" rel="noreferrer noreferrer noreferrer" target="_blank">https://developercertificate.org/</a><br>
<br>
I'd like to hear if anyone has any opinions or experience in this area <br>
(especially from those of you in big companies which have legal <br>
departments which may be opinionated.)<br>
<br>
After we've discussed for a few days (weeks if being debated), I'll put <br>
together a motion to vote on.<br>
<br>
Cheers,<br>
<br>
-- <br>
Cameron Shorter<br>
Technology Demystifier<br>
Open Technologies and Geospatial Consultant<br>
<br>
M +61 (0) 419 142 254<br>
<br>
_______________________________________________<br>
SeasonOfDocs mailing list<br>
<a href="mailto:SeasonOfDocs@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">SeasonOfDocs@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail-m_-6702178831341743438gmail-m_-8285043556314919745m_-1619797398952127495m_-2093734746967556632gmail-m_7606012145896584373gmail-m_6315377600278890152gmail-m_7403531451136431936gmail-m_-5903426309018284258gmail-m_-6234627366832736802gmail-m_-6836959172058582935m_1423712025437714053gmail-m_304411448907830057gmail_signature">------------------------<br><a href="http://about.me/jocook" rel="noreferrer noreferrer" target="_blank">http://about.me/jocook</a></div>
_______________________________________________<br>
SeasonOfDocs mailing list<br>
<a href="mailto:SeasonOfDocs@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">SeasonOfDocs@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
</blockquote></div>
_______________________________________________<br>
SeasonOfDocs mailing list<br>
<a href="mailto:SeasonOfDocs@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">SeasonOfDocs@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
</blockquote></div>
</blockquote></div>
_______________________________________________<br>
SeasonOfDocs mailing list<br>
<a href="mailto:SeasonOfDocs@lists.osgeo.org" rel="noreferrer" target="_blank">SeasonOfDocs@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_-6702178831341743438gmail-m_-8285043556314919745m_-1619797398952127495m_-2093734746967556632gmail-m_7606012145896584373gmail-m_6315377600278890152gmail-m_7403531451136431936gmail-m_-5903426309018284258gmail_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" rel="noreferrer" target="_blank">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>
</blockquote></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_-6702178831341743438gmail-m_-8285043556314919745m_-1619797398952127495m_-2093734746967556632gmail-m_7606012145896584373gmail-m_6315377600278890152gmail_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" rel="noreferrer" target="_blank">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>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_-6702178831341743438gmail-m_-8285043556314919745m_-1619797398952127495m_-2093734746967556632gmail-m_7606012145896584373gmail_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" rel="noreferrer" target="_blank">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>
_______________________________________________<br>
SeasonOfDocs mailing list<br>
<a href="mailto:SeasonOfDocs@lists.osgeo.org" rel="noreferrer" target="_blank">SeasonOfDocs@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_-6702178831341743438gmail-m_-8285043556314919745m_-1619797398952127495m_-2093734746967556632gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><div><span style="font-size:12.8px">Cameron Shorter</span><br></div><div>Technology Demystifier</div><div>Open Technologies and Geospatial Consultant</div><div><br></div><div>M +61 (0) 419 142 254</div><div><br></div></div><div><br><br></div></div></div></div></div></div></div></div></div>
_______________________________________________<br>
SeasonOfDocs mailing list<br>
<a href="mailto:SeasonOfDocs@lists.osgeo.org" rel="noreferrer" target="_blank">SeasonOfDocs@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
</blockquote></div>
_______________________________________________<br>
SeasonOfDocs mailing list<br>
<a href="mailto:SeasonOfDocs@lists.osgeo.org" target="_blank">SeasonOfDocs@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
</blockquote></div></div>
_______________________________________________<br>
SeasonOfDocs mailing list<br>
<a href="mailto:SeasonOfDocs@lists.osgeo.org" target="_blank">SeasonOfDocs@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail-m_-6702178831341743438gmail_signature">------------------------<br><a href="http://about.me/jocook" target="_blank">http://about.me/jocook</a></div>
_______________________________________________<br>
SeasonOfDocs mailing list<br>
<a href="mailto:SeasonOfDocs@lists.osgeo.org" target="_blank">SeasonOfDocs@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_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">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>