[GitHub] [arrow] thisisnic commented on a change in pull request #12483: ARROW-15349: [Doc][Guide] Existing Contributors page - update

[GitBox <gi...@apache.org>]

thisisnic commented on a change in pull request #12483:
URL: https://github.com/apache/arrow/pull/12483#discussion_r829212895



##########
File path: docs/source/developers/guide/step_by_step/finding_issues.rst
##########
@@ -64,57 +67,88 @@ you will see:
 How to create a JIRA issue
 ==========================
 
-After creating an account you can click **Create an issue** and select **Apache Arrow project**
-and **Type** of the issue (Bug, Feature, …).
+After creating an account you can click **Create an issue** and select
+**Apache Arrow project** and **Type** of the issue (Bug, Feature, …).
 
-.. figure:: jira_create_issue.jpeg
+.. figure:: /developers/images/jira_create_issue.jpeg
    :scale: 70 %
    :alt: creating JIRA issue
 
    The window to create a JIRA issue.
 
-If you are already in JIRA dashboard click the red ``create`` button in the top to do the same.
+If you are already in JIRA dashboard click the red ``create`` button in
+the top to do the same.
 
-You are ready to create the issue! Add a title and a description following the
-:ref:`tips for using JIRA <jira-tips>` and you are ready to go!
+You are ready to create the issue! Add a title and a description following
+the :ref:`tips for using JIRA <jira-tips>` and you are ready to go!
 
 .. seealso::
 	:ref:`Tips for using JIRA <jira-tips>`
 
 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, for example assigning
-yourself an issue, you will need **“Contributor” permissions**. To get this role, ask on the
-:ref:`mailing_list` or in the comment of the JIRA issue you created.
+Once you are more involved in the project and want to do more on JIRA, for
+example assigning yourself an issue, you will need **“Contributor” permissions**.
+To get this role, ask on the :ref:`mailing_list` or in the comment of the JIRA
+issue you created.
 
-When the ticket is created you can start a discussion about it in the JIRA comments section.
+When the ticket is created you can start a discussion about it in the
+JIRA comments section.
 
 How we use JIRA to find an issue
 ================================
 
-To make it easier for you to find issues that are well-suited for new contributors, we have added labels
-like “good-first-issue” or “beginner” to some JIRA tickets.
+To make it easier for you to find issues that are well-suited for new
+contributors, we have added labels like “good-first-issue” or “beginner”
+to some JIRA tickets.
 
 .. seealso::
-	Search for good first/second issues with labels like in the `link here
-	<https://issues.apache.org/jira/issues/?filter=-4&jql=project%20%3D%20ARROW%20AND%20status%20%3D%20Open%20AND%20labels%20in%20(Beginner%2C%20beginner%2C%20beginners%2C%20beginnner%2C%20beginner-friendly%2C%20good-first-issue%2C%20good-second-issue%2C%20GoodForNewContributors%2C%20newbie%2C%20easyfix%2C%20documentation)%20order%20by%20created%20DESC>`_
+   Search for good first/second issues with labels like in the `link here
+   <https://issues.apache.org/jira/issues/?filter=-4&jql=project%20%3D%20ARROW%20AND%20status%20%3D%20Open%20AND%20labels%20in%20(Beginner%2C%20beginner%2C%20beginners%2C%20beginnner%2C%20beginner-friendly%2C%20good-first-issue%2C%20good-second-issue%2C%20GoodForNewContributors%2C%20newbie%2C%20easyfix%2C%20documentation)%20order%20by%20created%20DESC>`_
 
-The issues labeled as good first issues should take no more than two days or a weekend to
-fix them. Once you dig into the code you may find that the issue is not easy at all - this can
-happen as the problem could be harder than the person who triaged the ticket expected it to be.
-Don't hesitate to write that in the comments.
+The issues labeled as good first issues should take no more than two days or
+a weekend to fix them. Once you dig into the code you may find that the issue
+is not easy at all - this can happen as the problem could be harder than the
+person who triaged the ticket expected it to be. Don't hesitate to write that
+in the comments.
 
-.. figure:: jira_good_first_issue.jpeg
+.. figure:: /developers/images/jira_good_first_issue.jpeg
    :scale: 45 %
    :alt: finding good first JIRA issue
 
    Example of the list of good first issues.
 
 .. note::
-	When you find a JIRA 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.
+   
+   When you find a JIRA 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.
 
 Also, do not hesitate to ask questions in the comment section of the issue.
 You can get some pointers about where to start and similar issues already solved.
 
-**Do not forget to create a new branch once you have created or chosen an issue you will be
-working on!** Follow the instructions in the :ref:`pr_lifecycle` section or follow the next section: :ref:`arrow-codebase`.
+**What if an issue is already asigned?**
+Anything that’s not in the “In Progress” state is fair game, even if it is
+“Assigned” to someone, particularly if it has not been recently updated.
+When in doubt, comment on the issue asking if they mind if you try to put
+together a pull request; interpret no response to mean that you’re free to
+proceed.
+
+**Aske questions**

Review comment:
       ```suggestion
   **Ask questions**
   ```




-- 
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-unsubscribe@arrow.apache.org

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