Thanks for the feedback - I've created the following to request changes to the ARROW project issue assignment scheme:
https://issues.apache.org/jira/browse/INFRA-23589 Duncan: It's particularly helpful to get your feedback on friction you experience as a recent first-time contributor. I'd very much like to hear more about the gaps you perceived and challenges you faced. I created https://issues.apache.org/jira/browse/ARROW-17447 to track this feedback - please feel free to add context there. On Thu, Aug 11, 2022 at 7:58 AM Duncan MacQuarrie <duncan.macquar...@wayflyer.com.invalid> wrote: > My two pence as a recent first-time contributor: being able to assign, and > Start Progress, on JIRA issues would be useful, and remove worries about > burdening busy maintainers with such admin queries. > > (Offtopic but related to new contributor experience: expanding > CONTRIBUTING.md to outline norms relating to setup of dev environment, CI > checks, code review etc. would be very welcome.) > > > On Thu, Aug 11, 2022 at 1:26 PM Neal Richardson < > neal.p.richard...@gmail.com> > wrote: > > > +1, SGTM > > > > Neal > > > > On Wed, Aug 10, 2022 at 6:17 PM Rok Mihevc <rok.mih...@gmail.com> wrote: > > > > > It would be great if this friction point is removed. +1 > > > > > > Rok > > > > > > On Wed, Aug 10, 2022 at 11:36 PM Sutou Kouhei <k...@clear-code.com> > > wrote: > > > > > > > +1 > > > > > > > > In <CAGNHocMShABErqKgLY= > svbeb7ncnnyn0p3yusdhrp6mvymf...@mail.gmail.com > > > > > > > "Proposal: Allow any ASF Jira user to assign ARROW issues" on Wed, > 10 > > > > Aug 2022 14:32:21 -0600, > > > > Todd Farmer <t...@voltrondata.com.INVALID> wrote: > > > > > > > > > Hello, > > > > > > > > > > Community members seeking to address issues in the ASF Jira ARROW > > > project > > > > > must both register for ASF Jira and be given the "Contributor" > role. > > > > > Current project documentation [1] instructs individuals to request > > this > > > > > role via this mailing list, or in a comment on the issue itself. > This > > > > adds > > > > > friction for new contributors, isn't very efficient, and is likely > to > > > > fail > > > > > at scale - it's hard to expect responsible parties to scan every > > issue > > > > > comment. > > > > > > > > > > One possible solution to reduce new contributor friction would be > to > > > > allow > > > > > any ASF-registered account to assign ARROW issues. Most ASF > projects > > > > > function as we do currently, but there are some notable exceptions. > > > > > Cassandra [2] [3] allows any ASF user to assign issues, as did > > Airflow > > > > [4] > > > > > (prior to migration to GitHub issues). Note that issue resolution > > would > > > > > remain restricted as it is today. > > > > > > > > > > Giving all ASF users the ability to assign ARROW issues may > increase > > > > issues > > > > > incorrectly assigned. If that proves to be the case, the proposed > > > change > > > > > could be reverted, or potentially mitigated through automation > (e.g., > > > > users > > > > > making assignment changes can only self-assign or set to > unassigned). > > > > > > > > > > Does the community support enabling any ASF user to assign ARROW > > > issues? > > > > > > > > > > [1] https://arrow.apache.org/docs/developers/bug_reports.html > > > > > [2] https://issues.apache.org/jira/browse/CASSANDRA-17035 (ensure > > > > logged in) > > > > > [3] https://issues.apache.org/jira/browse/INFRA-13811 > > > > > [4] https://issues.apache.org/jira/browse/INFRA-11953 > > > > > > > > > > Thanks, > > > > > > > > > > Todd > > > > > > > > > >
