incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig Russell <>
Subject Re: Does Zipkin need to sign a SGA ?
Date Wed, 19 Sep 2018 15:09:39 GMT
Hi Alex,

Without going into history let's discuss the current guidance:

If you want to cite historical references that conflict with this, we can have that discussion.

Establishing provenance is one of the primary tasks of a project in incubation. In order to
change the headers on code, the owners of the IP for that code need to agree. SGA or ICLA
is documentation of that agreement.



> On Sep 18, 2018, at 11:38 PM, Alex Harui <> wrote:
> I may be mis-remembering, but I thought that an SGA wasn't required for ALv2 code.  OpenZipkin
appears to be ALv2.  The licenses in the SGA are pretty much the same as in ALv2.
> I thought that for ALv2 code, we mostly cared that the community documented that it was
willing to make the move from wherever the code is now to the ASF, and it wasn't super important
to get approval from folks with minor contributions as long as we were confident their contributions
were under ALv2.
> Once the community has approved the move to the ASF, any copyright holder or an agent
can replace the headers with the ASF header.
> Of course, I could be wrong...
> -Alex
> On 9/18/18, 7:00 PM, "Adrian Cole" < <>>
>    Hi, John
>    Thanks for the input. So, I would hazard a guess that Twitter folks
>    would like to help with this. I'm not sure who would want to hunt
>    through the management chain to find someone to reverse-own a decision
>    made 3 years ago, though! Regardless, on my part, I'll see if I can
>    find a champion inside Twitter to resurrect and SGA.
>    Best,
>    -A
>    On Wed, Sep 19, 2018 at 9:36 AM John D. Ament <> wrote:
>> Thanks Adrian.  Some comments/banter below.
>> Migrating a repository from one org to another does not require an SGA.  If
>> it did, we would not be able to have code living in our repos that had
>> headers other than the ASF standard headers (e.g. BSD licenses, or Apache
>> License w/ different copyright statements).  The SGA is used to replace the
>> headers with the standard ASF headers.  We should not block migrating the
>> repositories over while the SGA/ICLA is worked out.
>> Resolving the SGA/ICLA situation would block graduation - we should ensure
>> that the provenance is in place, which is part of the incubation process.
>> This doesn't need to be solved on day 1, but by the time the podling is
>> ready to graduate.
>> With that said, from a pure foundation standpoint it would be ideal to
>> receive a SGA from Twitter.  Even if the current code doesn't match the
>> code at the time of Twitter's conversion, it gives us a better IP history
>> for the codebase to answer questions and deal with any potential problems
>> that may come up along the way.  However, to be realistic I believe if we
>> receive an ICLA from the primary contributors based on [1], that should
>> satisfy enough providence of the codebase, in addition to the contribution
>> process that Adrian has pointed out below.
>> Thoughts?
>> John
>> [1]:;;sdata=uM8FYSSrTEoprQjlxBn7CaGMUUKN1q5kFIKZbwJK5OI%3D&amp;reserved=0
>> On Tue, Sep 18, 2018 at 9:25 PM Adrian Cole < <>>
>>> There was a process involved at Twitter when we first moved it to the
>>> openzipkin organization. It was 100% clear that this was an act for
>>> the community to control the code.  Senior management were involved
>>> After that, all the repositories had contributing files like the below
>>> indicating that all changes we to be redistributable under ASL
>>> <;;sdata=8%2Fx%2BpmxlUvivCroYblZxO7XmCoSlqH%2BLyYTaEeqD3GM%3D&amp;reserved=0
>>> There was no collection of contributor agreements beyond this. Most of
>>> the code except save some UI assets have been completely rewritten
>>> since the migration to OpenZipkin a few years back.
>>> Hope these details help,
>>> -A
>>> On Wed, Sep 19, 2018 at 9:09 AM Craig Russell < <>>
>>> wrote:
>>>> Hi Mick,
>>>> tldr; with my Incubator PMC hat on, "all that needs to be done" is to
>>> establish that all of the copyright owners sign either a Software Grant or
>>> an ICLA.
>>>> In order to establish that Apache has the rights to the code base, every
>>> line of code needs to have its provenance researched.
>>>> Looking at the proposal;;sdata=V%2FPLstoMZBDO%2B8nIMbB%2BDZudrj4dN4eqEy6gXXSMtZg%3D&amp;reserved=0
>>> it seems like most of the code is in the github repository
. Is there any code coming from
>>> another source? Was the original code from Twitter granted to OpenZipkin?
>>> Is there any documentation of that copyright transfer? Does Twitter retain
>>> any rights?
>>>> The capitalization of the "Initial Source" section is a bit strange. But
>>> can we assume that the only committers to the project are listed at
>>>> The proposal also says that "All source code is copyrighted to 'The
>>> OpenZipkin Authors', to which the existing core community(members list in
>>> Initial Committers) has the rights to re-assign to the ASF. "
>>>> It looks like there were many people who contributed a few lines of
>>> code. Did they sign anything like a Contributor Agreement that grants their
>>> copyright to The OpenZipkin Authors?
>>>> Craig
>>>>> On Sep 18, 2018, at 4:58 PM, Mick Semb Wever < <>>
>>>>> It's come up that the migration of the github Zipkin repositories to
>>> ASF requires either a signed SGA or a sign-off from the Secretary. Chris
>>> raised this on `INFRA-16989 – Zipkin incubator project request for the
>>> GitHub repositories moving service`.
>>>>> I was under the impression that if the Copyright was already held by
>>> the community, it is held by 'The OpenZipkin Authors', that the ICLA from
>>> all those authors would suffice and a SGA not be required. And it's news to
>>> me that this would also require a sign-off from the ASF Secretary.
>>>>> What's the correct process here? who can help? should I forward the
>>> question to the Secretary?
>>>>> regards,
>>>>> Mick
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: <>
>>>>> For additional commands, e-mail: <>
>>>> Craig L Russell
>>>> Secretary, Apache Software Foundation
>>>> <> < <>>;;sdata=z8%2BGhYTmcV1p7Ts%2FixW8BZ6Kyv02YRe4%2FyKMGV25d2k%3D&amp;reserved=0
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: <>
>>> For additional commands, e-mail: <>
>    ---------------------------------------------------------------------
>    To unsubscribe, e-mail:
>    For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Craig L Russell
Secretary, Apache Software Foundation <> <>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message