jorisvandenbossche commented on code in PR #14852:
URL: https://github.com/apache/arrow/pull/14852#discussion_r1042208179


##########
CONTRIBUTING.md:
##########
@@ -21,42 +21,35 @@
 
 ## Did you find a bug?
 
-The Arrow project uses JIRA as a bug tracker.  To report a bug, you'll have
-to first create an account on the
-[Apache Foundation JIRA](https://issues.apache.org/jira/).  The JIRA server
-hosts bugs and issues for multiple Apache projects.  The JIRA project name
-for Arrow is "ARROW".
-
-To be assigned to an issue, ask an Arrow JIRA admin to go to
-[Arrow 
Roles](https://issues.apache.org/jira/plugins/servlet/project-config/ARROW/roles),
-click "Add users to a role," and add you to the "Contributor" role.  Most
-committers are authorized to do this; if you're a committer and aren't
-able to load that project admin page, have someone else add you to the
-necessary role.
-
-Before you create a new bug entry, we recommend you first
-[search](https://issues.apache.org/jira/projects/ARROW/issues/ARROW-5140?filter=allopenissues)
-among existing Arrow issues.
-
-When you create a new JIRA entry, please don't forget to fill the "Component"
-field.  Arrow has many subcomponents and this helps triaging and filtering
-tremendously.  Also, we conventionally prefix the issue title with the 
component
-name in brackets, such as "[C++] Crash in Array::Frobnicate()", so as to make
-lists more easy to navigate, and we'd be grateful if you did the same.
+The Arrow project uses GitHub as a bug tracker.  To report a bug, sign in to
+your GitHub account and select **Bug Report** in the
+[GitHub issues](https://github.com/apache/arrow/issues/new/choose).
+
+To be assigned to an issue, add a comment "take: #ISSUE-NUMBER" to that issue.

Review Comment:
   ```suggestion
   To be assigned to an issue, add a comment "take" to that issue.
   ```
   
   (I _think_ just "take" is enough)



##########
CONTRIBUTING.md:
##########
@@ -21,42 +21,35 @@
 
 ## Did you find a bug?
 
-The Arrow project uses JIRA as a bug tracker.  To report a bug, you'll have
-to first create an account on the
-[Apache Foundation JIRA](https://issues.apache.org/jira/).  The JIRA server
-hosts bugs and issues for multiple Apache projects.  The JIRA project name
-for Arrow is "ARROW".
-
-To be assigned to an issue, ask an Arrow JIRA admin to go to
-[Arrow 
Roles](https://issues.apache.org/jira/plugins/servlet/project-config/ARROW/roles),
-click "Add users to a role," and add you to the "Contributor" role.  Most
-committers are authorized to do this; if you're a committer and aren't
-able to load that project admin page, have someone else add you to the
-necessary role.
-
-Before you create a new bug entry, we recommend you first
-[search](https://issues.apache.org/jira/projects/ARROW/issues/ARROW-5140?filter=allopenissues)
-among existing Arrow issues.
-
-When you create a new JIRA entry, please don't forget to fill the "Component"
-field.  Arrow has many subcomponents and this helps triaging and filtering
-tremendously.  Also, we conventionally prefix the issue title with the 
component
-name in brackets, such as "[C++] Crash in Array::Frobnicate()", so as to make
-lists more easy to navigate, and we'd be grateful if you did the same.
+The Arrow project uses GitHub as a bug tracker.  To report a bug, sign in to
+your GitHub account and select **Bug Report** in the
+[GitHub issues](https://github.com/apache/arrow/issues/new/choose).

Review Comment:
   "in the github issues" sounds incomplete. Maybe the "github issues form" or 
"github issues selector"?
   
   Alternatively, we could also point people to 
https://github.com/apache/arrow/issues and direct them to click on "New issue" ?



##########
README.md:
##########
@@ -93,12 +93,13 @@ integrations in other projects, we'd be happy to have you 
involved:
 - Join the mailing list: send an email to
   [dev-subscr...@arrow.apache.org][1]. Share your ideas and use cases for the
   project.
-- [Follow our activity on JIRA][3]
+- Follow our activity on [GitHub issues][3] and [GitHub labels][6]

Review Comment:
   Is the link to the labels needed? (you also can't follow or watch issues 
based on the label)



-- 
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: github-unsubscr...@arrow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to