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
