Todd said: >User identifiers differ between systems... To help with this, I created a couple of small scripts [1] that extract details from resolved Arrow Jira issues and the associated merged GitHub PRs, then perform some cleaning, to generate a list [2] of matching Jira user identifiers and GitHub user identifiers.
This is an incomplete list: it does not include users who have created Arrow Jira issues but never created an Arrow PR that was merged. Please do some sanity-checking on this list before using it. [1] https://gist.github.com/ianmcook/0f1538ebc8268a88cd4e0a0a61445287 [2] https://docs.google.com/spreadsheets/d/1C8Pxmad93TJjIeN1lX9wkw1KORKocNSLYtUUPlxHmG0/ Ian On Wed, Oct 26, 2022 at 8:12 AM Neal Richardson <neal.p.richard...@gmail.com> wrote: > > Thanks Todd! That's really helpful. > > Neal > > On Tue, Oct 25, 2022 at 7:47 PM Todd Farmer <t...@voltrondata.com.invalid> > wrote: > > > I'm beginning to track decisions needing to be made and problems needing to > > be solved in the Arrow project GitHub issues, prefixing all such issues > > with "MIGRATION: ..". They can be found here: > > > > https://github.com/apache/arrow/issues?q=is%3Aissue+is%3Aopen+MIGRATION > > > > I feel this will be a better forum to talk through specific challenges or > > decisions if a future vote supports migration to GitHub issues. Please > > feel free to comment or to create an issue to track a decision/concern > > that's not already defined. > > > > On Tue, Oct 25, 2022 at 6:37 AM Neal Richardson < > > neal.p.richard...@gmail.com> > > wrote: > > > > > I'll start a vote on this in the next day or so since it seems like we > > have > > > consensus on the main issue (moving from Jira to GitHub Issues) and are > > > working out the finer points on how we'll migrate and how we'll map Jira > > > concepts to Issues. > > > > > > Speaking of the migration: now would be an *excellent* time for folks to > > go > > > through the Jira backlog and close out some old, stale, invalid issues so > > > that we don't have to import a bunch of stuff we don't need. > > > > > > Neal > > > > > > > > > On Tue, Oct 25, 2022 at 5:33 AM Alessandro Molina > > > <alessan...@voltrondata.com.invalid> wrote: > > > > > > > On Tue, Oct 25, 2022 at 1:55 AM Joris Van den Bossche < > > > > jorisvandenboss...@gmail.com> wrote: > > > > > > > > > > > > > > I think the main thing we will miss are the Links (relation between > > > > > issues), but we can try to promote some consistent usage of adding > > > > > "Duplicate of #...", "Related to #..." in top post of an issue when > > > > > appropriate. > > > > > > > > > > > > > If we plan to migrate to GitHub, I think we should add an Issue > > Template > > > ( > > > > > > > > > > > > > https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository > > > > ) to make sure we don't proliferate too many ways to do the same thing > > in > > > > terms of categorizing issues properly > > > > > > > > >
