Re: [PATCH v3 03/16] reftable: add LICENSE

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Nov 30, 2020, 21:21 UTC
Message-ID: <CAMP44s0zoekLZYQ=r516jjdsGGQ2Y7m1fXpwW2BBJsGjQ5sseA@mail.gmail.com>
In-Reply-To: <CAFQ2z_MXF0wO76tVTcBuJJp0CwjVoVfE11BOYYQ7Y7h1h_VwJg@mail.gmail.com>

On Mon, Nov 30, 2020 at 2:28 PM Han-Wen Nienhuys <hanwen@google.com> wrote:

Show 8 quoted lines

>
> On Mon, Nov 30, 2020 at 12:26 PM Han-Wen Nienhuys <hanwen@google.com> wrote:
> > Until the reftable code is actually merged into git, I work on the
> > reftable library itself at github.com/google/reftable. I've asked our
> > opensource team if we could switch off the CLA enforcement for this
> > repo, to facilitate back & forth imports of fixes.
>
> I've asked our lawyers, but this is not currently possible, unfortunately.

Maybe I'm not understanding something correctly.

Git's license is GPLv2. When you add your Signed-off-by line you are saying you are authorized to provide this code to the Git project under its open source license.

Therefore, I should be able to take your patches, and rework them in any way I want as long as I keep Git's license.

I don't need your permission, you are supposedly giving it by adding your Signed-off-by line.

Read: https://developercertificate.org/

If you are not authorized to provide these patches under an open source license, then you should not add your Signed-off-by line.

And if these patches cannot be used by the Git project, nor can we work on them in a collaborative manner, then what's the point in providing them?

Sounds to me Google has not made its mind about actually contributing these changes.

Or am I missing something?

Cheers.

-- 
Felipe Contreras