I'm also +1 on Jira. On Sat, Feb 23, 2019 at 10:58 PM Christofer Dutz <[email protected]> wrote:
> And all of these projects adopting github issues and. PRs usually end up > flooding every mailbox with thousands of useless emails and makes it > impossible to sensibly file the project. > > I would also favor jira. > > Chris > > Outlook für Android<https://aka.ms/ghei36> herunterladen > > ________________________________ > From: Furkan KAMACI <[email protected]> > Sent: Saturday, February 23, 2019 9:17:45 PM > To: [email protected] > Subject: Re: Jira // Bug tracker > > Hi, > > > Out of curiosity: Can you point at one or two? I assume it's mostly the > > newer ones. > > Yes, mostly new podlings uses Github for such purpose as like Justin > pointed i.e. https://github.com/apache/incubator-druid/issues > > My vote is for Jira too. It is more flexible and powerful i.e. if we want > to decide to use Confluence and integrate it with Jira. > > Kind Regards, > Furkan KAMACI > > On Sat, Feb 23, 2019 at 9:50 PM Sharan Foga <[email protected]> wrote: > > > Hi > > > > I'd prefer Jira too especially if it's going to be easier for anyone to > > contribute. > > > > Thanks > > Sharan > > > > On 2019/02/23 04:21:44, Kenneth Knowles <[email protected]> wrote: > > > > > One thing I've encountered on GitHub is that you can only assign a > PR > > > > > review to a member of the `apache` organization. Is that also true > > for > > > > > issues? > > > > > > > > Most likely but I don’t know. Because of GitHib's poor granularity of > > it's > > > > permission system INFRA have locked it down and a lot of things > > projects > > > > can do in the wild can’t be done at Apache. > > > > > > > > > > If this is true, I prefer Jira so non-committers can take issues. What > do > > > you do on echarts? Do you know what they do on royale-asjs? > > > > > > Kenn > > > > > >
