Apache does have a requirement that community discussions and especially votes are stored on apache servers. This is often done by linking different systems together (like pull requests to JIRA) or by having a fire-hose of changes from the external system sent to some apache mailing list that it can archive. I have not used github issues much but from what I have done it does not look even close to being as full featured as JIRA. So my vote would be to ask people to use JIRA, but not ignore the github issues.
- Bobby On Friday, May 26, 2017, 9:57:43 AM CDT, Sijie Guo <guosi...@gmail.com> wrote:Hi all, Currently we are using Jira for issue tracking and using Github for managing pull requests. For a new developer, he has to create two accounts in order to engage with BookKeeper community. I am thinking - shall we also move the issue tracking to use Github Issues (which I believe Apache Infra supports that now)? So most of the development activities will happen in Github. Another reason I asked this - I saw a Github issue was created. https://github.com/apache/bookkeeper/issues/165 I believe we somehow requested to change the permissions to allow creating Github issues before. Any thoughts? - Sijie
