From c6f53ca65c03c49d57ebe5b716a475359a58c84e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C3=A9mi=20Verschelde?= Date: Thu, 10 Feb 2022 15:57:12 +0100 Subject: [PATCH] Contributing: 'junior job' renamed to 'good first issue' --- community/contributing/bug_triage_guidelines.rst | 4 ++-- community/contributing/ways_to_contribute.rst | 5 +++-- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/community/contributing/bug_triage_guidelines.rst b/community/contributing/bug_triage_guidelines.rst index def4c88ea..48c0c1803 100644 --- a/community/contributing/bug_triage_guidelines.rst +++ b/community/contributing/bug_triage_guidelines.rst @@ -70,8 +70,8 @@ The following labels are currently defined in the Godot repository: `godot-proposals `__ instead. - *For PR meeting*: the issue needs to be discussed in a pull request meeting. These meetings are public and are held on the `Godot Contributors Chat `_. -- *Junior job*: the issue is *assumed* to be an easy one to fix, which makes - it a great fit for junior contributors who need to become familiar with +- *Good first issue*: the issue is *assumed* to be an easy one to fix, which makes + it a great fit for new contributors who need to become familiar with the code base. - *High priority:* the issue is particularly important as it can prevent people from releasing their projects or cause data loss. diff --git a/community/contributing/ways_to_contribute.rst b/community/contributing/ways_to_contribute.rst index 595deada6..ea22647dc 100644 --- a/community/contributing/ways_to_contribute.rst +++ b/community/contributing/ways_to_contribute.rst @@ -84,8 +84,9 @@ To ensure good collaboration and overall quality, the Godot developers enforce some rules for code contributions, for example regarding the style to use in the C++ code (indentation, brackets, etc.) or the Git and PR workflow. -A good place to start is by searching for issues tagged as `junior jobs `_ -(or `Hacktoberfest `_ during October) on GitHub. +A good place to start is by searching for issues tagged as +`good first issue `_ +on GitHub. .. seealso:: Technical details about the PR workflow are outlined in a specific section, :ref:`doc_pr_workflow`.