You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by Marko Rodriguez <ok...@gmail.com> on 2015/01/26 17:32:59 UTC
Questions on Migrating Code from GitHub to Apache.
Hi mentors,
Stephen and I are a bit confused as to next steps for migrating code.
Here are some questions:
1. Should a mentor first review the GitHub code to find any problems with licensing before migrating?
- or migrate over and review in Apache Git?
2. Should we prefix each file with the Apache Foundation /** **/ preambled header?
3. CLAs for all active contributors to TinkerPop3.
- TinkerPop3 has the following contributors and we have an e-CLA that each contributor signed using https://www.clahub.com/. (I sent the CLA in a private@ thread to Hadrian)
https://github.com/tinkerpop/tinkerpop3/graphs/contributors
- Is this sufficient for migration and/or do we need to get the Apache CLA signed for each contributor?
4. Once we migrate over, is it easy to get the mirror back to GitHub going so we can continue to reference those URLs in our emails/etc?
We would like to migrate all the code over in "one go" so that we can continue to develop against a single repository and not have our attention spit between two repos.
Thank you for your time,
Marko.
http://markorodriguez.com
Re: Questions on Migrating Code from GitHub to Apache.
Posted by James Carman <ja...@carmanconsulting.com>.
I haven't heard anything lately. I believe there was a request to get
some help from the legal folks.
On Wed, Jan 28, 2015 at 10:49 AM, Marko Rodriguez <ok...@gmail.com> wrote:
> Hi guys,
>
> Any movement on the software grant application? James Carman?
>
> Thank you,
> Marko.
>
> http://markorodriguez.com
>
> On Jan 26, 2015, at 2:50 PM, David Nalley <da...@gnsa.us> wrote:
>
>> It may be enough, you'll need to send it to secretary@ - if he
>> accepts, it's enough. He'll reply with feedback if not.
>>
>> --David
>>
>> On Mon, Jan 26, 2015 at 3:57 PM, Marko Rodriguez <ok...@gmail.com> wrote:
>>> Hey,
>>>
>>> I sent the SGA on the private@ list at it contains the CLAs from all the TinkerPop Contributors.
>>>
>>> Is what I sent sufficient?
>>>
>>> Thanks,
>>> Marko.
>>>
>>> http://markorodriguez.com
>>>
>>> On Jan 26, 2015, at 1:49 PM, David Nalley <da...@gnsa.us> wrote:
>>>
>>>> We need to get the SGA in place.
>>>> Once that's is settled, we can then migrate en masse, and that really
>>>> is a trivial operation.
>>>>
>>>> --David
>>>>
>>>>
>>>> On Mon, Jan 26, 2015 at 11:32 AM, Marko Rodriguez <ok...@gmail.com> wrote:
>>>>> Hi mentors,
>>>>>
>>>>> Stephen and I are a bit confused as to next steps for migrating code.
>>>>>
>>>>> Here are some questions:
>>>>> 1. Should a mentor first review the GitHub code to find any problems with licensing before migrating?
>>>>> - or migrate over and review in Apache Git?
>>>>> 2. Should we prefix each file with the Apache Foundation /** **/ preambled header?
>>>>> 3. CLAs for all active contributors to TinkerPop3.
>>>>> - TinkerPop3 has the following contributors and we have an e-CLA that each contributor signed using https://www.clahub.com/. (I sent the CLA in a private@ thread to Hadrian)
>>>>> https://github.com/tinkerpop/tinkerpop3/graphs/contributors
>>>>> - Is this sufficient for migration and/or do we need to get the Apache CLA signed for each contributor?
>>>>> 4. Once we migrate over, is it easy to get the mirror back to GitHub going so we can continue to reference those URLs in our emails/etc?
>>>>>
>>>>> We would like to migrate all the code over in "one go" so that we can continue to develop against a single repository and not have our attention spit between two repos.
>>>>>
>>>>> Thank you for your time,
>>>>> Marko.
>>>>>
>>>>> http://markorodriguez.com
>>>>>
>>>
>
Re: Questions on Migrating Code from GitHub to Apache.
Posted by Marko Rodriguez <ok...@gmail.com>.
Hi guys,
Any movement on the software grant application? James Carman?
Thank you,
Marko.
http://markorodriguez.com
On Jan 26, 2015, at 2:50 PM, David Nalley <da...@gnsa.us> wrote:
> It may be enough, you'll need to send it to secretary@ - if he
> accepts, it's enough. He'll reply with feedback if not.
>
> --David
>
> On Mon, Jan 26, 2015 at 3:57 PM, Marko Rodriguez <ok...@gmail.com> wrote:
>> Hey,
>>
>> I sent the SGA on the private@ list at it contains the CLAs from all the TinkerPop Contributors.
>>
>> Is what I sent sufficient?
>>
>> Thanks,
>> Marko.
>>
>> http://markorodriguez.com
>>
>> On Jan 26, 2015, at 1:49 PM, David Nalley <da...@gnsa.us> wrote:
>>
>>> We need to get the SGA in place.
>>> Once that's is settled, we can then migrate en masse, and that really
>>> is a trivial operation.
>>>
>>> --David
>>>
>>>
>>> On Mon, Jan 26, 2015 at 11:32 AM, Marko Rodriguez <ok...@gmail.com> wrote:
>>>> Hi mentors,
>>>>
>>>> Stephen and I are a bit confused as to next steps for migrating code.
>>>>
>>>> Here are some questions:
>>>> 1. Should a mentor first review the GitHub code to find any problems with licensing before migrating?
>>>> - or migrate over and review in Apache Git?
>>>> 2. Should we prefix each file with the Apache Foundation /** **/ preambled header?
>>>> 3. CLAs for all active contributors to TinkerPop3.
>>>> - TinkerPop3 has the following contributors and we have an e-CLA that each contributor signed using https://www.clahub.com/. (I sent the CLA in a private@ thread to Hadrian)
>>>> https://github.com/tinkerpop/tinkerpop3/graphs/contributors
>>>> - Is this sufficient for migration and/or do we need to get the Apache CLA signed for each contributor?
>>>> 4. Once we migrate over, is it easy to get the mirror back to GitHub going so we can continue to reference those URLs in our emails/etc?
>>>>
>>>> We would like to migrate all the code over in "one go" so that we can continue to develop against a single repository and not have our attention spit between two repos.
>>>>
>>>> Thank you for your time,
>>>> Marko.
>>>>
>>>> http://markorodriguez.com
>>>>
>>
Re: Questions on Migrating Code from GitHub to Apache.
Posted by David Nalley <da...@gnsa.us>.
It may be enough, you'll need to send it to secretary@ - if he
accepts, it's enough. He'll reply with feedback if not.
--David
On Mon, Jan 26, 2015 at 3:57 PM, Marko Rodriguez <ok...@gmail.com> wrote:
> Hey,
>
> I sent the SGA on the private@ list at it contains the CLAs from all the TinkerPop Contributors.
>
> Is what I sent sufficient?
>
> Thanks,
> Marko.
>
> http://markorodriguez.com
>
> On Jan 26, 2015, at 1:49 PM, David Nalley <da...@gnsa.us> wrote:
>
>> We need to get the SGA in place.
>> Once that's is settled, we can then migrate en masse, and that really
>> is a trivial operation.
>>
>> --David
>>
>>
>> On Mon, Jan 26, 2015 at 11:32 AM, Marko Rodriguez <ok...@gmail.com> wrote:
>>> Hi mentors,
>>>
>>> Stephen and I are a bit confused as to next steps for migrating code.
>>>
>>> Here are some questions:
>>> 1. Should a mentor first review the GitHub code to find any problems with licensing before migrating?
>>> - or migrate over and review in Apache Git?
>>> 2. Should we prefix each file with the Apache Foundation /** **/ preambled header?
>>> 3. CLAs for all active contributors to TinkerPop3.
>>> - TinkerPop3 has the following contributors and we have an e-CLA that each contributor signed using https://www.clahub.com/. (I sent the CLA in a private@ thread to Hadrian)
>>> https://github.com/tinkerpop/tinkerpop3/graphs/contributors
>>> - Is this sufficient for migration and/or do we need to get the Apache CLA signed for each contributor?
>>> 4. Once we migrate over, is it easy to get the mirror back to GitHub going so we can continue to reference those URLs in our emails/etc?
>>>
>>> We would like to migrate all the code over in "one go" so that we can continue to develop against a single repository and not have our attention spit between two repos.
>>>
>>> Thank you for your time,
>>> Marko.
>>>
>>> http://markorodriguez.com
>>>
>
Re: Questions on Migrating Code from GitHub to Apache.
Posted by Marko Rodriguez <ok...@gmail.com>.
Hey,
I sent the SGA on the private@ list at it contains the CLAs from all the TinkerPop Contributors.
Is what I sent sufficient?
Thanks,
Marko.
http://markorodriguez.com
On Jan 26, 2015, at 1:49 PM, David Nalley <da...@gnsa.us> wrote:
> We need to get the SGA in place.
> Once that's is settled, we can then migrate en masse, and that really
> is a trivial operation.
>
> --David
>
>
> On Mon, Jan 26, 2015 at 11:32 AM, Marko Rodriguez <ok...@gmail.com> wrote:
>> Hi mentors,
>>
>> Stephen and I are a bit confused as to next steps for migrating code.
>>
>> Here are some questions:
>> 1. Should a mentor first review the GitHub code to find any problems with licensing before migrating?
>> - or migrate over and review in Apache Git?
>> 2. Should we prefix each file with the Apache Foundation /** **/ preambled header?
>> 3. CLAs for all active contributors to TinkerPop3.
>> - TinkerPop3 has the following contributors and we have an e-CLA that each contributor signed using https://www.clahub.com/. (I sent the CLA in a private@ thread to Hadrian)
>> https://github.com/tinkerpop/tinkerpop3/graphs/contributors
>> - Is this sufficient for migration and/or do we need to get the Apache CLA signed for each contributor?
>> 4. Once we migrate over, is it easy to get the mirror back to GitHub going so we can continue to reference those URLs in our emails/etc?
>>
>> We would like to migrate all the code over in "one go" so that we can continue to develop against a single repository and not have our attention spit between two repos.
>>
>> Thank you for your time,
>> Marko.
>>
>> http://markorodriguez.com
>>
Re: Questions on Migrating Code from GitHub to Apache.
Posted by David Nalley <da...@gnsa.us>.
We need to get the SGA in place.
Once that's is settled, we can then migrate en masse, and that really
is a trivial operation.
--David
On Mon, Jan 26, 2015 at 11:32 AM, Marko Rodriguez <ok...@gmail.com> wrote:
> Hi mentors,
>
> Stephen and I are a bit confused as to next steps for migrating code.
>
> Here are some questions:
> 1. Should a mentor first review the GitHub code to find any problems with licensing before migrating?
> - or migrate over and review in Apache Git?
> 2. Should we prefix each file with the Apache Foundation /** **/ preambled header?
> 3. CLAs for all active contributors to TinkerPop3.
> - TinkerPop3 has the following contributors and we have an e-CLA that each contributor signed using https://www.clahub.com/. (I sent the CLA in a private@ thread to Hadrian)
> https://github.com/tinkerpop/tinkerpop3/graphs/contributors
> - Is this sufficient for migration and/or do we need to get the Apache CLA signed for each contributor?
> 4. Once we migrate over, is it easy to get the mirror back to GitHub going so we can continue to reference those URLs in our emails/etc?
>
> We would like to migrate all the code over in "one go" so that we can continue to develop against a single repository and not have our attention spit between two repos.
>
> Thank you for your time,
> Marko.
>
> http://markorodriguez.com
>
Re: Questions on Migrating Code from GitHub to Apache.
Posted by Hadrian Zbarcea <hz...@gmail.com>.
It usually comes as a software grant [1]. In this case, not sure what
the easiest thing is. Attach the original iclas to the grant?
Hadrian
[1] https://www.apache.org/licenses/software-grant.txt
On 01/26/2015 11:32 AM, Marko Rodriguez wrote:
> Hi mentors,
>
> Stephen and I are a bit confused as to next steps for migrating code.
>
> Here are some questions:
> 1. Should a mentor first review the GitHub code to find any problems with licensing before migrating?
> - or migrate over and review in Apache Git?
> 2. Should we prefix each file with the Apache Foundation /** **/ preambled header?
> 3. CLAs for all active contributors to TinkerPop3.
> - TinkerPop3 has the following contributors and we have an e-CLA that each contributor signed using https://www.clahub.com/. (I sent the CLA in a private@ thread to Hadrian)
> https://github.com/tinkerpop/tinkerpop3/graphs/contributors
> - Is this sufficient for migration and/or do we need to get the Apache CLA signed for each contributor?
> 4. Once we migrate over, is it easy to get the mirror back to GitHub going so we can continue to reference those URLs in our emails/etc?
>
> We would like to migrate all the code over in "one go" so that we can continue to develop against a single repository and not have our attention spit between two repos.
>
> Thank you for your time,
> Marko.
>
> http://markorodriguez.com
>
>