Re: Migrating Heron code to Apache

+1 for Taylor's approach as well. On Wed, Nov 8, 2017 at 10:57 AM, Bill Graham wrote: > +1 for that approach, thanks Taylor. > > > > On Wed, Nov 8, 2017 at 10:47 AM, P. Taylor Goetz > wrote: > > > Another thing to keep in mind is that non-Apache release

Re: Migrating Heron code to Apache

+1 for that approach, thanks Taylor. On Wed, Nov 8, 2017 at 10:47 AM, P. Taylor Goetz wrote: > Another thing to keep in mind is that non-Apache release artifacts cannot > be hosted on ASF infrastructure. Even so, non-Apache releases can be cut > from an ASF-hosted git

Re: Migrating Heron code to Apache

Another thing to keep in mind is that non-Apache release artifacts cannot be hosted on ASF infrastructure. Even so, non-Apache releases can be cut from an ASF-hosted git repository. Non-Apache releases also need to be clearly labeled as such. In terms of moving from “com.twitter” to

Re: Migrating Heron code to Apache

Sorry for the late reply. +1 to moving to apache git first. +1 on using gitbox so that the github repo is writable. That should simplify a lot of things. When we migrated parquet, we first moved the code to apache git and only later renamed packages to the new org.apache.parquet namespace. For

Re: Migrating Heron code to Apache

I don't believe the location of the code influences the type of release allowed. For example, I believe the Parquet project to did a non-Apache release after migrating. Maybe Julien can confirm that. Or Jake/another can reconfirm/refute my memory. On Sun, Oct 29, 2017 at 9:24 AM, Bill Graham

Re: Migrating Heron code to Apache

As in terms of the order execution. I am not a lawyer, but I think you can still cut releases with packages in com.twitter even after in it is in apache git. In the early days of Apache Storm, all the Java code was under org.backtype, however releases were still cut without a problem. If this

Re: Migrating Heron code to Apache

Hello all, I strongly agree with Bill on migrating the code base to org.apache. This will attract more developers and automatically fix issues involving copyrights and headers that we don't need to waste our time dealing with. Heron, as an open source project, is in a state of limbo. Developers

Re: Migrating Heron code to Apache

Jacques, I was under the impression that once the code was imported to apache, releases had to be apache releases. This would require 1 and a number of other changes. Is that not the case? The motivation for doing 1 first was so we could continue to cut releases as needed during that effort. On

Re: Migrating Heron code to Apache

I'm -0 on plan. Why not just import code then do changes 1 and 2 after 3? Just seems like getting 3 done is a key blocking item on forward progress of the community. On Oct 27, 2017 3:16 PM, "Sanjeev Kulkarni" wrote: > +1 > > On Thu, Oct 26, 2017 at 9:15 AM, Bill Graham

Re: Migrating Heron code to Apache

Looks good to me as well! Best, Andrew Jorgensen @ajorgensen On Thu, Oct 26, 2017 at 12:21 PM, Ashvin A wrote: > LGTM > > +1 > > On Thu, Oct 26, 2017 at 9:15 AM, Bill Graham wrote: > > > Any other comments on this proposal from Heron developers? The

Re: Migrating Heron code to Apache

LGTM +1 On Thu, Oct 26, 2017 at 9:15 AM, Bill Graham wrote: > Any other comments on this proposal from Heron developers? The next podling > report is due on Wednesday so we should address our plan. > > On Sat, Oct 21, 2017 at 3:38 PM, John D. Ament

Re: Migrating Heron code to Apache

Any other comments on this proposal from Heron developers? The next podling report is due on Wednesday so we should address our plan. On Sat, Oct 21, 2017 at 3:38 PM, John D. Ament wrote: > If you do in fact want to use gitbox (which allows you to have github > writable

Re: Migrating Heron code to Apache

If you do in fact want to use gitbox (which allows you to have github writable repos), infra will need to be made an admin on your organization temporarily to do the migration. Many new projects are doing this, so it's not uncommon to just use gitbox since you're already on github. John On

Re: Migrating Heron code to Apache

Thank you both for the info :-) I had not realized it would just be re-homed in a different Github org. Thanks! Brian On Thu, Oct 19, 2017 at 11:58 AM, Bill Graham wrote: > Right, it would still be on github, just at apache/heron instead of > twitter/heron. > > On Thu,

Re: Migrating Heron code to Apache

Apache git can also refer to the Github Apache org as a number of projects are running in that fashion. They key is that the code has been imported over to the Apache Infra owned/managed infrastructure -Jake On Thu, Oct 19, 2017 at 11:04 AM, Brian Hatfield wrote: > Silly

Re: Migrating Heron code to Apache

+1 sounds good. Based on the discussion in LEGAL-339, we will need to get the SGA submitted prior to graduating from the incubator and becoming a top level project, but we can track that progress as a jira story and not block incubator and day to day code development -Jake On Thu, Oct 19, 2017

Migrating Heron code to Apache

Hi, In LEGAL-339 it was concluded that we can in fact move the code to Apache git and cut Apache releases without the SGA. I propose we move forward on that. I suggest the following plan: 1.a Refactor all Heron build dependencies (mainly c++