+1, the bar for using JIRA is too high—contributors need a PMC/committer to create an account. Using GitHub issues would make it much easier for people to participate. DB Tsai | https://www.dbtsai.com/ | PGP 42E5B25A8F7A82C1
> On Jan 26, 2026, at 2:30 PM, Hyukjin Kwon <[email protected]> wrote: > > TBH, if we can manage to migrate all related repos in Apache Spark, I feel > like it might be a great idea. > lately I started to actively work on Apache Arrow, and realised that they > also successfully migrate to GitHub Issues from JIRA for all ther repos. > > On Tue, 27 Jan 2026 at 05:49, Tian Gao via dev <[email protected] > <mailto:[email protected]>> wrote: >> Hi all, I'd like to start a discussion on a draft SPIP: >> https://docs.google.com/document/d/1WMaA49hKyu7gtU189fPq4k8TeI-Q73Q6bqSeWAgR3y8/edit?usp=sharing >> >> tl; dr >> >> I think we should move from JIRA to github issues for >> * more feedback from community >> * lower barrier to entry for new contributors >> * better integration with the whole github eco-system >> >> Many apache projects have moved from JIRA to github issues successfully, >> including Arrow, Airflow, Beam, Maven, Lucene ... Actually most of apache >> projects are using github issues now, with a few exceptions including spark. >> >> I'd like to hear more about this proposal from the community. >> >> Thanks! >> >> Tian Gao
signature.asc
Description: Message signed with OpenPGP
