I would be a strong +1 for using GitHub for all new top-level issues. We already have a title formatting requirement on JIRAs (e.g., [R] Some issue description) and so I don't see any reason why labels could not be added in retrospect even if they don't exist yet.
On Thu, Nov 24, 2022 at 7:30 AM Joris Van den Bossche < jorisvandenboss...@gmail.com> wrote: > On Thu, 24 Nov 2022 at 11:31, Antoine Pitrou <anto...@python.org> wrote: > > > > > > Are all the required labels ready? I don't seem to see the components > > in https://github.com/apache/arrow/labels. Also, we should curate the > > existing labels and namespace all the remaining ones so that the > > categories can be easily understood. > > I think we do have a label already for many of the components. The > naming is just a bit differently (eg "lang-c++" vs "component: C++"). > And we should indeed clean up this and decide on a consistent taxonomy > for our labels, but I think we can also do that while using github > issues (which we essentially already are doing, since new reporters > have started using github anyway). It is easy to rename labels through > the github interface. > > From a quick look, the ones that seem to be missing are: Archery, > Benchmarking, Continuous Integration, Developer Tools, Format, > Integration, Packaging, Website, Other. We can easily add them if that > unblocks a vote and allow us to get started using github. > > > > > Besides, it seems the component lists in the issue templates haven't > > been cleaned up yet, I still see entries like "Compute IR", "SQL" or > > the various "Rust" entries that shouldn't be there. > > That was already being fixed by > https://github.com/apache/arrow/pull/14688 (which I just merged). > > > > > Based on this I'd make it a -1 for now, but it can be revisited very > > soon if those tasks are done :-) > > > > > > > > On Wed, 23 Nov 2022 14:37:01 -0700 > > Todd Farmer <t...@voltrondata.com.INVALID> wrote: > > > Hello, > > > > > > I would like to propose that issue reporting in ASF Jira for the Apache > > > Arrow project be disabled, and all users directed to use GitHub issues > for > > > reporting going forward. GitHub issue reporting is now enabled [1] in > > > response to a recent Infra policy change eliminating self-service user > > > registration for ASF Jira accounts. The Apache Arrow project has > already > > > voted in support of migrating issue tracking from ASF Jira to GitHub > issues > > > [2], and migration work is ongoing [3]. > > > > > > Disabling ASF Jira issue reporting will move all such work to GitHub > > > issues. I expect that usage of this new platform by all participants - > not > > > just new community members lacking ASF Jira accounts - will expedite > > > further discovery and improvements to this platform. Furthermore, this > will > > > prevent new users from being routed to a new, and potentially "lesser", > > > issue reporting experience. > > > > > > Please note that this proposal does NOT move work on existing ASF Jira > > > issues to GitHub - that work should continue in Jira until issues are > > > migrated and the Jira system set to read-only. There will be a separate > > > discussion when that activity is ready. > > > > > > The vote will be open for at least 72 hours. > > > > > > [ ] +1 Disable issue reporting on ASF Jira for the Apache Arrow project > > > [ ] -1 Leave issue reporting enabled on ASF Jira for the Apache Arrow > > > project because... > > > > > > [1] https://github.com/apache/arrow/issues/new/choose > > > [2] https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > > [3] > > > > https://docs.google.com/document/d/1UaSJs-oyuq8QvlUPoQ9GeiwP19LK5ZzF_5-HLfHDCIg/edit?usp=sharing > > > > > > Todd Farmer > > > > > > > > > >
