Re: Codebase transition from GH to ASF git repo

I think recreating PR is totally up to(and should be) original author. Also I have filed an issue to enable github-jira integration for Zeppelin ( https://issues.apache.org/jira/browse/INFRA-9335) Best, moon On Wed, Mar 25, 2015 at 5:43 PM Jongyoul Lee wrote: > Alex, > > Thanks for good workf

Re: Codebase transition from GH to ASF git repo

Alex, Thanks for good workflow. Can I make a same PR on incubator-zeppelin now? I will also make a Jira ticket. Regards, JL On Wed, Mar 25, 2015 at 5:13 PM, Alex B. wrote: > Congratulations everybody https://github.com/apache/incubator-zeppelin > working! > > Re-creating 17 PRs manually for d

Re: Codebase transition from GH to ASF git repo

Congratulations everybody https://github.com/apache/incubator-zeppelin working! Re-creating 17 PRs manually for discussion purpose sounds not that bad (may be it's up to original PR authors?) AND after issues migration is finished we should have a JIRA tickets for all of them too. Then merge some

Re: Codebase transition from GH to ASF git repo

First, congrat!! I've checked tat git repo. In my opinion about existing PR, we can make a same PR under github/apa/incubator-zeppelin because there are 17 PRs opened for now. I think It's easy to migrate and the most efficient way. Regards, Jongyoul Lee On Wed, Mar 25, 2015 at 1:41 PM, moon soo

Re: Codebase transition from GH to ASF git repo

INFRA-9305 resolved and git mirror is on http://git.apache.org/incubator-zeppelin.git I'll start migrate homepage source code, too. One thing to discuss is about existing PR. SGA is signed and sent by 20, Mar 2014 from NFLabs. And i'm not sure the S

Re: Codebase transition from GH to ASF git repo

Sounds nice. I'm looking forward to the migration. Best regards, Hyunsik On Sat, Mar 21, 2015 at 7:33 AM, Alex wrote: > Sound a good! > > Yes, I think it will work although because of that issue we are not going to > be able to keep the same issue numbers in GH and Jira. > > Will try to delete

Re: Codebase transition from GH to ASF git repo

Sound a good! Yes, I think it will work although because of that issue we are not going to be able to keep the same issue numbers in GH and Jira. Will try to delete it tomorrow and see if that helps, will let you know. -- Kind regards, Alexander > On 21 Mar 2015, at 21:44, moon soo Lee wrote:

Re: Codebase transition from GH to ASF git repo

Issue for github mirror filed. https://issues.apache.org/jira/browse/INFRA-9305 I think we're ready to start issue migration. Once it's done, i'll turn off 'issue' feature on github.com/NFLabs/zeppelin and file an issue to turn on github integration. One thing is, JIRA have an issue created https

Re: Codebase transition from GH to ASF git repo

Great news! As discussed before I can help with issues migration. On Sat, Mar 21, 2015 at 2:19 PM, Jongyoul Lee wrote: > Good news!! > > On Sat, Mar 21, 2015 at 4:06 AM, moon soo Lee wrote: > > > SGA is sent and master branch of https://github.com/NFLabs/zeppelin.git > > pushed to > > > > http

Re: Codebase transition from GH to ASF git repo

Good news!! On Sat, Mar 21, 2015 at 4:06 AM, moon soo Lee wrote: > SGA is sent and master branch of https://github.com/NFLabs/zeppelin.git > pushed to > > https://git-wip-us.apache.org/repos/asf/incubator-zeppelin > > > Next step would be > > 1. enable mirror on github (INFRA) > > 2. migrate iss

Re: Codebase transition from GH to ASF git repo

SGA is sent and master branch of https://github.com/NFLabs/zeppelin.git pushed to https://git-wip-us.apache.org/repos/asf/incubator-zeppelin Next step would be 1. enable mirror on github (INFRA) 2. migrate issues to JIRA 3. enable github integration (INFRA) Issue to INFRA (github mirror and

Re: Codebase transition from GH to ASF git repo

If all contributions to Zeppelin legally belongs to NFLabs I think we could just attach the full history donation. - Henry On Tue, Jan 20, 2015 at 3:53 AM, Alex wrote: > I have a question to contributors: do we want full Git history to be donated > to ASF and migrated to ASF git or only the lat

Re: Codebase transition from GH to ASF git repo

I have a question to contributors: do we want full Git history to be donated to ASF and migrated to ASF git or only the latest state would be enough I.e HEAD of the master? Therefor another question is to mentors: in case of full history donation, would it be enough to just mention full history

Re: Codebase transition from GH to ASF git repo

On Thu, Jan 8, 2015 at 7:03 PM, Alex wrote: > Yes, NFLabs is a legal entity incorporated in South Korea, here is CTO on > the list. > And so far we assumed the same - that NFLabs retained copyright on the > entire codebase until now. If NFLabs is within its legal right to control the entire code

Re: Codebase transition from GH to ASF git repo

Yes, NFLabs is a legal entity incorporated in South Korea, here is CTO on the list. And so far we assumed the same - that NFLabs retained copyright on the entire codebase until now. So is there something else we can do to help with subj? (like tracking down individual contributors and asking for S

Re: Codebase transition from GH to ASF git repo

I am a cto and one of the board members of NFLabs Inc. I think i can help legal issues related NFLabs Inc for codebase transition. Best, moon 2015년 1월 7일 수요일, Roman Shaposhnik님이 작성한 메시지: > This could be a complicated (and very important!) subject, but let me > try to simplify this conversation a

Re: Codebase transition from GH to ASF git repo

This could be a complicated (and very important!) subject, but let me try to simplify this conversation a bit: on your project website I see this: "© 2014 NFLabs Inc" Presumably, NFLabs Inc is the legal entity that holds the rights to the entire codebase. If that's the case, is there any chance we

Re: Codebase transition from GH to ASF git repo

Hi, Maybe we should ask to people who contribute the most? because asking for people who did only one commit doesnt make sence to me. But maybe i am wrong. Lets ask to our mentor to help us to clarify this. And in the Apache License, there is a point about contribution (I am not sure if i under

Re: Codebase transition from GH to ASF git repo

My guess is if there're code from non-CLA contributor, we can say it's Apache 2 license while "by submitting a patch you agree on Apache2 license" is effective. And if the contributed code has author tag, i guess keeping them in source code would okay for copyrights while non-CLA contributor does n

Re: Codebase transition from GH to ASF git repo

I'm not en expert, but as far as I understand code *Copyright* and *verification of Distribution Rights* (Licences of the dependencies) are different things\activities. And looks like both are needed for IP Clearance (although http://incubator.apache.org/ip-clearance/ does not exit for a while, say

Re: Codebase transition from GH to ASF git repo

Hi, I have curious about this right to the code base, too. What is difference between code from non-CLA contributor and one of our dependency that is Apache2 license? (when "by submitting a patch you agree on Apache2 license" is effective) Also i think we need to check license of every dependenci

Codebase transition from GH to ASF git repo

Hi, as Roman mentioned recently, *"The biggest next step is to do transition thecode base from GH to our newly minted Git repo: https://git-wip-us.apache.org/repos/asf?p=incubator-zeppelin.git This will require an SGA from w