heron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sanjeev Kulkarni <sanjee...@gmail.com>
Subject Re: Moving to Apache
Date Tue, 27 Feb 2018 23:23:12 GMT
Thanks Jerry for taking the lead on this!
I second the proposal to just transfer the github account to Apache. Could
someone from Twitter follow up internally?


On Tue, Feb 27, 2018 at 3:20 PM, Jerry Peng <jerry.boyang.peng@gmail.com>
wrote:

> Hello all,
>
> I just want to start an email thread discussing moving Heron to
> Apache.  There are some items we need to figure out for this:
>
> 1. Moving the code to Apache github
>
> I was told that an repo can be transferred to another account and
> people have done this in the past to move to the Apache github
> account.  This is the best way to move the code to be under apache
> since with this method heron will keep all its stars and forks.
>
> We need to start converting heron packages from com.twitter -> org.apache.
>
> Ideally this whole process of migrating to Apache will not be a
> blocker for development and releases.
>
> Thus, if mentors or people with experience in this area want to chime
> in on the exact details (step by step) of what needs to be do for
> heron to be completely migrated to Apache that would be great!
>
> 2. Moving website to heron.apache.org
>
> What do we want to do here?  Migrate the whole website to
> heron.apache.org? And Have heron.io forward to heron.apache.org?
>
> 3.  How can we use apache infra
>
> I think committers/mentors need to file some tickets to apache infra for
> this.
>
> How can we use the apache infra to do apache release for heron?
>
> Lets get the discussion going!
>
> Thanks!
>
> Jerry
>

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