Thanks waterlx for comments and raised questions - that's next discussion I would like to call. Hadoop use a different way - most of discussions are happening on JIRA instead of github, but it really depends on how the tubemq community think.
Thanks, Junping 李响 <wate...@gmail.com> 于2019年12月26日周四 上午10:45写道： > +1 for JIRA to track issue. > Another topic is how to review and comment code ? HBase currently prefers > using JIRA to track issue, putting a link to github on JIRA and reviewing > on github. (Please correct me if I am wrong about that) In that way, it > seems lead to that we have almost nothing but only a link and the original > description on JIRA, while storing the most useful parts (review and > discussion history) on github. > > On Thu, Dec 26, 2019 at 10:14 AM Yiheng Wang <yihe...@gmail.com> wrote: > > > +1 for JIRA. > > > > Github Issue is not as powerful as JIRA. > > > > On Thu, Dec 26, 2019 at 9:53 AM Kayne Wu <wuzhongbom...@gmail.com> > wrote: > > > > > +1 for JIRA > > > JIRA a more open place, with more developers participating in > > development > > > and discussions, > > > which helps tubemq to develop and growing faster. > > > > > > > > > > > > Goson zhang <gosonzh...@gmail.com> 于2019年12月26日周四 上午9:38写道： > > > > > > > +1 for JIRA. > > > > > > > > tison <wander4...@gmail.com> 于2019年12月25日周三 上午11:19写道： > > > > > > > > > +1 for JIRA. > > > > > > > > > > JIRA provides rich functions for tagging & releasing which, in > > GitHub, > > > > > should > > > > > take more efforts to setup and maintain. Also I second that JIRA is > > > > hosted > > > > > by Apache makes it more reliable for TubeMQ an Apache project. > > > > > > > > > > As a reminder, if we choose to use JIRA, make sure we close GitHub > > > issue > > > > > entry so that newcomer doesn't get confused. > > > > > > > > > > Best, > > > > > tison. > > > > > > > > > > > > > > > 俊平堵 <junping...@apache.org> 于2019年12月25日周三 上午11:13写道： > > > > > > > > > > > Hi, > > > > > > Continue with TubeMQ's wechat group discussion, shall we use > > JIRA > > > > or > > > > > > Github issue to track issues for TubeMQ? > > > > > > My recommendation is to use JIRA, for following reasons: > > > > > > 1. Most of existing Apache projects use JIRA to track issues > which > > is > > > > > more > > > > > > friendly to project management with lots of functions. > > > > > > 2. Github (and issue) is not own by Apache, so it could be more > > risky > > > > to > > > > > > lost history or access especially during repository migration, > etc. > > > > > > 3. Existing workflow of many projects are JIRA based, and many of > > > > tubemq > > > > > > contributors/committers are from them, such as hadoop, flink, > > spark, > > > > > hbase, > > > > > > etc. It could be more friendly to early contributor. > > > > > > Thoughts? > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Junping > > > > > > > > > > > > > > > > > > > > > > > -- > > 李响 Xiang Li > > 手机 cellphone ：+86-136-8113-8972 > 邮件 e-mail ：wate...@gmail.com >
