Hi all, ASF Infra has announced [1] that, due to spam account creation, it will no longer be possible for people to sign themselves up for a Jira account to report issues as of November 6. Instead, the PMC will have to request the creation of Jira accounts.
Their email says: > Infra knows this process change places an increasing burden on PMC members > for managing contributors, and makes it harder for people to contribute bug reports. > We suggest projects consider using GitHub Issues for customer-facing questions/bug > reports/etc., while maintaining development issues on Jira. but I think that having a two-tiered system for issue tracking presents some notable downsides for us, including: * Increased barriers to entry for new contributors and a sense of inequality between "us" and "them". There's already too much friction IMO, and this pushes that up significantly. * Maintenance burden of triaging and synchronizing issues across trackers sounds like a lot for us to take on. I'd prefer the active maintainers on the project spend their time shipping useful, reliable software, not doing bookkeeping. So as much as I genuinely *hate* bringing this topic up, I wanted to see what folks think about moving our issue tracking fully to GitHub Issues. I know this has been discussed before and shot down, but the circumstances are different now so I think it merits revisiting. It would also be great to hear from the Rust folks how their experience has been using GitHub Issues on arrow-rs and datafusion. Neal [1]: https://lists.apache.org/thread/jx9d7sp690ro660pjpttwtg209w3m39w (not sure if everyone has access to the annou...@infra.apache.org list)
