You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@community.apache.org by se...@apache.org on 2023/03/29 18:29:00 UTC
[comdev-site] branch master updated: JIRA is properly called Jira (according to Infra)
This is an automated email from the ASF dual-hosted git repository.
sebb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/comdev-site.git
The following commit(s) were added to refs/heads/master by this push:
new da27c74 JIRA is properly called Jira (according to Infra)
da27c74 is described below
commit da27c74083f46543c656ef24d7947bdc88e03165
Author: Sebb <se...@apache.org>
AuthorDate: Wed Mar 29 19:28:51 2023 +0100
JIRA is properly called Jira (according to Infra)
---
layouts/_default/baseof.html | 5 +++--
source/gettingStarted/101.md | 2 +-
source/gsoc/gsoc-admin-tasks.md | 8 ++++----
source/gsoc/guide-to-being-a-mentor.md | 6 +++---
source/newcommitter.md | 4 ++--
5 files changed, 13 insertions(+), 12 deletions(-)
diff --git a/layouts/_default/baseof.html b/layouts/_default/baseof.html
index 11aaa27..798bd34 100644
--- a/layouts/_default/baseof.html
+++ b/layouts/_default/baseof.html
@@ -71,7 +71,8 @@
<a class="dropdown-item" href="/contactpoints.html">Contact Points Within the ASF</a>
<a class="dropdown-item" href="https://whimsy.apache.org/board/minutes/Community_Development.html#2009-11-01">ComDev Original Board Resolution</a>
<a class="dropdown-item" href="https://whimsy.apache.org/board/minutes/Community_Development.html">ComDev Board Reports</a>
- <a class="dropdown-item" href="https://issues.apache.org/jira/projects/COMDEV">Community Development JIRA</a>
+ <a class="dropdown-item" href="https://issues.apache.org/jira/projects/COMDEV">Community Development Jira</a>
+ <a class="dropdown-item" href="https://issues.apache.org/jira/projects/GSOC">GSoC Jira</a>
<div class="dropdown-divider"></div>
<a class="dropdown-item text-uppercase disabled" href="#">About Apache</a>
<a class="dropdown-item" href="https://www.apache.org/">The Apache Software Foundation</a>
@@ -96,7 +97,7 @@
<a class="dropdown-item" href="/gsoc/mentee-ranking-process.html">Mentee Ranking Process</a>
<a class="dropdown-item" href="/gsoc/experiences.html">Past GSoC Experiences</a>
<a class="dropdown-item" href="/gsoc/guide-to-being-a-mentor.html">Guide to being a Mentor</a>
- <a class="dropdown-item" href="/gsoc/use-the-comdev-issue-tracker-for-gsoc-tasks.html">Using ComDev's JIRA for GSoC Ideas</a>
+ <a class="dropdown-item" href="/gsoc/use-the-comdev-issue-tracker-for-gsoc-tasks.html">Using ComDev's Jira for GSoC Ideas</a>
<a class="dropdown-item" href="/gsoc/gsoc-admin-tasks.html">Tasks of a GSoC Admin at the ASF</a>
</div>
</li>
diff --git a/source/gettingStarted/101.md b/source/gettingStarted/101.md
index 408ab93..22997a6 100644
--- a/source/gettingStarted/101.md
+++ b/source/gettingStarted/101.md
@@ -40,7 +40,7 @@ projects page linked above.
In the project's issue tracker you will find details of bugs that have been reported and feature
requests the project is considering. This should give you some
inspiration about how you might be able to help the project community. If
-you are looking for a beginner-level issue, try searching JIRA for issues
+you are looking for a beginner-level issue, try searching Jira for issues
with the label "GSoC" or "mentor"; these are issues the community feels are
manageable for someone new to the ASF and their project.
diff --git a/source/gsoc/gsoc-admin-tasks.md b/source/gsoc/gsoc-admin-tasks.md
index d7ee52b..729c61e 100644
--- a/source/gsoc/gsoc-admin-tasks.md
+++ b/source/gsoc/gsoc-admin-tasks.md
@@ -7,9 +7,9 @@ A comprehensive guide to being a GSoC admin for the ASF
List of duties:
1. Make sure the ASF has an extensive list of project ideas ready shortly after Google announces the
-program (around the end of January). Projects must create JIRA issues for their ideas and
-label them with `gsoc<year>;` and `mentor`. If a project doesn't use JIRA, have them create the ideas in the COMDEV
-JIRA project. Create a JIRA filter for these ideas to use in the application (see next). Have
+program (around the end of January). Projects must create Jira issues for their ideas and
+label them with `gsoc<year>;` and `mentor`. If a project doesn't use Jira, have them create the ideas in the GSOC
+Jira project. Create a Jira filter for these ideas to use in the application (see next). Have
prospective mentors subscribe to `mentors@community.apache.org`. The following is an email sent to `pmcs@a.o`
explaining the procedures to them:
@@ -22,7 +22,7 @@ contributors to your projects.
If you want to participate with your project you now need to
- understand what it means to be a mentor [1]
- - propose your project ideas. Just label your issues with gsoc2023 in JIRA and
+ - propose your project ideas. Just label your issues with gsoc2023 in Jira and
they will show up at [2]. See also [1].
- subscribe to mentors@community.apache.org (restricted to potential mentors, meant to be used
as a private list - general discussions on the public
diff --git a/source/gsoc/guide-to-being-a-mentor.md b/source/gsoc/guide-to-being-a-mentor.md
index c92d5ff..1abe6db 100644
--- a/source/gsoc/guide-to-being-a-mentor.md
+++ b/source/gsoc/guide-to-being-a-mentor.md
@@ -11,12 +11,12 @@ Note: This document is bout GSoC, not about a generic Mentoring Program.
We invite all ASF projects to submit their ideas for consideration in the
ASF mentoring programme. Any Apache member and experienced committers can
-submit ideas via JIRA (if your project does not use JIRA you can [use the Comdev Issue Tracker For GSoC Tasks](use-the-comdev-issue-tracker-for-gsoc-tasks.html). We are looking for as many interesting projects as we can come up with.
+submit ideas via Jira (if your project does not use Jira you can [use the Comdev Issue Tracker For GSoC Tasks](use-the-comdev-issue-tracker-for-gsoc-tasks.html). We are looking for as many interesting projects as we can come up with.
<a name="guidetobeingamentor-Summary"></a>
## Important Steps
-* Add an issue to JIRA (if your project does not use JIRA you can [use the Comdev GSoC Issue Tracker For GSoC Tasks](use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html)
+* Add an issue to Jira (if your project does not use Jira you can [use the Comdev GSoC Issue Tracker For GSoC Tasks](use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html)
* Add sub-tasks if necessary
* Label the main issue with "*mentor*" (these will show up at the [ASF-wide list of issues](https://issues.apache.org/jira/issues?jql=labels%20in%20(gsoc2023)%20AND%20labels%20in%20(mentor,%20Mentor)))
* Label the main issue with "*gsoc2023*" if appropriate (these will show up at [GSoC 2023 Ideas](https://s.apache.org/gsoc2023ideas))
@@ -33,7 +33,7 @@ Please NOTE Ideas list is manually updated by GSoC admins, please ping mentors (
<a name="guidetobeingamentor-Detail"></a>
## Details
-To ensure we include your JIRA issues in our list of mentored projects,
+To ensure we include your Jira issues in our list of mentored projects,
please add the label "mentor" to the issue. If you want it to be included
in the Google Summer of Code lists also add the "gsoc" label. If you want
to include a number of issues in a single mentored project, please create a
diff --git a/source/newcommitter.md b/source/newcommitter.md
index f062fe9..d87c076 100644
--- a/source/newcommitter.md
+++ b/source/newcommitter.md
@@ -16,7 +16,7 @@ drafts for the various communications that are necessary.
## Guidelines for assessing new candidates for committership
When voting, all PMC members need to make up their own minds as to whether a candidate
-should be approved to become a committer. They might search mailing lists and JIRA to see
+should be approved to become a committer. They might search mailing lists and Jira to see
how the candidate interacts with others, and the contributions (code or doc patches, suggestions, engagement in conversation) they have made.
All new committers **must** adhere to the [Apache Code of Conduct](https://www.apache.org/foundation/policies/conduct.html).
@@ -89,7 +89,7 @@ Use the Whimsy tool to update the roster via https://whimsy.apache.org/roster/co
1. Wait until root says it is done
1. PMC Chair updates LDAP group membership which enables svn, gitbox and other access.
If the committer uses GitHub, they are responsible for linking it to their ASF account.
- 1. Add committer to the appropriate groups in JIRA and CWiki
+ 1. Add committer to the appropriate groups in Jira and CWiki
1. Notify the committer of completion (template/committerDone.txt)
1. If committer is also to be a PMC member, PMC Chair sends email to board@ asking for acknowledgement of new PMC member
(templates/email-member-ack.txt)