<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 29 November 2016 at 14:50, Thomas Monjalon <span dir="ltr"><<a href="mailto:thomas.monjalon@6wind.com" target="_blank">thomas.monjalon@6wind.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">2016-11-29 14:20, Francois Ozog:<br>
<span class="gmail-">> Hi Matt,<br>
><br>
> I coy/paste Mike Dolan's comment on CLA:<br>
><br>
> "Most of our projects use the Apache CCLA if a CLA is required. We have a<br>
> fully automated e-signature management system for CLA signings. You can see<br>
> the CCLA for Kubernetes for example here:<br>
> <a href="https://identity.linuxfoundation.org/content/cncf-corporate-contributor-license-agreement" rel="noreferrer" target="_blank">https://identity.<wbr>linuxfoundation.org/content/<wbr>cncf-corporate-contributor-<wbr>license-agreement</a><br>
</span>> <<a href="https://www.google.com/url?q=https://identity.linuxfoundation.org/content/cncf-corporate-contributor-license-agreement&sa=D&ust=1480344167438000&usg=AFQjCNEbhgdm3M7dTLB1Xxwp8af7LJcC-A" rel="noreferrer" target="_blank">https://www.google.com/url?q=<wbr>https://identity.<wbr>linuxfoundation.org/content/<wbr>cncf-corporate-contributor-<wbr>license-agreement&sa=D&ust=<wbr>1480344167438000&usg=<wbr>AFQjCNEbhgdm3M7dTLB1Xxwp8af7LJ<wbr>cC-A</a>><br>
<span class="gmail-">> "<br>
><br>
> I had Linaro member companie lawyers have a look at it and they said it is<br>
> fine.<br>
><br>
> So it should be nice to have such CCLA in place in DPDK.<br>
<br>
</span>Why?<br>
</blockquote></div><br>In an early mail I said:</div><div class="gmail_extra"><br></div><div class="gmail_extra">"<span style="font-size:12.8px">I am not a lawyer and I am out of my league here. That said, we all know that</span><span style="font-size:12.8px"> </span><span class="gmail-il" style="font-size:12.8px">NDA</span><span style="font-size:12.8px">'s cannot be executed by any employee of a company. So, the DPDK signoff is nice, but why implement a policy that is less binding for something that may be involving very high liability issues? </span><div style="font-size:12.8px"><br></div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">DPDK says precisely "The purpose of the signoff is explained in the Developer’s Certificate of Origin section of the Linux kernel guidelines.". The following note says the contributor has to "understand" DCO...</div><div style="font-size:12.8px">So unless I have missed something, nothing says that a contributor SHALL COMPLY to anything. And even if you change the sentences to include the word comply:</div><div style="font-size:12.8px">- their should be a DPDK DCO not a pointer to some external project</div><div style="font-size:12.8px">- do you have properly recorded in your books a paer signed by an authorized representative of a company ?</div><div style="font-size:12.8px">- the DCO itslef is somewhat loose: "The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license". It does not say it is:</div><div style="font-size:12.8px"> . free from patents</div><div style="font-size:12.8px"> . free to use in large scale production by an end customer (not a developper). Or more precisely, the developper (say the NEP) has the right to sell and the customer (the operator) has been transfered the right to use.</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">Bottom line, it is desirable that companies properly engage their responsability for licence, patents and copyright aspects.<br></div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px"><div>The CLA should be signed by each contributor company at the moment of joining: the company liability is engaged, not just the employee when submitting patches.</div><div><br></div><div>There is probably some additional statement to be done for already contributed code."</div><div><br></div></div><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><table style="font-size:small" border="0" cellpadding="0" cellspacing="0"><tbody><tr><td style="padding-right:10px" valign="top"><a href="http://www.linaro.org/" title="Linaro" style="color:rgb(17,85,204)" target="_blank"><img src="http://www.mydesignpad.com/email-sig/linaro/linaro-logo-web.png" alt="Linaro" border="0" height="46px" width="72px"></a></td><td valign="top"><table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td style="font-family:arial,helvetica,"sans serif";white-space:nowrap;font-size:9pt;padding-top:0px;color:rgb(87,87,87)" valign="top"><span style="font-weight:bold">François-Frédéric Ozog</span> <span style="color:rgb(161,161,161)">|</span> <i>Director Linaro Networking Group</i></td></tr><tr><td style="font-family:arial,helvetica,"sans serif";white-space:nowrap;font-size:9pt;padding-top:2px;color:rgb(87,87,87)" valign="top">T: <a href="tel:%2B33.67221.6485" value="+393384075993" style="color:rgb(17,85,204)" target="_blank">+33.67221.6485</a><br><a href="mailto:francois.ozog@linaro.org" style="color:rgb(87,87,87);text-decoration:none" target="_blank">francois.ozog@linaro.org</a> <span style="color:rgb(161,161,161)">|</span> Skype: ffozog</td></tr></tbody></table></td></tr></tbody></table></div></div></div></div></div><div><div><br style="font-size:small"></div></div></div></div></div></div></div>
</div></div>