Re: Moving to Apache

+1 On Wed, Feb 28, 2018 at 7:48 AM, Chris Kellogg wrote: > +1 for Karthik's suggestion too. > > > On Wed, Feb 28, 2018 at 6:04 AM, Josh Fischer wrote: > > > +1 to Karthiks suggestion > > > > On Wed, Feb 28, 2018 at 2:15 AM Karthik Ramasamy

Re: Moving to Apache

I apologize team. I am with Karthik. Continue to use github issues, not jira. I created the infra ticket in flow. I do not have permissions to delete or close it. Sent from Yahoo Mail on Android On Wed, Feb 28, 2018 at 7:48, Chris Kellogg wrote: +1 for Karthik's

Re: Moving to Apache

+1 for Karthik's suggestion too. On Wed, Feb 28, 2018 at 6:04 AM, Josh Fischer wrote: > +1 to Karthiks suggestion > > On Wed, Feb 28, 2018 at 2:15 AM Karthik Ramasamy > wrote: > > > Sree - > > > > Since Apache allows for using github.com (Apache Pulsar

Re: Moving to Apache

+1 to Karthiks suggestion On Wed, Feb 28, 2018 at 2:15 AM Karthik Ramasamy wrote: > Sree - > > Since Apache allows for using github.com (Apache Pulsar uses it) and the > team is used to github.com and its workflow using ISSUES and PR, I would > vote to > >

Re: Moving to Apache

Sree - Since Apache allows for using github.com (Apache Pulsar uses it) and the team is used to github.com and its workflow using ISSUES and PR, I would vote to github.com/twitter/heron > github.com/apache/incubator-heron This is not hard since the organization owner can transfer (in this

Re: Moving to Apache

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

Re: Moving to Apache

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

Re: Moving to Apache

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

Re: Moving to Apache

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

Re: Moving to Apache

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,

Re: Moving to Apache

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

Re: Moving to Apache

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

Re: Moving to Apache

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