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