+1 Github issues And it should be capable to export github issues to JIRA whenever it is a requirement. For instance, https://gist.github.com/henare/1106008
On Wed, Mar 7, 2018 at 7:00 PM, jun liu <[email protected]> wrote: > +1, prefer github issue. > > Since people already familar with github issues, i can’t figure out the > advances of moving to JIRA. > I know JIRA is a more powerful tool for project management, but do we > really need that when github meets most of our requirements? I’m not sure. > > > > > On 7 Mar 2018, at 4:27 PM, Adrian Cole <[email protected]> wrote: > > > > non-binding opinion from an integrator: > > > > dubbo is an RPC layer, so it has a lot of integrators on top. It has a > > history in github as well, and people are used to doing issues. I > > would suggest maintaining github issues as ecosystem-related change > > that is in github is far easier to track this way. For example, I've > > made many issues in different dubbo repositories, and cross linked to > > zipkin seamlessly. I like that it is easy. > >
