From: krtaylor <kurt.r.taylor@gmail.com>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: openbmc@lists.ozlabs.org
Subject: Re: sdbusplus commits missing CLA
Date: Fri, 21 Feb 2020 14:10:35 -0600 [thread overview]
Message-ID: <97f984a2-e975-c620-7fc3-e3b7defb75ea@gmail.com> (raw)
In-Reply-To: <20200220203546.GF41328@patrickw3-mbp.dhcp.thefacebook.com>
On 2/20/20 2:35 PM, Patrick Williams wrote:
> Kurt,
(Not a lawyer)
> We have a few commits for the openbmc/sdbusplus repository that have
> been floating around in Gerrit since early 2018 and seem to be stuck in
> "missing CLA limbo". It appears that there was some discussion on the
> CLA at one point but I don't know what happened to it. I don't see a
> CLA from the Bosch company in the Google Doc folder.
I have not received a CLA from Bosch, or an ICLA from the developer(s)
referenced.
> https://gerrit.openbmc-project.xyz/q/owner:mark.jonas%2540de.bosch.com
>
> There was recently a request to revive this work because someone else is
> finding it useful (and we've had a feature request open for a long time
> on one of them as well). What options do we, the maintainers, have in
> this situation?
We cannot accept/merge the code until resolved. If they cannot complete
a ICLA/CCLA for this submission, it should be abandoned.
> I don't really want to blindly reimplement this feature since there was
> good work done here. There appears to have been no plagiarism issues.
> Since the commits have a S-O-B by two people from the same company, it
> seems reasonable that they fully intended to contribute this work
> publicly. I'm not looking to restart a "why do we have CLAs"
CLA's protect the company, individual and the project. We must have
permission from the company that a developer they are employing has
their permission to submit code to the project. If they don't care, that
is what the ICLA is for.
Kurt Taylor (krtaylor)
> discussion, but it seems like we need some direction on what maintainers
> should do when there is a missing CLA.
>
next prev parent reply other threads:[~2020-02-21 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 20:35 sdbusplus commits missing CLA Patrick Williams
2020-02-21 20:10 ` krtaylor [this message]
2020-02-24 0:14 ` Andrew Jeffery
2020-03-02 18:01 ` krtaylor
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=97f984a2-e975-c620-7fc3-e3b7defb75ea@gmail.com \
--to=kurt.r.taylor@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.