Re: Moving to Apache

[Ning Wang]

Sounds good to me. maosong@, do you have any concerns?

On Tue, Feb 27, 2018 at 3:23 PM, Sanjeev Kulkarni 
wrote:

> 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 
> 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
> >
>

Re: Heron Sync Up 02/27/2017

[Ning Wang]

A brief meeting notes for today's sync up meeting:


   -

   Updates
   -

  Huijun has been working on a failure handling (mostly for aurora)
  issue in heron update command (topology state not recovered to
the previous
  state). Also internal webhook integration.
  -

  Runtime config design doc is stable enough in major components (there
  might be notes in details.) and coding is started and one PR in
TMaster is
  ready for review.
  -

  A doc about per-component CPU config as well as other resource
  related config is available. Jerry will have a look.
  
https://docs.google.com/document/d/1mDDW6Lc0PXT8JD29n1zc3hv3G5LPXAoX4KkXu0Ycnds/edit#
  -

  Jerry got an issue that stateful example is not working (throwing
  exception). Maosong/Jerry will take a look
  -

 Note that currently stateful support is low level API and single
 thread only.
 -

   Discussion
   -

  Apache migration. We need a migration plan to discuss and review.
  
https://docs.google.com/document/d/1-G5qbFN1ftDRf42Dee_BjlEZ75C-gVdGJ_uaGIL8qx8/edit?usp=sharing
  Here are a few questions we need to have answers.
  -

 pointing the heron.apache.org - github pages
 -

 how to automatically do daily digest for slack and push into dev
 mailing lists
 -

 can we use the apache infrastructure for it?
 -

 When can we start using apache infrastructure
 -

 How to get access to Apache Maven repo
 -

 Whom we need to contact?
 -

  Other Apache migration thoughts have been talked about in the meeting
  -

 We need to replace all package name, but it is likely to require
 some config changes.  Maybe hold on until we have a plan and thing are
 ready.
 -

 We can move website/document first, but needs to set up SVN. There
 are other tickets and setups works. @karthik
 -

 Git repo. How to keep stars/forks in github?
 -

 Github issues or Apache jira?
 -

  First meetup.
  -

 Will be hosted in Twitter
 -

 User oriented.
 -

Estimate 2 hours,
-

We need have step by step instructions to start topology
locally/aws.


On Tue, Feb 27, 2018 at 6:56 PM, Ning Wang  wrote:

> Got it. Thanks!
>
> On Tue, Feb 27, 2018 at 6:23 PM, Dave Fisher 
> wrote:
>
>> Please post the notes into an email so that we can see what was discussed
>> through Apache hosted resources. This is an important part of the Apache
>> Way.
>>
>> Thanks!
>>
>> Regards,
>> Dave
>>
>> Sent from my iPhone
>>
>> > On Feb 27, 2018, at 4:33 PM, Ning Wang  wrote:
>> >
>> > All -
>> >
>> > We had the sync up meeting today and here is the brief note.
>> >
>> > https://docs.google.com/document/d/1cTIBq3jOVRTSR0Zd5OKK20Oq
>> wT2l90xXiY_HssVo8mE/edit?ts=5a15c620#
>> >
>> > Please feel free to comment or reply if you have any question.
>>
>>
>

Re: Heron Sync Up 02/27/2017

[Ning Wang]

Got it. Thanks!

On Tue, Feb 27, 2018 at 6:23 PM, Dave Fisher  wrote:

> Please post the notes into an email so that we can see what was discussed
> through Apache hosted resources. This is an important part of the Apache
> Way.
>
> Thanks!
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Feb 27, 2018, at 4:33 PM, Ning Wang  wrote:
> >
> > All -
> >
> > We had the sync up meeting today and here is the brief note.
> >
> > https://docs.google.com/document/d/1cTIBq3jOVRTSR0Zd5OKK20OqwT2l9
> 0xXiY_HssVo8mE/edit?ts=5a15c620#
> >
> > Please feel free to comment or reply if you have any question.
>
>

Re: Moving to Apache

[Dave Fisher]

I think it is good to have a document to edit and discuss. A typical way to do 
this can also be a wiki or an issue tracker. Github offers this. The project 
can use this approach either now or after moving to Apache Gitbox. 
Alternatively, Confluence and MoinMoin wikis are available. Bugzilla and JIRA 
issue trackers are also options.

Regards,
Dave

Sent from my iPhone

> On Feb 27, 2018, at 4:37 PM, Ning Wang  wrote:
> 
> I created a google doc for us to track questions and plans:
> 
> https://docs.google.com/document/d/1-G5qbFN1ftDRf42Dee_BjlEZ75C-gVdGJ_uaGIL8qx8/edit#
> 
> 
>> On Tue, Feb 27, 2018 at 4:23 PM, Josh Fischer  wrote:
>> 
>> Dave,
>> 
>> Thank you for the suggestions.  This is fantastic advice.
>> 
>> 
>>> On Tue, Feb 27, 2018 at 6:19 PM Dave Fisher  wrote:
>>> 
>>> Hi -
>>> 
>>> I will answer with two hats - (1) IPMC member and mentor to other
>>> projects, and (2) Brand committee member.
>>> 
>>> On Feb 27, 2018, at 3:20 PM, Jerry Peng 
>>> 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!
>>> 
>>> 
>>> (1) Transfer GitHub. Create an Infrastructure JIRA issue to convert the
>>> twitter repository to apache/incubator-heron/. You will need to have an
>>> admin for twitter give an ASF Infra admin rights to move.
>>> (2) Once moved then your apache-id and your GitHub id are associated
>>> through id.apache.org. You setup 2FA.
>>> (3) Once IDs and the repository are moved then you can begin.
>>> (4) Someone from Twitter in the project should make the changes.
>>> (5) As an Incubator podling you then begin making releases. You aren’t
>>> expected to get it correct the first time, but the closer you are the
>>> sooner you can graduate. The policy [1] and additional constraints for
>>> podlings. [2]
>>> 
>>> 
>>> [1] http://www.apache.org/legal/release-policy.html
>>> [2] https://incubator.apache.org/guides/releasemanagement.html
>>> 
>>> 
>>> 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?
>>> 
>>> 
>>> Yes. And Yes. There are other branding and incubator policies for the
>>> website. [3]
>>> 
>>> [3] https://www.apache.org/foundation/marks/pmcs
>>> 
>>> For those of you using the Heron brand in your site please see [4] for
>> the
>>> policies.
>>> 
>>> [4] https://www.apache.org/foundation/marks/
>>> 
>>> For special branding rules during incubation. [5]
>>> 
>>> [5] https://incubator.apache.org/guides/branding.html
>>> 
>>> 
>>> 3.  How can we use apache infra
>>> 
>>> I think committers/mentors need to file some tickets to apache infra for
>>> this.
>>> 
>>> 
>>> A ticket for Github/GitBox is required.
>>> 
>>> 
>>> How can we use the apache infra to do apache release for heron?
>>> 
>>> 
>>> Follow the rules above and ask questions as you go.
>>> 
>>> Best Regards,
>>> Dave
>>> 
>>> 
>>> Lets get the discussion going!
>>> 
>>> Thanks!
>>> 
>>> Jerry
>>> 
>>> --
>> Sent from A Mobile Device
>> 

Re: Heron Sync Up 02/27/2017

[Dave Fisher]

Please post the notes into an email so that we can see what was discussed 
through Apache hosted resources. This is an important part of the Apache Way.

Thanks!

Regards,
Dave

Sent from my iPhone

> On Feb 27, 2018, at 4:33 PM, Ning Wang  wrote:
> 
> All -
> 
> We had the sync up meeting today and here is the brief note.
> 
> https://docs.google.com/document/d/1cTIBq3jOVRTSR0Zd5OKK20OqwT2l90xXiY_HssVo8mE/edit?ts=5a15c620#
> 
> Please feel free to comment or reply if you have any question.

Re: Moving to Apache

[Bill Graham]

Thanks Jerry for kicking this off. Here are a few other related references.

- The proposed migration plan thread:
https://lists.apache.org/thread.html/a83095cd44e09fa179c4b5034e04acdb055a671406f1501a796700e0@%3Cdev.heron.apache.org%3E

- One of the larger development tasks (along with package renaming)
blocking an apache release is to no longer include binaries in the distro.
This work should be priorirtized and can happen in parallel with other
migration efforts:
https://github.com/twitter/heron/issues/2092

- The github issue for moving the codebase:
https://github.com/twitter/heron/issues/2133

thanks,
Bill

On Tue, Feb 27, 2018 at 5:43 PM, Sree V 
wrote:

> Project website request:https://jira.apache.org/jira/browse/INFRA-16118
>
>
> Thanking you.
> With Regards
> Sree
>
> On Tuesday, February 27, 2018, 5:35:51 PM PST, Sree V <
> sree_at_ch...@yahoo.com.INVALID> wrote:
>
>  Thank you for giving me access to create INFRA tickets.
> > (1) Transfer GitHub. Create an Infrastructure JIRA issue to convert the
> twitter repository to apache/incubator-heron/. You will need to have an
> admin for twitter give an ASF Infra admin rights to move.
>
> This is the most common path, that I worked with.
> external code (eg.google code)  -> apache git -> (periodic sync) ->
> github.com/apache
>
> Now we are asking for github.com/twitter/heron -> (move) ->
> github.com/apache/incubator-heron -> (one time) -> apache git ->
> (periodic sync) -> github.com/apache/incubator-heron.
>
>
> This probably very hard as there are more than Heron project under
> github.com/twitter/. We would not know, until we attempt.  Twitter
> employees for rescue.
> In detail:We need INFRA create, https://git-wip-us.apache.org/
> repos/asf/incubator-heron.githttps://jira.apache.org/
> jira/browse/INFRA-16116
>
> We need INFRA create, https://github.com/apache/incubator-heron
> https://jira.apache.org/jira/browse/INFRA-16117
> Here in the comments, I mentioned to move from github.com/twitter/heron
> to github.com/apache/incubator-heron, retaining everything without any
> exceptions.
>
>
> In addition, request to create JIRA project for HERON.
> https://jira.apache.org/jira/browse/INFRA-16115
> Karthik/PMC: you may add more admins for jira heron and add more
> developers as well.
>
>
>
>
> Thanking you.
> With Regards
> Sree
>
> On Tuesday, February 27, 2018, 4:44:38 PM PST, Ning Wang <
> wangnin...@gmail.com> wrote:
>
>   I created a google doc for us to track questions and plans:
>
> https://docs.google.com/document/d/1-G5qbFN1ftDRf42Dee_BjlEZ75C-
> gVdGJ_uaGIL8qx8/edit#
>
>
> On Tue, Feb 27, 2018 at 4:23 PM, Josh Fischer  wrote:
>
> > Dave,
> >
> > Thank you for the suggestions.  This is fantastic advice.
> >
> >
> > On Tue, Feb 27, 2018 at 6:19 PM Dave Fisher  wrote:
> >
> > > Hi -
> > >
> > > I will answer with two hats - (1) IPMC member and mentor to other
> > > projects, and (2) Brand committee member.
> > >
> > > On Feb 27, 2018, at 3:20 PM, Jerry Peng 
> > > 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!
> > >
> > >
> > > (1) Transfer GitHub. Create an Infrastructure JIRA issue to convert the
> > > twitter repository to apache/incubator-heron/. You will need to have an
> > > admin for twitter give an ASF Infra admin rights to move.
> > > (2) Once moved then your apache-id and your GitHub id are associated
> > > through id.apache.org. You setup 2FA.
> > > (3) Once IDs and the repository are moved then you can begin.
> > > (4) Someone from Twitter in the project should make the changes.
> > > (5) As an Incubator podling you then begin making releases. You aren’t
> > > expected to get it correct the first time, but the closer you are the
> > > sooner you can graduate. The policy [1] and additional constraints for
> > > podlings. [2]
> > >
> > >
> > > [1] http://www.apache.org/legal/release-policy.html
> > > [2] https://incubator.apache.org/guides/releasemanagement.html
> > >
> > >
> > > 2. Moving website to heron.apache.org
> > >
> > > What do we want 

Re: Moving to Apache

[Sree V]

Project website request:https://jira.apache.org/jira/browse/INFRA-16118


Thanking you.
With Regards
Sree 

On Tuesday, February 27, 2018, 5:35:51 PM PST, Sree V 
 wrote:  
 
 Thank you for giving me access to create INFRA tickets.
> (1) Transfer GitHub. Create an Infrastructure JIRA issue to convert the 
> twitter repository to apache/incubator-heron/. You will need to have an admin 
> for twitter give an ASF Infra admin rights to move.

This is the most common path, that I worked with.
external code (eg.google code)  -> apache git -> (periodic sync) -> 
github.com/apache

Now we are asking for github.com/twitter/heron -> (move) -> 
github.com/apache/incubator-heron -> (one time) -> apache git -> (periodic 
sync) -> github.com/apache/incubator-heron.


This probably very hard as there are more than Heron project under 
github.com/twitter/. We would not know, until we attempt.  Twitter employees 
for rescue.
In detail:We need INFRA create, 
https://git-wip-us.apache.org/repos/asf/incubator-heron.githttps://jira.apache.org/jira/browse/INFRA-16116

We need INFRA create, https://github.com/apache/incubator-heron
https://jira.apache.org/jira/browse/INFRA-16117
Here in the comments, I mentioned to move from github.com/twitter/heron to 
github.com/apache/incubator-heron, retaining everything without any exceptions.


In addition, request to create JIRA project for 
HERON.https://jira.apache.org/jira/browse/INFRA-16115
Karthik/PMC: you may add more admins for jira heron and add more developers as 
well.




Thanking you.
With Regards
Sree 

    On Tuesday, February 27, 2018, 4:44:38 PM PST, Ning Wang 
 wrote:  
 
  I created a google doc for us to track questions and plans:

https://docs.google.com/document/d/1-G5qbFN1ftDRf42Dee_BjlEZ75C-gVdGJ_uaGIL8qx8/edit#


On Tue, Feb 27, 2018 at 4:23 PM, Josh Fischer  wrote:

> Dave,
>
> Thank you for the suggestions.  This is fantastic advice.
>
>
> On Tue, Feb 27, 2018 at 6:19 PM Dave Fisher  wrote:
>
> > Hi -
> >
> > I will answer with two hats - (1) IPMC member and mentor to other
> > projects, and (2) Brand committee member.
> >
> > On Feb 27, 2018, at 3:20 PM, Jerry Peng 
> > 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!
> >
> >
> > (1) Transfer GitHub. Create an Infrastructure JIRA issue to convert the
> > twitter repository to apache/incubator-heron/. You will need to have an
> > admin for twitter give an ASF Infra admin rights to move.
> > (2) Once moved then your apache-id and your GitHub id are associated
> > through id.apache.org. You setup 2FA.
> > (3) Once IDs and the repository are moved then you can begin.
> > (4) Someone from Twitter in the project should make the changes.
> > (5) As an Incubator podling you then begin making releases. You aren’t
> > expected to get it correct the first time, but the closer you are the
> > sooner you can graduate. The policy [1] and additional constraints for
> > podlings. [2]
> >
> >
> > [1] http://www.apache.org/legal/release-policy.html
> > [2] https://incubator.apache.org/guides/releasemanagement.html
> >
> >
> > 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?
> >
> >
> > Yes. And Yes. There are other branding and incubator policies for the
> > website. [3]
> >
> > [3] https://www.apache.org/foundation/marks/pmcs
> >
> > For those of you using the Heron brand in your site please see [4] for
> the
> > policies.
> >
> > [4] https://www.apache.org/foundation/marks/
> >
> > For special branding rules during incubation. [5]
> >
> > [5] https://incubator.apache.org/guides/branding.html
> >
> >
> > 3.  How can we use apache infra
> >
> > I think committers/mentors need to file some tickets to apache infra for
> > this.
> >
> >
> > A ticket for Github/GitBox is required.
> >
> >
> > How can we use the apache infra to do apache release for heron?
> >
> >
> > Follow the rules above and ask questions as you go.
> >
> > Best Regards,
> > Dave
> 

Re: Heron Sync Up 02/27/2017

[Sree V]

Thank you, Ning.



Thanking you.
With Regards
Sree 

On Tuesday, February 27, 2018, 4:33:48 PM PST, Ning Wang 
 wrote:  
 
 All -

We had the sync up meeting today and here is the brief note.

https://docs.google.com/document/d/1cTIBq3jOVRTSR0Zd5OKK20OqwT2l90xXiY_HssVo8mE/edit?ts=5a15c620#

Please feel free to comment or reply if you have any question.
  

Re: Moving to Apache

[Sree V]

Thank you for giving me access to create INFRA tickets.
> (1) Transfer GitHub. Create an Infrastructure JIRA issue to convert the 
> twitter repository to apache/incubator-heron/. You will need to have an admin 
> for twitter give an ASF Infra admin rights to move.

This is the most common path, that I worked with.
external code (eg.google code)  -> apache git -> (periodic sync) -> 
github.com/apache

Now we are asking for github.com/twitter/heron -> (move) -> 
github.com/apache/incubator-heron -> (one time) -> apache git -> (periodic 
sync) -> github.com/apache/incubator-heron.


This probably very hard as there are more than Heron project under 
github.com/twitter/. We would not know, until we attempt.  Twitter employees 
for rescue.
In detail:We need INFRA create, 
https://git-wip-us.apache.org/repos/asf/incubator-heron.githttps://jira.apache.org/jira/browse/INFRA-16116

We need INFRA create, https://github.com/apache/incubator-heron
https://jira.apache.org/jira/browse/INFRA-16117
Here in the comments, I mentioned to move from github.com/twitter/heron to 
github.com/apache/incubator-heron, retaining everything without any exceptions.


In addition, request to create JIRA project for 
HERON.https://jira.apache.org/jira/browse/INFRA-16115
Karthik/PMC: you may add more admins for jira heron and add more developers as 
well.




Thanking you.
With Regards
Sree 

On Tuesday, February 27, 2018, 4:44:38 PM PST, Ning Wang 
 wrote:  
 
  I created a google doc for us to track questions and plans:

https://docs.google.com/document/d/1-G5qbFN1ftDRf42Dee_BjlEZ75C-gVdGJ_uaGIL8qx8/edit#


On Tue, Feb 27, 2018 at 4:23 PM, Josh Fischer  wrote:

> Dave,
>
> Thank you for the suggestions.  This is fantastic advice.
>
>
> On Tue, Feb 27, 2018 at 6:19 PM Dave Fisher  wrote:
>
> > Hi -
> >
> > I will answer with two hats - (1) IPMC member and mentor to other
> > projects, and (2) Brand committee member.
> >
> > On Feb 27, 2018, at 3:20 PM, Jerry Peng 
> > 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!
> >
> >
> > (1) Transfer GitHub. Create an Infrastructure JIRA issue to convert the
> > twitter repository to apache/incubator-heron/. You will need to have an
> > admin for twitter give an ASF Infra admin rights to move.
> > (2) Once moved then your apache-id and your GitHub id are associated
> > through id.apache.org. You setup 2FA.
> > (3) Once IDs and the repository are moved then you can begin.
> > (4) Someone from Twitter in the project should make the changes.
> > (5) As an Incubator podling you then begin making releases. You aren’t
> > expected to get it correct the first time, but the closer you are the
> > sooner you can graduate. The policy [1] and additional constraints for
> > podlings. [2]
> >
> >
> > [1] http://www.apache.org/legal/release-policy.html
> > [2] https://incubator.apache.org/guides/releasemanagement.html
> >
> >
> > 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?
> >
> >
> > Yes. And Yes. There are other branding and incubator policies for the
> > website. [3]
> >
> > [3] https://www.apache.org/foundation/marks/pmcs
> >
> > For those of you using the Heron brand in your site please see [4] for
> the
> > policies.
> >
> > [4] https://www.apache.org/foundation/marks/
> >
> > For special branding rules during incubation. [5]
> >
> > [5] https://incubator.apache.org/guides/branding.html
> >
> >
> > 3.  How can we use apache infra
> >
> > I think committers/mentors need to file some tickets to apache infra for
> > this.
> >
> >
> > A ticket for Github/GitBox is required.
> >
> >
> > How can we use the apache infra to do apache release for heron?
> >
> >
> > Follow the rules above and ask questions as you go.
> >
> > Best Regards,
> > Dave
> >
> >
> > Lets get the discussion going!
> >
> > Thanks!
> >
> > Jerry
> >
> > --
> Sent from A Mobile Device
>  

Re: Moving to Apache

[Ning Wang]

 I created a google doc for us to track questions and plans:

https://docs.google.com/document/d/1-G5qbFN1ftDRf42Dee_BjlEZ75C-gVdGJ_uaGIL8qx8/edit#


On Tue, Feb 27, 2018 at 4:23 PM, Josh Fischer  wrote:

> Dave,
>
> Thank you for the suggestions.  This is fantastic advice.
>
>
> On Tue, Feb 27, 2018 at 6:19 PM Dave Fisher  wrote:
>
> > Hi -
> >
> > I will answer with two hats - (1) IPMC member and mentor to other
> > projects, and (2) Brand committee member.
> >
> > On Feb 27, 2018, at 3:20 PM, Jerry Peng 
> > 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!
> >
> >
> > (1) Transfer GitHub. Create an Infrastructure JIRA issue to convert the
> > twitter repository to apache/incubator-heron/. You will need to have an
> > admin for twitter give an ASF Infra admin rights to move.
> > (2) Once moved then your apache-id and your GitHub id are associated
> > through id.apache.org. You setup 2FA.
> > (3) Once IDs and the repository are moved then you can begin.
> > (4) Someone from Twitter in the project should make the changes.
> > (5) As an Incubator podling you then begin making releases. You aren’t
> > expected to get it correct the first time, but the closer you are the
> > sooner you can graduate. The policy [1] and additional constraints for
> > podlings. [2]
> >
> >
> > [1] http://www.apache.org/legal/release-policy.html
> > [2] https://incubator.apache.org/guides/releasemanagement.html
> >
> >
> > 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?
> >
> >
> > Yes. And Yes. There are other branding and incubator policies for the
> > website. [3]
> >
> > [3] https://www.apache.org/foundation/marks/pmcs
> >
> > For those of you using the Heron brand in your site please see [4] for
> the
> > policies.
> >
> > [4] https://www.apache.org/foundation/marks/
> >
> > For special branding rules during incubation. [5]
> >
> > [5] https://incubator.apache.org/guides/branding.html
> >
> >
> > 3.  How can we use apache infra
> >
> > I think committers/mentors need to file some tickets to apache infra for
> > this.
> >
> >
> > A ticket for Github/GitBox is required.
> >
> >
> > How can we use the apache infra to do apache release for heron?
> >
> >
> > Follow the rules above and ask questions as you go.
> >
> > Best Regards,
> > Dave
> >
> >
> > Lets get the discussion going!
> >
> > Thanks!
> >
> > Jerry
> >
> > --
> Sent from A Mobile Device
>

Heron Sync Up 02/27/2017

[Ning Wang]

All -

We had the sync up meeting today and here is the brief note.

https://docs.google.com/document/d/1cTIBq3jOVRTSR0Zd5OKK20OqwT2l90xXiY_HssVo8mE/edit?ts=5a15c620#

Please feel free to comment or reply if you have any question.

Re: Moving to Apache

[Dave Fisher]

Hi -

I will answer with two hats - (1) IPMC member and mentor to other projects, and 
(2) Brand committee member.

> On Feb 27, 2018, at 3:20 PM, Jerry Peng  > 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!

(1) Transfer GitHub. Create an Infrastructure JIRA issue to convert the twitter 
repository to apache/incubator-heron/. You will need to have an admin for 
twitter give an ASF Infra admin rights to move.
(2) Once moved then your apache-id and your GitHub id are associated through 
id.apache.org . You setup 2FA.
(3) Once IDs and the repository are moved then you can begin.
(4) Someone from Twitter in the project should make the changes.
(5) As an Incubator podling you then begin making releases. You aren’t expected 
to get it correct the first time, but the closer you are the sooner you can 
graduate. The policy [1] and additional constraints for podlings. [2]


[1] http://www.apache.org/legal/release-policy.html 

[2] https://incubator.apache.org/guides/releasemanagement.html 


> 
> 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 ?

Yes. And Yes. There are other branding and incubator policies for the website. 
[3]

[3] https://www.apache.org/foundation/marks/pmcs 


For those of you using the Heron brand in your site please see [4] for the 
policies.

[4] https://www.apache.org/foundation/marks/ 


For special branding rules during incubation. [5]

[5] https://incubator.apache.org/guides/branding.html 



> 3.  How can we use apache infra
> 
> I think committers/mentors need to file some tickets to apache infra for this.

A ticket for Github/GitBox is required.

> 
> How can we use the apache infra to do apache release for heron?

Follow the rules above and ask questions as you go.

Best Regards,
Dave

> 
> Lets get the discussion going!
> 
> Thanks!
> 
> Jerry



signature.asc
Description: Message signed with OpenPGP

Re: Moving to Apache

[Sanjeev Kulkarni]

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 
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
>

Moving to Apache

[Jerry Peng]

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

Release 0.17.6 tagged

[Karthik Ramasamy]

All -

Heron release 0.17.6 is tagged as a pre-release and we are working on
publishing the binaries.

cheers
/karthik

OSS sync up today

[Jerry Peng]

Hello all,

Just a reminder this is the hangout link to the heron OSS sync up today:

https://plus.google.com/hangouts/_/streaml.io/oss-heron-sync?hceid=a2FydGhpa0BzdHJlYW1sLmlv.218m8hgr4ekqsf1o8of2olo1a0=0

Somethings on agenda for discussion today:

- pointing the heron.apache.org - github pages
- how to automatically do daily digest for slack and push into dev mailing lists
- can we use the apache infrastructure for it?

Best,

Jerry

Re: Release Today/Tomorrow

[Ning Wang]

sgtm

On Tue, Feb 27, 2018 at 2:27 AM, Karthik Ramasamy 
wrote:

> Ok let us do a release. Any objections to do a release?
>
> Sent from my iPhone
>
> > On Feb 27, 2018, at 1:57 AM, Chris Kellogg  wrote:
> >
> > It's a little more involved then i thought. We could do a release and
> then
> > follow up with another one soon.
> >
> > On Mon, Feb 26, 2018 at 8:50 PM, Karthik Ramasamy 
> > wrote:
> >
> >> We can do a release. Chris wanted to get a PR in. Chris - any update?
> >>
> >> On Mon, Feb 26, 2018 at 11:38 PM Jerry Peng <
> jerry.boyang.p...@gmail.com>
> >> wrote:
> >>
> >>> We haven't done a release in a while.  Should we do a release today or
> >>> tomorrow?
> >>>
> >>> Best,
> >>>
> >>> Jerry
> >>>
> >>
>