You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@arrow.apache.org by jo...@apache.org on 2022/12/22 10:42:06 UTC
[arrow] branch master updated: GH-14885: [Docs] Make changes to the New Contrib Guide (Jira -> GitHub) (#14889)
This is an automated email from the ASF dual-hosted git repository.
jorisvandenbossche pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/arrow.git
The following commit(s) were added to refs/heads/master by this push:
new 3b26565813 GH-14885: [Docs] Make changes to the New Contrib Guide (Jira -> GitHub) (#14889)
3b26565813 is described below
commit 3b26565813221e2ea4b91c512098a1472e9a88c7
Author: Alenka Frim <Al...@users.noreply.github.com>
AuthorDate: Thu Dec 22 11:42:00 2022 +0100
GH-14885: [Docs] Make changes to the New Contrib Guide (Jira -> GitHub) (#14889)
This PR is part of the work to update the documentation as we are moving from Jira issue tracker to GitHub issues:
https://github.com/apache/arrow/issues/14822
Closes #14885
* Closes: #14885
Lead-authored-by: Alenka Frim <fr...@gmail.com>
Co-authored-by: Alenka Frim <Al...@users.noreply.github.com>
Co-authored-by: Joris Van den Bossche <jo...@gmail.com>
Co-authored-by: Raúl Cumplido <ra...@gmail.com>
Signed-off-by: Joris Van den Bossche <jo...@gmail.com>
---
docs/source/developers/guide/communication.rst | 76 ++++++----------
docs/source/developers/guide/documentation.rst | 23 ++---
docs/source/developers/guide/index.rst | 2 +-
.../guide/step_by_step/arrow_codebase.rst | 2 +-
.../guide/step_by_step/finding_issues.rst | 97 +++++----------------
.../developers/guide/step_by_step/pr_lifecycle.rst | 9 +-
.../developers/guide/tutorials/python_tutorial.rst | 61 ++++---------
.../developers/guide/tutorials/r_tutorial.rst | 23 +++--
.../developers/images/R_tutorial_jira_issue.jpeg | Bin 639086 -> 0 bytes
.../developers/images/jira_create_issue.jpeg | Bin 39797 -> 0 bytes
.../developers/images/jira_good_first_issue.jpeg | Bin 241925 -> 0 bytes
.../source/developers/images/jira_new_account.jpeg | Bin 42987 -> 0 bytes
.../developers/images/jira_search_component.jpeg | Bin 87082 -> 0 bytes
.../images/jira_search_documentation.jpeg | Bin 117897 -> 0 bytes
.../images/python_tutorial_jira_comment.jpeg | Bin 82115 -> 0 bytes
.../images/python_tutorial_jira_description.jpeg | Bin 94669 -> 0 bytes
.../images/python_tutorial_jira_issue.jpeg | Bin 162426 -> 0 bytes
.../images/python_tutorial_jira_title.jpeg | Bin 80541 -> 0 bytes
18 files changed, 90 insertions(+), 203 deletions(-)
diff --git a/docs/source/developers/guide/communication.rst b/docs/source/developers/guide/communication.rst
index 3ba0c3a2c3..a8659f83ac 100644
--- a/docs/source/developers/guide/communication.rst
+++ b/docs/source/developers/guide/communication.rst
@@ -52,64 +52,46 @@ Where to get help 👋
For any question you may have or problems you are facing you can write to
user or development :ref:`mailing_list` or you can create an issue on
-:ref:`github`.
-
-For searching through the issues, reporting bugs and creating feature
-requests or proposals you can use :ref:`jira` issue tracker.
-
-.. _jira:
-
-JIRA
-~~~~
-
-When to use JIRA?
-
-- If you want to **report a bug**.
-- If you want to **propose a new feature**.
-- If you want to **propose a bigger change in the documentation**.
-
-In these cases you can create a JIRA issue and connect with other
-contributors in the issue comments. It is good to mention the
-way you are planning to solve the issue and have one of the Arrow
-developers agree with your basic proposal for fixing it. Better
-to ask before you spend too much of your time on something that we
-might think is not a good idea.
-
-.. seealso::
-
- - :ref:`create_jira`
- - :ref:`creating-issues` and :ref:`bug-report-tips`
-
-- If you want to **solve an issue that is already in JIRA**, you should
- connect with other contributors in the issue comments.
-
-JIRA is used to discuss the problem before a Pull Request is possibly made
-(how to start, where to search for the solution, etc..).
+:ref:`github`. Also use GitHub to search through the issues, report bugs
+and create feature requests or proposals.
.. _github:
GitHub
~~~~~~
-Further options of communicating are provided through GitHub where the project
+Different options of communicating are provided through GitHub where the project
is hosted. What we use are GitHub Issues and Pull Requests.
-When to use GitHub?
+You can use GitHub issues to:
+
+- **ask questions**,
+- **report a bug**,
-- If you have **a problem with building** one of the Arrow libraries, you can
- create an issue on GitHub and discuss the possible solution (or write to the
- user mailing list).
+ .. seealso::
+
+ :ref:`How to make good bug reports and feature requests <bug-reports>`
+
+- **propose a new feature**,
+- **propose a bigger change in the documentation**,
+- report **a problem with building** one of the Arrow libraries and discuss
+ the possible solution (or write to the user mailing list).
Making an issue about things you are not sure about may feel intimidating,
but it is also useful for others and the project.
.. note::
- Make sure to add which operating system and Arrow version you are using in the
- issue description plus the debug information/error.
+ Make sure to add which operating system and Arrow version you are using
+ in the issue description plus the debug information/error.
+
+If you have **a new contribution already written**, you can create a Pull
+Request after creating a GitHub issue and mentioning the way you plan to
+implement it. It is important to have one of the Arrow developers agree with
+your basic proposal for fixing it. Better to ask before you spend too much of
+your time on something that we might think is not a good idea.
-- If you have **a new contribution already written**, you can create a Pull Request after
- creating a JIRA ticket and mentioning the way you plan to implement it.
-- GitHub is also used to discuss your work after the **Pull Request** is made.
+If you want to **solve an issue that is already in GitHub**, you should
+connect with other contributors in the issue comments.
.. _mailing_list:
@@ -117,10 +99,10 @@ Mailing Lists
~~~~~~~~~~~~~
You can subscribe to the **user** or **development** mailing list and browse for
-previous topics or ask questions. Whereas discussion on GitHub and JIRA
-only notifies people who have subscribed to that particular Pull Request or issue,
-the mailing list allows you to broadcast to all users or developers. Use these when
-you want to get feedback or answers from a wider audience.
+previous topics or ask questions. Whereas discussion on GitHub only notifies people
+who are mentioned or are collaborating on a Pull Request, the mailing list allows
+you to broadcast to all users or developers. Use these when you want to get feedback
+or answers from a wider audience.
There is also a **biweekly developers sync call** that anyone is welcome to join.
It is announced on the development mailing list together with the link to join.
diff --git a/docs/source/developers/guide/documentation.rst b/docs/source/developers/guide/documentation.rst
index a2bf64ccdf..8e0c7c9b90 100644
--- a/docs/source/developers/guide/documentation.rst
+++ b/docs/source/developers/guide/documentation.rst
@@ -37,26 +37,15 @@ incomplete or inaccurate, share your hard-earned knowledge
with the rest of the community.
If you didn't come across something to improve in the
-documentation itself, you can search for an issue on JIRA.
+documentation itself, you can search for an issue in GitHub.
.. note::
- When searching for JIRA issue that deals with documentation,
- try selecting **Components** from the **More** tab in JIRA search
- and select **Documentation** from the list.
+ When searching for an issue that deals with documentation,
+ navigate to `GitHub labels <https://github.com/apache/arrow/labels>`_
+ and select **Component: Documentation** or search for **Documentation**
+ in the "Search all labels" window.
- See `Example search. <https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20%3D%20Open%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20Documentation%20AND%20assignee%20in%20(EMPTY)%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC>`_
-
- .. figure:: /developers/images/jira_search_component.jpeg
- :scale: 40 %
- :alt: selecting Components in JIRA search
-
- First select Components tab in JIRA.
-
- .. figure:: /developers/images/jira_search_documentation.jpeg
- :scale: 40 %
- :alt: selecting Documentation in JIRA search
-
- Then choose Documentation from the Components list.
+ See `Example search. <https://github.com/apache/arrow/issues?q=is%3Aopen+is%3Aissue+label%3A%22Component%3A+Documentation%22+>`_
Documentation improvements are also a great way to gain some
experience with our submission and review process without
diff --git a/docs/source/developers/guide/index.rst b/docs/source/developers/guide/index.rst
index cbaf272876..6a34258b20 100644
--- a/docs/source/developers/guide/index.rst
+++ b/docs/source/developers/guide/index.rst
@@ -128,7 +128,7 @@ of adding a basic feature.
Communication is very important. You may need some help solving problems
you encounter on the way (this happens to developers all the time). Also,
- if you have a JIRA issue you want to solve, then it is advisable to let the team
+ if you have a GitHub issue you want to solve, then it is advisable to let the team
know you are working on it and may need some help.
See possible channels of :ref:`communication`.
diff --git a/docs/source/developers/guide/step_by_step/arrow_codebase.rst b/docs/source/developers/guide/step_by_step/arrow_codebase.rst
index 0250434ffe..0beece991b 100644
--- a/docs/source/developers/guide/step_by_step/arrow_codebase.rst
+++ b/docs/source/developers/guide/step_by_step/arrow_codebase.rst
@@ -128,7 +128,7 @@ C++ we must create the binding manually to use it in that implementation.
As mentioned before, the underlying code is written in C++.
Python then connects to it via Cython. If you
are not familiar with it you can ask for help and remember,
- **look for similar Pull Requests and JIRA issues!**
+ **look for similar Pull Requests and GitHub issues!**
**Adding tests**
diff --git a/docs/source/developers/guide/step_by_step/finding_issues.rst b/docs/source/developers/guide/step_by_step/finding_issues.rst
index 537c345319..89c5a81b73 100644
--- a/docs/source/developers/guide/step_by_step/finding_issues.rst
+++ b/docs/source/developers/guide/step_by_step/finding_issues.rst
@@ -18,11 +18,11 @@
.. SCOPE OF THIS SECTION
.. This section should include additional information
-.. about JIRA, how to find issues or how to create one.
+.. about GitHub, how to find issues or how to create one.
.. Should not duplicate with Report bugs and propose features
.. section:
-.. https://arrow.apache.org/docs/developers/contributing.html#tips-for-using-jira
+.. https://arrow.apache.org/docs/developers/bug_reports.html#bug-reports
.. _finding-issues:
@@ -38,70 +38,25 @@ you might already have a bug to fix in mind, or a new feature that
you want to implement. Or you still need an issue to work on and
you need some help with finding one.
-For both cases, JIRA is the issue tracker that we use.
+For both cases, GitHub is the issue tracker that we use.
-First we will explain how to use JIRA if you have a fix or a feature
-to work on that doesn't yet have a JIRA ticket open, in which case you
-will need to create a JIRA ticket yourself.
+- If you do not have a GitHub account yet, navigate to the
+ `GitHub login page <https://github.com/join>`_ to create one.
+- If you need help with creating a new GitHub issue see the
+ `GitHub documentation <https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue>`_.
-Secondly, we will show you a way to find good first issues to work on.
+When the ticket is created you can start a discussion about it in the GitHub comments.
-
-Creating a JIRA account
-==========================
-
-First thing you need to do is to make an account on the ASF JIRA following
-`this link <https://issues.apache.org/jira/secure/Signup!default.jspa>`_.
-You will be asked to select a language and choose an avatar if you wish. If
-the registration is successful you will see:
-
-.. figure:: /developers/images/jira_new_account.jpeg
- :scale: 70 %
- :alt: creating an ASF JIRA account
-
- The window you get after creating an account on the ASF JIRA.
-
-
-.. _create_jira:
-
-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, …).
-
-.. 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.
-
-You are ready to create the issue! Add a title and a description following
-the guidance in :ref:`creating issues <creating-issues>` and you are ready to go!
-
-.. seealso::
- :ref:`Creating issues <creating-issues>`
-
-You don’t need any special permissions on JIRA to be able to create
-or self-assign issues.
-To get this role, ask on the :ref:`dev mailing list <mailing_list>`.
-
-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
-================================
+GitHub labels
+=============
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.
+contributors, we have added a label **“good-first-issue”** to some
+GitHub issues.
.. 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 issues `good-first-issue label listing
+ <https://github.com/apache/arrow/labels/good-first-issue>`_
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
@@ -109,32 +64,24 @@ 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:: /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 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.
-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.
+Also, do not hesitate to ask questions in the comment. You can get some
+pointers about where to start and similar issues already solved.
**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.
**Ask questions**
-Please do ask questions, either on the JIRA itself or on the dev mailing list,
-if you have doubts about where to begin or what approach to take.
-This is particularly a good idea if this is your first code contribution,
+Please do ask questions, either on the GitHub issue itself or on the dev
+mailing list, if you have doubts about where to begin or what approach to
+take. This is particularly a good idea if this is your first code contribution,
so you can get some sense of what the core developers in this part of the
project think a good solution looks like. For best results, ask specific,
direct questions, such as:
diff --git a/docs/source/developers/guide/step_by_step/pr_lifecycle.rst b/docs/source/developers/guide/step_by_step/pr_lifecycle.rst
index fa1e1a47f3..6cdb642bc3 100644
--- a/docs/source/developers/guide/step_by_step/pr_lifecycle.rst
+++ b/docs/source/developers/guide/step_by_step/pr_lifecycle.rst
@@ -38,7 +38,7 @@ the official Arrow repository which is saved in your set up as
``upstream``.
You should have Git set up by now, have cloned the repository,
-have successfully built Arrow and have a JIRA issue to work on.
+have successfully built Arrow and have a GitHub issue to work on.
**Before making changes to the code, you should create a new
branch in Git.**
@@ -189,16 +189,15 @@ that supports quality and with it you can learn a lot.
If it still takes too long to get merged, do not hesitate to remind
maintainers in the comment section of the pull request and post
-reminders on the JIRA ticket also.
+reminders on the GitHub issue also.
How to get your pull request to be reviewed?
--------------------------------------------
Arrow maintainers will be notified when a pull request is created and
they will get to it as soon as possible. If days pass and it still had
-not been reviewed go ahead and mention the reporter of the JIRA issue
-or a developer that you communicated with via JIRA comments, mailing
-list or GitHub.
+not been reviewed go ahead and mention the reporter of the GitHub issue
+or a developer that you communicated with via mailing list or GitHub.
To put a **mention** in GitHub insert @ in the comment and select the
username from the list.
diff --git a/docs/source/developers/guide/tutorials/python_tutorial.rst b/docs/source/developers/guide/tutorials/python_tutorial.rst
index 8184975e81..ad5e646289 100644
--- a/docs/source/developers/guide/tutorials/python_tutorial.rst
+++ b/docs/source/developers/guide/tutorials/python_tutorial.rst
@@ -73,8 +73,8 @@ the instructions for the building process in this tutorial.
For the **instructions** on how to build PyArrow refer to the
:ref:`build_pyarrow` section.
-Create a JIRA issue for the new feature
----------------------------------------
+Create a GitHub issue for the new feature
+-----------------------------------------
We will add a new feature that imitates an existing function
``min_max`` from the ``arrow.compute`` module but makes the
@@ -84,49 +84,18 @@ made-up function for the purpose of this guide.
See the example of the ``pc.min_max`` in
`this link <https://arrow.apache.org/cookbook/py/data.html#computing-mean-min-max-values-of-an-array>`_.
-First we need to create a JIRA issue as it doesn't exist yet.
-With a JIRA account created we will navigate to the
-`Apache Arrow JIRA dashboard <https://issues.apache.org/jira/projects/ARROW>`_
-and click on the **Create** button.
-
-.. figure:: /developers/images/python_tutorial_jira_title.jpeg
- :scale: 70 %
- :alt: JIRA dashboard with a window for creating a new issue.
-
- Creating a JIRA issue, adding title (summary) and components.
-
-.. figure:: /developers/images/python_tutorial_jira_description.jpeg
- :scale: 70 %
- :alt: JIRA dashboard with a window for creating a
- description for the new issue.
-
- Creating a JIRA issue, adding a description.
+First we need to create a GitHub issue as it doesn't exist yet.
+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. If that option is not working, we would
-need to ask for a project maintainer’s help on the
-:ref:`mailing_list`.
-
-Lets also add some comments to start a conversation.
-
-.. figure:: /developers/images/python_tutorial_jira_comment.jpeg
- :scale: 50 %
- :alt: JIRA issue page where comment is being added.
-
- Adding a comment to the JIRA ticket we created.
-
-We have successfully created a new JIRA issue with index
-`ARROW-14977 <https://issues.apache.org/jira/browse/ARROW-14977>`_.
-
-.. figure:: /developers/images/python_tutorial_jira_issue.jpeg
- :scale: 50 %
- :alt: JIRA page of the issue just created.
-
- Our JIRA issue. Yay!
+know we are working on it. You can do that with adding a comment
+``take`` to the issue created.
.. seealso::
- To get more information on JIRA issues go to
+ To get more information on GitHub issues go to
:ref:`finding-issues` part of the guide.
Start the work on a new branch
@@ -531,9 +500,13 @@ by clicking on **Compare & pull request**.
Notice bar on the Apache Arrow repository.
-First we need to change the Title to *ARROW-14977: [Python] Add a "made-up"*
-*feature for the guide tutorial* in order to match it
-with the JIRA issue. Note a punctuation mark was added!
+First we need to change the Title to *ARROW-14977: [Python] Add a "made-up"
+feature for the guide tutorial* in order to match it
+with the issue. Note a punctuation mark was added!
+
+*Extra note: when this tutorial was created, we had been using the Jira issue
+tracker. As we are currently using GitHub issues, the title would be prefixed
+with GH-14977: [Python] Add a "made-up" feature for the guide tutorial*.
We will also add a description to make it clear to others what we are
trying to do.
@@ -548,7 +521,7 @@ Pull Request in the Apache Arrow repository.
Here it is, our Pull Request!
-The Pull Request gets connected to the JIRA issue and the CI is
+The Pull Request gets connected to the issue and the CI is
running. After some time passes and we get a review we can correct
the code, comment, resolve conversations and so on. The Pull Request
we made can be viewed `here <https://github.com/apache/arrow/pull/11900>`_.
diff --git a/docs/source/developers/guide/tutorials/r_tutorial.rst b/docs/source/developers/guide/tutorials/r_tutorial.rst
index 3b8acaab65..a4ae9df139 100644
--- a/docs/source/developers/guide/tutorials/r_tutorial.rst
+++ b/docs/source/developers/guide/tutorials/r_tutorial.rst
@@ -98,19 +98,12 @@ the instructions for the building process in this tutorial.
For the **instructions** on how to build the R package refer to the
`R developer docs <https://arrow.apache.org/docs/r/articles/developing.html>`_.
-JIRA issue
-----------
+The issue
+---------
-In this tutorial we will be tackling a JIRA issue for implementing
+In this tutorial we will be tackling an issue for implementing
a simple binding for ``mday()`` function that will match that of the
-existing R function from ``lubridate``. The issue can be found on
-`this link <https://issues.apache.org/jira/browse/ARROW-14816>`_.
-
-.. figure:: /developers/images/R_tutorial_jira_issue.jpeg
- :scale: 40 %
- :alt: JIRA page of the issue for the R binding.
-
- JIRA page of the issue for the lubridate::mday() binding.
+existing R function from ``lubridate``.
.. note::
@@ -435,7 +428,11 @@ by clicking on **Compare & pull request**.
First we need to change the Title to **ARROW-14816: [R] Implement
bindings for lubridate::mday()** in order to match it with the
-JIRA issue. Note a punctuation mark was added!
+issue. Note a punctuation mark was added!
+
+*Extra note: when this tutorial was created, we had been using the Jira issue
+tracker. As we are currently using GitHub issues, the title would be prefixed
+with GH-14816: [R] Implement bindings for lubridate::mday()*.
We will also add a description to make it clear to others what we are trying to do.
@@ -456,7 +453,7 @@ a Pull Request in the Apache Arrow repository.
Here it is, our Pull Request!
-The pull request gets connected to the JIRA issue and the CI is running.
+The pull request gets connected to the issue and the CI is running.
After some time passes and we get a review we can correct the code,
comment, resolve conversations and so on.
diff --git a/docs/source/developers/images/R_tutorial_jira_issue.jpeg b/docs/source/developers/images/R_tutorial_jira_issue.jpeg
deleted file mode 100644
index acab37e81e..0000000000
Binary files a/docs/source/developers/images/R_tutorial_jira_issue.jpeg and /dev/null differ
diff --git a/docs/source/developers/images/jira_create_issue.jpeg b/docs/source/developers/images/jira_create_issue.jpeg
deleted file mode 100644
index 5aa41a738e..0000000000
Binary files a/docs/source/developers/images/jira_create_issue.jpeg and /dev/null differ
diff --git a/docs/source/developers/images/jira_good_first_issue.jpeg b/docs/source/developers/images/jira_good_first_issue.jpeg
deleted file mode 100644
index 3d4a96bf43..0000000000
Binary files a/docs/source/developers/images/jira_good_first_issue.jpeg and /dev/null differ
diff --git a/docs/source/developers/images/jira_new_account.jpeg b/docs/source/developers/images/jira_new_account.jpeg
deleted file mode 100644
index 5e44a2d127..0000000000
Binary files a/docs/source/developers/images/jira_new_account.jpeg and /dev/null differ
diff --git a/docs/source/developers/images/jira_search_component.jpeg b/docs/source/developers/images/jira_search_component.jpeg
deleted file mode 100644
index d69a05b4db..0000000000
Binary files a/docs/source/developers/images/jira_search_component.jpeg and /dev/null differ
diff --git a/docs/source/developers/images/jira_search_documentation.jpeg b/docs/source/developers/images/jira_search_documentation.jpeg
deleted file mode 100644
index e3fcbc4a4d..0000000000
Binary files a/docs/source/developers/images/jira_search_documentation.jpeg and /dev/null differ
diff --git a/docs/source/developers/images/python_tutorial_jira_comment.jpeg b/docs/source/developers/images/python_tutorial_jira_comment.jpeg
deleted file mode 100644
index 5460a2b87d..0000000000
Binary files a/docs/source/developers/images/python_tutorial_jira_comment.jpeg and /dev/null differ
diff --git a/docs/source/developers/images/python_tutorial_jira_description.jpeg b/docs/source/developers/images/python_tutorial_jira_description.jpeg
deleted file mode 100644
index 46a3a73b07..0000000000
Binary files a/docs/source/developers/images/python_tutorial_jira_description.jpeg and /dev/null differ
diff --git a/docs/source/developers/images/python_tutorial_jira_issue.jpeg b/docs/source/developers/images/python_tutorial_jira_issue.jpeg
deleted file mode 100644
index 918fcbdc1d..0000000000
Binary files a/docs/source/developers/images/python_tutorial_jira_issue.jpeg and /dev/null differ
diff --git a/docs/source/developers/images/python_tutorial_jira_title.jpeg b/docs/source/developers/images/python_tutorial_jira_title.jpeg
deleted file mode 100644
index 9da8950d3a..0000000000
Binary files a/docs/source/developers/images/python_tutorial_jira_title.jpeg and /dev/null differ