Attendees: - Percy T. Aucahuasi - Ian Cook - Raúl Cumplido - James Duong - Todd Farmer - Alenka Frim - Stephanie Hazlitt - Ian Joiner - David Li - Rok Mihevc - Matthew Topol - Joris Van den Bossche - Jacob Wujciak
Discussion: Migration from Jira to GitHub issues - ASF Infra has disabled creation of new Jira accounts [1] - The Arrow PMC has voted to move issue tracking to GitHub Issues [2] - There is ongoing work to migrate existing Jira issues to GitHub Issues and to improve the user and developer experience with GitHub Issues [3][4] - There was some discussion about whether we should stop new Jira issue creation now and begin to use GitHub Issues for all new issues (even before the existing Jira issues are migrated) - An alternative approach would be to have Arrow maintainers open a Jira issue to represent each GitHub Issue (if there is a fix PR) until the next release (11.0.0) at which point we can fully migrate off of Jira. This might make the release process more straightforward but would create extra work for maintainers in the interim. - The general consensus on the call was that we should stop new Jira issue creation now (pending a vote); Todd started a vote on the ML after the call [5] - This creates an immediate need to modify the PR merge script; Raúl opened an issue for this after the call [6]; this also raises the question of whether we still need the PR merge script or whether committers can use the "Squash and merge" button in the GitHub web UI instead - There was a discussion about whether we should still require contributors to open Issues before they open PRs; the general consensus was that this will be unnecessary in many cases (because GitHub PRs have all the same fields as GitHub Issues) however changes that require community discussion before implementation should still be opened as Issues first - The consensus was that we should put in practice a policy asking people to create meaningful descriptions in their PRs; at the next release when we are finalizing the migration we could consider adopting a standard convention for PR messages, such as Conventional Commits [7]; Jacob will send out an ML post about this - Todd expects that the mechanism for importing Jira issues to GitHub Issues should be mostly ready in about a week - Communications and docs updates will be required to inform contributors and maintainers of the changes; these are listed in [3] - We will need to do a lot of communications and docs updates Proposal for catalog support in Flight SQL - James started a discussion on the ML about improving support for catalogs in Flight SQL [8] - There are open questions in the ML discussion about how this should be implemented; additional comments are welcome Flight SQL name - Some people outside the core Arrow developer community have reported confusion about the differences between Flight SQL and ADBC, despite our explanations of the differences (for example: [9]) - Some people have also reported confusion about the Flight SQL name because it supports Substrait, not only SQL - There was some discussion about whether we might consider using "ADBC" as an umbrella name encompassing the client API, driver client driver, and wire protocol; there were some concerns about whether this makes logical sense and about investments in the current "Flight SQL" name; more ideas and discussion welcome [1] https://infra.apache.org/blog/jira-public-signup-disabled.html [2] https://lists.apache.org/thread/8pmlx3186b32hm36fkqxfj6vp2ltwkf7 [3] https://docs.google.com/document/d/1UaSJs-oyuq8QvlUPoQ9GeiwP19LK5ZzF_5-HLfHDCIg/ [4] https://github.com/apache/arrow/issues?q=is%3Aissue+is%3Aopen+MIGRATION [5] https://lists.apache.org/thread/v9sjwx8mdg0bfssbrlqz7c0wxwc8dx49 [6] https://github.com/apache/arrow/issues/14720 [7] https://www.conventionalcommits.org/ [8] https://lists.apache.org/thread/fd6r1n7vt91sg2c7fr35wcrsqz6x4645 [9] https://voltrondata.com/resources/update/2022/08/25/simplifying-database-connectivity-with-arrow-flight-sql-and-adbc On Tue, Nov 22, 2022 at 5:56 PM Ian Cook <i...@ursacomputing.com> wrote: > > Hi all, > > Our biweekly sync call is tomorrow at 12:00 noon Eastern time. > > The Zoom meeting URL for this and other biweekly Arrow sync calls is: > https://zoom.us/j/87649033008?pwd=SitsRHluQStlREM0TjJVYkRibVZsUT09 > > Alternatively, enter this information into the Zoom website or app to > join the call: > Meeting ID: 876 4903 3008 > Passcode: 958092 > > Thanks, > Ian
