+1 from me as well. I actually proposed this a few years ago and voted down :)
I think we can build some integration tooling around GH issues. To me being able to cross reference against other projects will be invaluable, Since most of those are already on github. Love to see if there are more contrary opinions On Mon, Aug 18, 2025 at 11:14 Hari Mani <hariatul1...@gmail.com> wrote: > Hi, > > I think this is really a welcome move especially because of the lowering > the barrier for new contributors aspect. One thing to keep in mind though > is that the automation support in GitHub issues is not as extensive as > Jira's. The first hand experience of other projects who have made the move > will be valueable in foreseeing limitations in this aspect. But overall I > think the move will really help bring in more new contributors. > > Regards, > *Hari Mani* > > On Mon, Aug 18, 2025, 11:14 PM Bhavani Sudha <bhavanisu...@apache.org> > wrote: > > > Hey folks, > > > > I wanted to start a quick conversation about our issue tracking. Right > now, > > we’re using JIRA, but many ASF projects have been moving over to GitHub > > Issues. The main reasons are pretty compelling: > > > > - > > > > It’s easier for contributors who are already working on GitHub. > > - > > > > Issues, PRs, and code all live in one place. > > - > > > > It lowers the barrier for new contributors to get involved. > > > > If we decide to do this, we’ll need to figure out how to handle existing > > JIRA tickets and make sure we don’t lose any important history. ASF Infra > > has some guidance and tools to help with the transition, so we wouldn’t > be > > on our own. > > > > What do you all think — does moving to GitHub Issues make sense for Hudi? > > Any concerns or things we should be careful about? Feel free to suggest > any > > feedback. > > > > > > Thanks, > > > > Sudha > > >
