From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Francois Ozog <francois.ozog@linaro.org>
Cc: Matt Spencer <Matt.Spencer@arm.com>,
"O'Driscoll, Tim" <tim.odriscoll@intel.com>,
Dave Neary <dneary@redhat.com>,
moving@dpdk.org
Subject: Re: [dpdk-moving] Reminder on Today's Meeting and Updated Charter
Date: Tue, 29 Nov 2016 14:50:49 +0100 [thread overview]
Message-ID: <1582367.tENoNDAmhm@xps13> (raw)
In-Reply-To: <CAHFG_=Vo4UXAj0FvJ0OjLroSQpWPxH9hDacRJJG0Xqj+EpGtbg@mail.gmail.com>
2016-11-29 14:20, Francois Ozog:
> Hi Matt,
>
> I coy/paste Mike Dolan's comment on CLA:
>
> "Most of our projects use the Apache CCLA if a CLA is required. We have a
> fully automated e-signature management system for CLA signings. You can see
> the CCLA for Kubernetes for example here:
> https://identity.linuxfoundation.org/content/cncf-corporate-contributor-license-agreement
> <https://www.google.com/url?q=https://identity.linuxfoundation.org/content/cncf-corporate-contributor-license-agreement&sa=D&ust=1480344167438000&usg=AFQjCNEbhgdm3M7dTLB1Xxwp8af7LJcC-A>
> "
>
> I had Linaro member companie lawyers have a look at it and they said it is
> fine.
>
> So it should be nice to have such CCLA in place in DPDK.
Why?
next prev parent reply other threads:[~2016-11-29 13:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 11:08 O'Driscoll, Tim
2016-11-22 14:47 ` Vincent JARDIN
2016-11-23 22:26 ` Dave Neary
2016-11-24 12:46 ` O'Driscoll, Tim
2016-11-24 13:26 ` Thomas Monjalon
2016-11-24 14:16 ` Matt Spencer
2016-11-24 17:27 ` O'Driscoll, Tim
2016-11-24 18:07 ` Vincent Jardin
2016-11-24 18:20 ` Ed Warnicke
2016-11-24 19:05 ` Vincent Jardin
2016-11-24 18:13 ` Ed Warnicke
2016-11-29 13:20 ` Francois Ozog
2016-11-29 13:50 ` Thomas Monjalon [this message]
2016-11-29 14:25 ` Francois Ozog
2016-11-29 14:50 ` Vincent JARDIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1582367.tENoNDAmhm@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=Matt.Spencer@arm.com \
--cc=dneary@redhat.com \
--cc=francois.ozog@linaro.org \
--cc=moving@dpdk.org \
--cc=tim.odriscoll@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).