pitrou commented on code in PR #13781: URL: https://github.com/apache/arrow/pull/13781#discussion_r952285380
########## docs/source/developers/bug_reports.rst: ########## @@ -18,82 +18,70 @@ .. _bug-reports: ******************************** -Report bugs and propose features +Bug reports and feature requests ******************************** -Using the software and sharing your experience is a very helpful contribution -itself. Those who actively develop Arrow need feedback from users on what -works and what doesn't. Alerting us to unexpected behavior and missing features, -even if you can't solve the problems yourself, help us understand and prioritize -work to improve the libraries. +Arrow relies upon user feedback to identify defects and improvement +opportunities. All users are encouraged to participate by creating bug reports +and feature request or commenting on existing issues. Even if you cannot +contribute solutions to the issues yourself, your feedback helps us understand +problems and prioritize work to improve the libraries. -We use `JIRA <https://issues.apache.org/jira/projects/ARROW/issues>`_ -to manage our development "todo" list and to maintain changelogs for releases. -In addition, the project's `Confluence site <https://cwiki.apache.org/confluence/display/ARROW>`_ -has some useful higher-level views of the JIRA issues. +.. _apache-arrow-jira: -To create a JIRA issue, you'll need to have an account on the ASF JIRA, which -you can `sign yourself up for <https://issues.apache.org/jira/secure/Signup!default.jspa>`_. -The JIRA server hosts bugs and issues for multiple Apache projects. The JIRA -project name for Arrow is "ARROW". +Apache Arrow Jira +================= -You don't need any special permissions on JIRA to be able to create issues. -Once you are more involved in the project and want to do more on JIRA, such as -assign yourself an issue, you will need "Contributor" permissions on the -Apache Arrow JIRA. To get this role, ask on the mailing list for a project -maintainer's help. +The Arrow project uses `Jira <https://issues.apache.org/jira/projects/ARROW/issues>`_ +to track issues - both bug reports and feature requests. No account or +permissions are required to view or search Jira issues. The Jira server +hosts issue tracking for multiple Apache projects. The Jira project name for +Arrow is "ARROW". +.. _required-permissions: -.. _jira-tips: +Required permissions +++++++++++++++++++++ -Tips for using JIRA -=================== +Any registered ASF Jira account may create Jira issues in the Apache Arrow +project without additional permissions. Individuals may +`create an ASF Jira account here <https://issues.apache.org/jira/secure/Signup!default.jspa>`_. +Self-assigning issues to work requires +the "Contributor" permission. This permission is set by project maintainers, +and may be requested by emailing the :ref:`development mailing list <mailing_list>`. -Before you create a new issue, we recommend you first -`search <https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20resolution%20%3D%20Unresolved>`_ -among existing Arrow issues. +.. _creating-issues: -When reporting a new issue, follow these conventions to help make sure the -right people see it: +Creating issues +=============== -* Use the **Component** field to indicate the area of the project that your - issue pertains to (for example "Python" or "C++"). -* Also prefix the issue title with the component name in brackets, for example - ``[Python] issue name`` ; this helps when navigating lists of open issues, - and it also makes our changelogs more readable. Most prefixes are exactly the - same as the **Component** name, with the following exceptions: +No one likes having bugs or feature gaps in their software, and in an ideal +world, all bugs would get fixed as soon as they were reported. However, time +and attention are finite, especially in an open-source project where most +contributors are participating in their spare time. All contributors in Apache +projects are volunteers and act as individuals, even if they are contributing Review Comment: > But even in that case, the company contributions are "voluntary" - they choose what work their employees work on, and are not explicitly directed by the project. I don't know if that's what the text is trying to convey. But in any case the word "volunteer" does sound misleading. Given that the paragraph is about "Tips for successful bug reports", it seems this sentence is a bit superfluous and could simply be removed, what do you think? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
