GH-51232: [CI] Remove the "take" comment bot for self-assigning issues

.github/workflows/comment_bot.yml

@@ -56,21 +56,3 @@ jobs:
           archery --debug trigger-bot \
             --event-name "${GITHUB_EVENT_NAME}" \
             --event-payload "${GITHUB_EVENT_PATH}"
-
-  issue_assign:
-    name: "Assign issue"
-    permissions:
-      issues: write
-    if: github.event.comment.body == 'take'
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/github-script@v9
-        with:
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          script: |
-            github.rest.issues.addAssignees({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                issue_number: context.payload.issue.number,
-                assignees: context.payload.comment.user.login
-            });

CONTRIBUTING.md

@@ -25,7 +25,8 @@ The Arrow project uses GitHub as a bug tracker.  To report a bug, sign in to
 your GitHub account, navigate to [GitHub issues](https://github.com/apache/arrow/issues)
 and click on **New issue** .
 
-To be assigned to an issue, add a comment "take" to that issue.
+To be assigned to an issue, leave a comment on that issue saying you would
+like to work on it, and a committer or collaborator will assign it to you.
 
 Before you create a new bug entry, we recommend you first search among existing
 Arrow issues in

docs/source/developers/bug_reports.rst

@@ -243,5 +243,7 @@ Issue assignment
 ++++++++++++++++
 
 Assignment signals commitment to work on an issue, and contributors should
-self-assign issues when that work starts. Anyone can now self-assign issues
-by commenting ``take``.
+be assigned to issues when that work starts. If you would like to work on an
+issue, leave a comment saying so and a committer or collaborator will assign
+it to you. See :ref:`collaborators` for how to get the ability to assign
+issues yourself.

docs/source/developers/guide/step_by_step/finding_issues.rst

@@ -79,8 +79,8 @@ in the comments.
 
    When you find a GitHub issue you would like to work on, please mention
    your interest in the comment section of that issue; that way we will know
-   you are working on it.
-   Consider assigning yourself to the issue (:ref:`issue-assignment`) when the work starts.
+   you are working on it and can assign the issue to you
+   (see :ref:`issue-assignment`).
 
 Also, do not hesitate to ask questions in the comment. You can get some
 pointers about where to start and similar issues already solved.

docs/source/developers/guide/tutorials/python_tutorial.rst

@@ -89,9 +89,10 @@ With a GitHub account created we will navigate to the
 `GitHub issue dashboard <https://github.com/apache/arrow/issues>`_
 and click on the **New issue** button.
 
-We should make sure to assign ourselves to the issue to let others
-know we are working on it. You can do that with adding a comment
-``take`` to the issue created.
+We should make sure to let others know we are working on the issue.
+You can do that by adding a comment to the issue created saying you
+would like to work on it, and a committer or collaborator will assign
+it to you.
 
 .. seealso::
 

docs/source/developers/reviewing.rst

@@ -296,6 +296,8 @@ In addition, we use the following labels to indicate priority:
   superset of issues marked "Critical Fix", as it also contains certain fixes
   to issues causing errors and crashes.
 
+.. _collaborators:
+
 Collaborators
 =============