On Thu, Mar 14, 2019 at 11:14 AM Coty Sutherland <csuth...@apache.org> wrote:
> On Thu, Mar 14, 2019 at 8:39 AM Mark Thomas <ma...@apache.org> wrote: > >> It is early days but my impression is that the move to git has triggered >> an increase in conversations that end up split between a GitHub PR and >> Bugzilla. >> >> Personally, I'm not finding it unmanageable at this point but it does >> feel a little disorganized. >> > > +1, I was just thinking about this earlier while trying to follow some > conversations. > > >> >> I'm wondering if we need clearer guidelines about what to discuss where >> or do we need something else? What about a bigger change such as moving >> issue tracking to GitHub? Would that be beneficial? >> > > I agree that we should probably outline the best way to carry on > conversations now that we have the possibility of dev/user list, BZ, and > PRs; I'm not sure what exactly that would look like though. Is there a way > to push links from PR comments into BZ (that's how GitHub does it with PRs > and issues IIRC) to retain the conversation flow? Moving to GitHub's issue > tracker is an interesting solution. I think that the issue tracker is > robust enough that we wouldn't have any issues moving over, but is that OK > in the eyes of the ASF Infra team? How would we be archiving those > conversations (assuming that we need to)? > Apache CloudStack instructs people to use Jira (which mostly has GSoC issues), but also has several issues reported on the GitHub issue tracker; there doesn't seem to be any integration between the two. They use a nice template for issues on GitHub too. > > >> >> What do others think? >> >> Mark >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: dev-h...@tomcat.apache.org >> >>
