This is an automated email from the ASF dual-hosted git repository.
sebb pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/comdev-site.git
The following commit(s) were added to refs/heads/main by this push:
new b4e87f41 Use span instead of 'a' for local anchors
b4e87f41 is described below
commit b4e87f41df317bbc7720047d4a3e132d04ce7ee0
Author: Sebb <[email protected]>
AuthorDate: Tue Dec 2 15:09:51 2025 +0000
Use span instead of 'a' for local anchors
---
source/_index.md | 2 +-
source/committers/_index.md | 2 +-
source/contactpoints.md | 10 +++++-----
source/gsoc/_index.md | 22 +++++++++++-----------
source/gsoc/guide-to-being-a-mentor.md | 16 ++++++++--------
source/gsoc/mentee-ranking-process.md | 12 ++++++------
source/history/mentoringprogramme-icfoss-pilot.md | 8 ++++----
source/newbiefaq.md | 18 +++++++++---------
source/newcomers/_index.md | 2 +-
source/newcommitter.md | 20 ++++++++++----------
source/newpmcmember.md | 8 ++++----
source/pmc/adding-committers.md | 20 ++++++++++----------
source/pmc/adding-pmc-members.md | 8 ++++----
13 files changed, 74 insertions(+), 74 deletions(-)
diff --git a/source/_index.md b/source/_index.md
index fc2c66eb..0dcec03b 100644
--- a/source/_index.md
+++ b/source/_index.md
@@ -21,7 +21,7 @@ processes, and advice to help open-source projects improve
their own
community health.
</div>
-<a name="Index-Startingpoints"></a>
+<span id="Index-Startingpoints"></span>
<community-front-page>
diff --git a/source/committers/_index.md b/source/committers/_index.md
index 006c8b24..8611ff77 100755
--- a/source/committers/_index.md
+++ b/source/committers/_index.md
@@ -41,7 +41,7 @@ opportunity to contribute to and benefit from our software,
regardless
of motivation or financial objectives. There is more discussion of this
principle
in our document [Project Independence][12].
-<a name="Index-Assistingwithprojectmanagement"></a>
+<span id="Index-Assistingwithprojectmanagement"></span>
## Development processes
diff --git a/source/contactpoints.md b/source/contactpoints.md
index c4879a70..b89d0a2f 100644
--- a/source/contactpoints.md
+++ b/source/contactpoints.md
@@ -28,7 +28,7 @@ the project.
Most of the below mailing lists are privately archived: you can mail to them,
and
we'll answer, but you won't be able to read the archives.
-<a name="ContactPoints-Trademarks"></a>
+<span id="ContactPoints-Trademarks"></span>
## Trademarks
@@ -37,7 +37,7 @@ ASF and any projects: see our [Trademark Site
Map](//www.apache.org/foundation/m
or [Contact the Trademarks team](https://apache.org/foundation/marks/contact).
-<a name="ContactPoints-PublicityandMarketing"></a>
+<span id="ContactPoints-PublicityandMarketing"></span>
## Publicity and Marketing
@@ -45,7 +45,7 @@ Issues dealing with publicity, marketing, or any inquires
from the
press or analysts: see our [Press Team Page](https://www.apache.org/press/),
or [Contact the Press team](https://www.apache.org/press/#contact-us).
-<a name="ContactPoints-FundraisingandSponsorship"></a>
+<span id="ContactPoints-FundraisingandSponsorship"></span>
## Fundraising and Sponsorship
@@ -53,7 +53,7 @@ Questions about fundraising, sponsorships, donations, or
related
finances: see our [Donations
Information](//www.apache.org/foundation/contributing.html),
or email to [[email protected]](mailto:[email protected]).
-<a name="ContactPoints-Legal"></a>
+<span id="ContactPoints-Legal"></span>
### Legal
@@ -68,7 +68,7 @@ response from the ASF's legal counsel, then email this
private list:
If you have **general** questions about licensing or Apache projects, then
please
use our [public legal-discuss@ mailing
list](https://apache.org/foundation/mailinglists.html#foundation-legal).
-<a name="ContactPoints-Other"></a>
+<span id="ContactPoints-Other"></span>
### Other
diff --git a/source/gsoc/_index.md b/source/gsoc/_index.md
index 66e79105..28ea6386 100644
--- a/source/gsoc/_index.md
+++ b/source/gsoc/_index.md
@@ -17,12 +17,12 @@ Google is sponsoring the [{{< current_year >}} Summer of
Code](https://summerofc
This page is your entry point to the ASF GSoC program.
Please watch this page for updates concerning our participation in {{<
current_year >}}.
-<a name="GSoC-Mentors:readthis"></a>
+<span id="GSoC-Mentors:readthis"></span>
# Mentors: read this
Navigate to the [mentor documentation](./guide-to-being-a-mentor.html).
-<a name="GSoC-Students:readthis"></a>
+<span id="GSoC-Students:readthis"></span>
# Students: read this
* Learn [about GSoC](https://summerofcode.withgoogle.com/about/)
@@ -38,7 +38,7 @@ to the projects you are interested in.<br/>
Or simply use this link
https://issues.apache.org/jira/issues/?jql=labels+%3D+gsoc{{< current_year >}}
* If you do not see any interesting projects from the proposed ideas, we
encourage you to contact one of the Apache Project's mailing list and propose a
new idea. But these ideas have to be vetted on the project dev list. The ASF
does not encourage and will not respond to your personal new open source
project ideas which are unrelated to any Apache projects.
-<a name="GSoC-ApplyingforGSoC"></a>
+<span id="GSoC-ApplyingforGSoC"></span>
### Applying for GSoC
Details are announced now and we are in the project discussion phase. We
encourage you to discuss you application with the project community.
@@ -117,7 +117,7 @@ _Include any planned user testing, prototypes, code review._
-<a name="GSoC-ContactingtheASF"></a>
+<span id="GSoC-ContactingtheASF"></span>
## Contacting the ASF
The ASF is not just one project, it is a federation of projects, see the
@@ -131,14 +131,14 @@ engage with that project community.
Please contact [email protected] if you have questions/difficulties.
-<a name="GSoC-ASFGSoCTimeline"></a>
+<span id="GSoC-ASFGSoCTimeline"></span>
# ASF GSoC {{< current_year >}} Timeline
Below is a timeline of events for The Apache Software Foundation's
involvement in GSoC. Unless otherwise stated deadlines are 24:00 UTC on the
date indicated.
-<a name="GSoC-StudentApplicationandSelection"></a>
+<span id="GSoC-StudentApplicationandSelection"></span>
## Student Application and Selection
- 2025-02-27: Potential GSoC contributors discuss application ideas with
mentoring organizations
@@ -149,7 +149,7 @@ date indicated.
- 2025-04-25: Proposal scoring must be completed. Proposals without a score
will be rejected, no exceptions.
- 2025-05-08: Accepted student proposals announced on the Google Summer of
Code site.
-<a name="GSoC-GSoCisunderway"></a>
+<span id="GSoC-GSoCisunderway"></span>
## GSoC is underway
- 2025-05-08: Community bonding start
@@ -158,7 +158,7 @@ date indicated.
- 2025-07-14: Mentors and GSoC contributors can begin submitting Phase 1
evaluations
- 2025-07-18: Phase 1 Evaluation deadline (standard coding period)
-<a name="GSoC-Winddown"></a>
+<span id="GSoC-Winddown"></span>
## Wind down
- 2025-09-01: GSoC contributors submit their final work product and their
final mentor evaluation (standard coding
@@ -166,18 +166,18 @@ date indicated.
- 2025-09-01: ASF Mentors evaluations can be submitted
- 2025-09-08: ASF Mentors final evaluations deadline
-<a name="GSoC-Extended"></a>
+<span id="GSoC-Extended"></span>
## Extended coding period
- 2025-11-09: GSoC contributors with extended timelines continue coding
- 2025-11-10: Final date for all GSoC contributors to submit their final
work product and final evaluation
- 2025-11-17: Final date for mentors to submit evaluations for GSoC
contributor projects with extended deadlines
-<a name="GSoC-Vouching"></a>
+<span id="GSoC-Vouching"></span>
# Organization Vouching
The ASF currently has no policy establishing the criteria on what basis to
vouch for another organization. Until one is established the ASF therefore
doesn't vouch for any organization.
-<a name="GSoC-UsefulLinks"></a>
+<span id="GSoC-UsefulLinks"></span>
# Useful Links
* [Summer of Code home](https://summerofcode.withgoogle.com)
diff --git a/source/gsoc/guide-to-being-a-mentor.md
b/source/gsoc/guide-to-being-a-mentor.md
index a22add1d..8af4444a 100644
--- a/source/gsoc/guide-to-being-a-mentor.md
+++ b/source/gsoc/guide-to-being-a-mentor.md
@@ -6,14 +6,14 @@ title: guide to being a mentor
Note: This document is bout GSoC, not about a generic Mentoring Program.
-->
-<a name="guidetobeingamentor-Submittingideastothementoringprogramme"></a>
+<span id="guidetobeingamentor-Submittingideastothementoringprogramme"></span>
# Submitting ideas to the mentoring programme
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 GSoC Issue Tracker For GSoC
Tasks](use-the-comdev-gsoc-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>
+<span id="guidetobeingamentor-Summary"></span>
## 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)
@@ -31,7 +31,7 @@ submit ideas via Jira (if your project does not use Jira you
can [use the Comdev
Please NOTE Ideas list is manually updated by GSoC admins, please ping mentors
(at) community.apache.org if the page is not being updated .. :))
-<a name="guidetobeingamentor-Detail"></a>
+<span id="guidetobeingamentor-Detail"></span>
## Details
To ensure we include your Jira issues in our list of mentored projects,
@@ -60,7 +60,7 @@ those project will automatically go ahead. Depending on the
number of
projects; the number of people able to mentor, and the timing we will
probably have to make a smaller selection.
-<a name="guidetobeingamentor-Publicisingyourmentoredissues"></a>
+<span id="guidetobeingamentor-Publicisingyourmentoredissues"></span>
### Publicising your mentored issues
You can link to the [ASF wide list of
issues](https://issues.apache.org/jira/secure/IssueNavigator.jspa?requestId=12315361)
@@ -74,14 +74,14 @@ out.
If you have any cool ideas for using this data, let us know so we can
share them with other projects (mail `[email protected]`).
-<a name="guidetobeingamentor-Examples"></a>
+<span id="guidetobeingamentor-Examples"></span>
## Examples
- [Wookie GSoC
Issues](https://issues.apache.org/jira/secure/IssueNavigator.jspa?requestId=12315360)
- [Wookie RSS GSoC
feed](https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-rss/12315360/SearchRequest-12315360.xml?tempMax=1000)
- [Wookie XML GSoC
feed](https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12315360/SearchRequest-12315360.xml?tempMax=1000)
-<a name="guidetobeingamentor-Stayingintouch"></a>
+<span id="guidetobeingamentor-Stayingintouch"></span>
# Staying in touch
All mentors/prospective mentors **must** subscribe to
`[email protected]`, our list for
@@ -106,7 +106,7 @@ subscribe to `[email protected]`.
If you are planning on mentoring as part of the GSoC programme you also
need to register with Google. See our [GSoC](/gsoc/) page for more information.
-<a name="guidetobeingamentor-Howmucheffortisinvolvedwithbeingamentor"></a>
+<span id="guidetobeingamentor-Howmucheffortisinvolvedwithbeingamentor"></span>
## How much effort is involved with being a mentor?
Most mentors spend between three and five hours per week with their students.
Most
@@ -120,7 +120,7 @@ student and helping them deliver on their commitments.
The [GSoC Mentoring
Guide](https://developers.google.com/open-source/gsoc/resources/guide#mentor_guide)
has plenty of useful materials for mentors.
-<a name="guidetobeingamentor-Anoteabouteligibility"></a>
+<span id="guidetobeingamentor-Anoteabouteligibility"></span>
## A note about eligibility
If your project has any restrictions on who can participate (as is the case
diff --git a/source/gsoc/mentee-ranking-process.md
b/source/gsoc/mentee-ranking-process.md
index 680a9139..bc2c48cf 100644
--- a/source/gsoc/mentee-ranking-process.md
+++ b/source/gsoc/mentee-ranking-process.md
@@ -19,7 +19,7 @@ as a potential mentor (you don't actually have to _become_ a
mentor).
The instructions below described ranking proposals using the Google Summer
of Code application.
-<a name="MenteeRankingProcess-ScoringSystem"></a>
+<span id="MenteeRankingProcess-ScoringSystem"></span>
# Scoring System
We rank projects using this scoring system:
@@ -116,7 +116,7 @@ The admins transfer the scores to Melange.
At the end of this phase there is a short window for the community to
verify the admins' work before the final selection is made.
-<a name="MenteeRankingProcess-Whatarewelookingforinagoodproposal?"></a>
+<span id="MenteeRankingProcess-Whatarewelookingforinagoodproposal?"></span>
# What are we looking for in a good proposal?
In general we much prefer new mentees to repeat mentees. The goal is to
@@ -131,7 +131,7 @@ requests for more info)
* Acknowledgment of weaknesses in existing skill set and a plan for
addressing those weaknesses
-<a name="MenteeRankingProcess-Warningsignsinabadproposal"></a>
+<span id="MenteeRankingProcess-Warningsignsinabadproposal"></span>
# Warning signs in a bad proposal
* No engagement with project community
@@ -139,7 +139,7 @@ addressing those weaknesses
* Indication of external commitments (exams, job etc.)
* Previous failures within the mentor programme
-<a name="MenteeRankingProcess-Whathappensnext?"></a>
+<span id="MenteeRankingProcess-Whathappensnext?"></span>
# What happens next?
Towards the end of the ranking period Google announces how many slots
@@ -185,7 +185,7 @@ cut-off point may move as well, so Google may give us one
extra slot. So we
need to ensure that all rank-7 projects are correctly ordered, not just the
best.
-<a name="MenteeRankingProcess-Theprocessofbreakingclusters"></a>
+<span id="MenteeRankingProcess-Theprocessofbreakingclusters"></span>
## The process of breaking clusters
Admins work through all applications, adding a +8 to all those ranked above
@@ -203,7 +203,7 @@ score for this one (i.e. to try to spread the love).
It's not practical to ask the community to comment at this point as we are
on a tight deadline. We ask that the community trust the assigned admins.
-<a name="MenteeRankingProcess-Resolveconflicts"></a>
+<span id="MenteeRankingProcess-Resolveconflicts"></span>
# Resolve conflicts
Inevitably there will be one or two students who have been accepted in
diff --git a/source/history/mentoringprogramme-icfoss-pilot.md
b/source/history/mentoringprogramme-icfoss-pilot.md
index 4b449749..2f716477 100644
--- a/source/history/mentoringprogramme-icfoss-pilot.md
+++ b/source/history/mentoringprogramme-icfoss-pilot.md
@@ -20,7 +20,7 @@ will provide enough information for you to progress within
the project. You
need to bring the confidence to take their guidance and discover the detail
for yourself.
-<a name="Schedule"></a>
+<span id="Schedule"></span>
## Proposed Schedule
| Date | Description |
@@ -38,13 +38,13 @@ for yourself.
| October 28 | Mentors and students can begin submitting final evaluations |
| November 1 | Final evaluation deadline |
-<a name="MentoringProgramme-WorkshopMaterials"></a>
+<span id="MentoringProgramme-WorkshopMaterials"></span>
## Workshop Materials
The slides used for the local workshop at ICFOSS headquarters in Kerala are
available for
[download](https://people.apache.org/~lresende/presentations/asf-icfoss-mentoring.pdf).
-<a name="MentoringProgramme-ProjectIdeas"></a>
+<span id="MentoringProgramme-ProjectIdeas"></span>
## Project Ideas
Project ideas are jira created by possible mentors and can be viewed at:
@@ -54,7 +54,7 @@ Project ideas are jira created by possible mentors and can be
viewed at:
+ [2013 GSoC Project Ideas](https://s.apache.org/gsoc2013ideas)
-<a name="MentoringProgramme-ApplyingfortheMentorProgramme"></a>
+<span id="MentoringProgramme-ApplyingfortheMentorProgramme"></span>
## Applying for the Mentor Programme
Students can propose their own project ideas, or select one from the ASF
provided list. After selecting the project ideas. students should create a
project proposal following guidance from the **mentor** and the **project
community**.
diff --git a/source/newbiefaq.md b/source/newbiefaq.md
index 195d918c..e091892f 100644
--- a/source/newbiefaq.md
+++ b/source/newbiefaq.md
@@ -27,10 +27,10 @@ the information they're looking for. Please ask questions
or give us suggestions
[[email protected]](mailto:[email protected])
first).
-<a name="NewbieFAQ-AboutTheApacheSoftwareFoundation"></a>
+<span id="NewbieFAQ-AboutTheApacheSoftwareFoundation"></span>
# About The Apache Software Foundation
-<a name="NewbieFAQ-WhatprojectscanIfindinTheApacheSoftwareFoundation?"></a>
+<span id="NewbieFAQ-WhatprojectscanIfindinTheApacheSoftwareFoundation?"></span>
## What projects can I find in The Apache Software Foundation?
There are over 350 separate projects and communities hosted at the Apache
Software Foundation. We have
@@ -44,7 +44,7 @@ have active development and are moving towards graduating to
become TLPs.
* [Attic](https://attic.apache.org): these are end-of-life projects that
are no longer receiving active
development, but may still be useful.
-<a name="NewbieFAQ-HowareprojectsmanagedinTheApacheSoftwareFoundation"></a>
+<span id="NewbieFAQ-HowareprojectsmanagedinTheApacheSoftwareFoundation"></span>
## How are projects managed in the Apache Software Foundation?
Apache project participants all believe that if we look after the community,
good
@@ -71,7 +71,7 @@ constructively within them!
To learn more about "The Apache Way" in general, see the [How it
Works](https://apache.org/foundation/how-it-works.html)
pages. We also have [detailed overviews of how the ASF and projects are
governed](https://www.apache.org/foundation/governance/).
-<a name="NewbieFAQ-HowdoIaskaquestionabouttheASFingeneral?"></a>
+<span id="NewbieFAQ-HowdoIaskaquestionabouttheASFingeneral?"></span>
## How do I ask a question about the ASF in general? ## {#generalquestion}
The Community Development Project is here for this very purpose. Check out
@@ -79,7 +79,7 @@ the resources on this site first. If you don't find the
answer to your question,
to `[email protected]` (subscribe first by sending an email to
`[email protected]`).
-<a name="NewbieFAQ-HowdoIgetusersupportforanASFproject?"></a>
+<span id="NewbieFAQ-HowdoIgetusersupportforanASFproject?"></span>
## How do I get user support for an ASF project?
Everyone active in ASF projects is here as a volunteer. You need to be
@@ -120,10 +120,10 @@ expertise grows. Again, earning merit in this way will
help you to get
the support you need in the future.
-<a name="NewbieFAQ-GettingInvolvedwithApacheprojects"></a>
+<span id="NewbieFAQ-GettingInvolvedwithApacheprojects"></span>
# Getting Involved with Apache projects
-<a name="NewbieFAQ-HowdoIchooseanApacheprojecttoworkon?"></a>
+<span id="NewbieFAQ-HowdoIchooseanApacheprojecttoworkon?"></span>
## How do I choose an Apache project to work on?
The key to working on projects at Apache (and any open source project, for that
@@ -142,7 +142,7 @@ inspiration about how you might be able to help the project
community. If
you see an issue you would like to tackle, it's time to join the project's
mailing list and get started.
-<a name="NewbieFAQ-HowdoIgetinvolvedwithanApacheproject?"></a>
+<span id="NewbieFAQ-HowdoIgetinvolvedwithanApacheproject?"></span>
## How do I get involved with an Apache project?
You can improve your programming skills by watching the `commit`
@@ -156,7 +156,7 @@ and be willing to research the rest.
To learn more about getting involved with an Apache Project, see our [getting
started guide][3]. You will also find our [get
involved](https://apache.org/foundation/getinvolved.html) page a useful
starting point.
-<a name="NewbieFAQ-IsthereaCodeofConductforApacheprojects?"></a>
+<span id="NewbieFAQ-IsthereaCodeofConductforApacheprojects?"></span>
## Is there a Code of Conduct for Apache projects?
Our code of conduct is posted at
diff --git a/source/newcomers/_index.md b/source/newcomers/_index.md
index 402f18b0..86553284 100644
--- a/source/newcomers/_index.md
+++ b/source/newcomers/_index.md
@@ -27,7 +27,7 @@ you stepping up to help out.
This is probably not the right page to send a newcomer to.
-->
-<a name="Index-FirstContributions"></a>
+<span id="Index-FirstContributions"></span>
# First Contributions
<!--
diff --git a/source/newcommitter.md b/source/newcommitter.md
index 49516e1c..65b9adea 100644
--- a/source/newcommitter.md
+++ b/source/newcommitter.md
@@ -20,7 +20,7 @@ The [Contributor
Ladder](https://community.apache.org/contributor-ladder.html) h
{{% toc %}}
-<a name="NewCommitter-Summary"></a>
+<span id="NewCommitter-Summary"></span>
## TL;DR - Inviting a new Committer
1. Discuss the proposed committer (and optionally PMC member). (Use
@@ -56,7 +56,7 @@ If they accept, then:
template](templates/committer-announce.txt).
-<a name="NewCommitter-Guidelinesforassessingnewcandidatesforcommittership"></a>
+<span
id="NewCommitter-Guidelinesforassessingnewcandidatesforcommittership"></span>
## Guidelines for assessing new candidates for committership
Each project must decide what is the correct measure for inviting a new
@@ -100,7 +100,7 @@ for general advice you might offer.
The following are some points to consider when assessing a candidate's
qualifications for committership.
-<a name="NewCommitter-Abilitytoworkco-operativelywithpeers."></a>
+<span id="NewCommitter-Abilitytoworkco-operativelywithpeers."></span>
### Ability to work cooperatively with peers.
How do we evaluate?
@@ -108,7 +108,7 @@ How do we evaluate?
- By how they respond to criticism.
- By how they participate in the group decision-making process.
-<a name="NewCommitter-Abilitytobeamentor."></a>
+<span id="NewCommitter-Abilitytobeamentor."></span>
### Ability to be a mentor.
How do we evaluate?
@@ -116,7 +116,7 @@ How do we evaluate?
- By how clear they are and how willing they are to identify or even create
appropriate background
materials.
-<a name="NewCommitter-Community"></a>
+<span id="NewCommitter-Community"></span>
### Community
How do we evaluate?
@@ -124,7 +124,7 @@ How do we evaluate?
- Do they help to answer questions raised on the mailing list; do they show
a helpful
attitude and respect for other people's ideas?
-<a name="NewCommitter-Committment"></a>
+<span id="NewCommitter-Committment"></span>
### Commitment
How do we evaluate?
@@ -132,7 +132,7 @@ How do we evaluate?
- By how well they stick with the process through tough issues.
- By how they help on not-so-fun tasks.
-<a name="NewCommitter-Personalskill/ability"></a>
+<span id="NewCommitter-Personalskill/ability"></span>
### Personal skill/ability
How do we evaluate?
@@ -140,14 +140,14 @@ How do we evaluate?
- Quality of discussion in email.
- Whether their patches (where applicable) are easy to apply with only a
cursory review.
-<a name="NewCommitter-NewCommitterProcess"></a>
+<span id="NewCommitter-NewCommitterProcess"></span>
## New Committer Process
This section describes a typical Apache project's process for handling the
vote to add a new committer. Templates mentioned in the process appear
later in this document.
-<a name="NewCommitter-Discussion"></a>
+<span id="NewCommitter-Discussion"></span>
### Discussion
We do the discussion and vote on the `private@` mailing list to enable a frank
@@ -242,7 +242,7 @@ send a new account request. Members may use [ASF New
Account Request](https://id
Please supply the [mail archives](https://lists.apache.org/) URL as
proof of the vote results.
-<a name="NewCommitter-EmailTemplates"></a>
+<span id="NewCommitter-EmailTemplates"></span>
## Email Templates
The following templates are recommended ways to phrase your email
diff --git a/source/newpmcmember.md b/source/newpmcmember.md
index eeae61ba..842f9c0f 100644
--- a/source/newpmcmember.md
+++ b/source/newpmcmember.md
@@ -17,7 +17,7 @@ explain different roles.
{{% toc %}}
-<a name="NewPMCMember-Summary"></a>
+<span id="NewPMCMember-Summary"></span>
## TL;DR - Inviting a new PMC member
1. Discuss the proposed PMC member. (Use [this
template](templates/pmc-member-discuss.txt).)
@@ -37,7 +37,7 @@ If they accept, then:
1. Announce the new PMC member. (Use [this
template](templates/pmc-member-announce.txt).)
-<a name="#NewPMCMemberGuidelines"></a>
+<span id="#NewPMCMemberGuidelines"></span>
## Guidelines for inviting a new PMC member
Frequently adding new PMC members to your project helps to ensure the
@@ -51,7 +51,7 @@ decision-making process would better serve your stakeholders,
and
contribute to the Foundation's mission of providing software for the
public good.
-<a name="NewPMCMember-Discussion"></a>
+<span id="NewPMCMember-Discussion"></span>
### Discussion
Any PMC member may propose a potential PMC member.
@@ -102,7 +102,7 @@ our praise and welcome messages in public.
Other notes about the process are available on the main [Apache
site](https://www.apache.org/dev/pmc.html#newpmcmember).
-<a name="NewPMCMember-EmailTemplates"></a>
+<span id="NewPMCMember-EmailTemplates"></span>
## Email Templates
* [PMC member vote](templates/pmc-member-vote.txt)
diff --git a/source/pmc/adding-committers.md b/source/pmc/adding-committers.md
index 82dd5684..498882f2 100644
--- a/source/pmc/adding-committers.md
+++ b/source/pmc/adding-committers.md
@@ -20,7 +20,7 @@ The [Contributor
Ladder](https://community.apache.org/contributor-ladder.html) h
{{% toc %}}
-<a name="NewCommitter-Summary"></a>
+<span id="NewCommitter-Summary"></span>
## TL;DR - Inviting a new Committer
1. Discuss the proposed committer (and optionally PMC member). (Use
@@ -58,7 +58,7 @@ If they accept, then:
template](/templates/committer-announce.txt).
-<a name="NewCommitter-Guidelinesforassessingnewcandidatesforcommittership"></a>
+<span
id="NewCommitter-Guidelinesforassessingnewcandidatesforcommittership"></span>
## Guidelines for assessing new candidates for committership
Each project must decide what is the correct measure for inviting a new
@@ -102,7 +102,7 @@ for general advice you might offer.
The following are some points to consider when assessing a candidate's
qualifications for committership.
-<a name="NewCommitter-Abilitytoworkco-operativelywithpeers."></a>
+<span id="NewCommitter-Abilitytoworkco-operativelywithpeers."></span>
### Ability to work cooperatively with peers.
How do we evaluate?
@@ -110,7 +110,7 @@ How do we evaluate?
- By how they respond to criticism.
- By how they participate in the group decision-making process.
-<a name="NewCommitter-Abilitytobeamentor."></a>
+<span id="NewCommitter-Abilitytobeamentor."></span>
### Ability to be a mentor.
How do we evaluate?
@@ -118,7 +118,7 @@ How do we evaluate?
- By how clear they are and how willing they are to identify or even create
appropriate background
materials.
-<a name="NewCommitter-Community"></a>
+<span id="NewCommitter-Community"></span>
### Community
How do we evaluate?
@@ -126,7 +126,7 @@ How do we evaluate?
- Do they help to answer questions raised on the mailing list; do they show
a helpful
attitude and respect for other people's ideas?
-<a name="NewCommitter-Committment"></a>
+<span id="NewCommitter-Committment"></span>
### Commitment
How do we evaluate?
@@ -134,7 +134,7 @@ How do we evaluate?
- By how well they stick with the process through tough issues.
- By how they help on not-so-fun tasks.
-<a name="NewCommitter-Personalskill/ability"></a>
+<span id="NewCommitter-Personalskill/ability"></span>
### Personal skill/ability
How do we evaluate?
@@ -142,14 +142,14 @@ How do we evaluate?
- Quality of discussion in email.
- Whether their patches (where applicable) are easy to apply with only a
cursory review.
-<a name="NewCommitter-NewCommitterProcess"></a>
+<span id="NewCommitter-NewCommitterProcess"></span>
## New Committer Process
This section describes a typical Apache project's process for handling the
vote to add a new committer. Templates mentioned in the process appear
later in this document.
-<a name="NewCommitter-Discussion"></a>
+<span id="NewCommitter-Discussion"></span>
### Discussion
We do the discussion and vote on the `private@` mailing list to enable a frank
@@ -247,7 +247,7 @@ send a new account request. Members may use [ASF New
Account Request](https://id
Please supply the [mail archives](https://lists.apache.org/) URL as
proof of the vote results.
-<a name="NewCommitter-EmailTemplates"></a>
+<span id="NewCommitter-EmailTemplates"></span>
## Email Templates
The following templates are recommended ways to phrase your email
diff --git a/source/pmc/adding-pmc-members.md b/source/pmc/adding-pmc-members.md
index ac0f1c75..620e1a30 100644
--- a/source/pmc/adding-pmc-members.md
+++ b/source/pmc/adding-pmc-members.md
@@ -17,7 +17,7 @@ explain different roles.
{{% toc %}}
-<a name="NewPMCMember-Summary"></a>
+<span id="NewPMCMember-Summary"></span>
## TL;DR - Inviting a new PMC member
1. Discuss the proposed PMC member. (Use [this
template](/templates/pmc-member-discuss.txt).)
@@ -37,7 +37,7 @@ If they accept, then:
1. Announce the new PMC member. (Use [this
template](/templates/pmc-member-announce.txt).)
-<a name="#NewPMCMemberGuidelines"></a>
+<span id="#NewPMCMemberGuidelines"></span>
## Guidelines for inviting a new PMC member
Frequently adding new PMC members to your project helps to ensure the
@@ -51,7 +51,7 @@ decision-making process would better serve your stakeholders,
and
contribute to the Foundation's mission of providing software for the
public good.
-<a name="NewPMCMember-Discussion"></a>
+<span id="NewPMCMember-Discussion"></span>
### Discussion
Any PMC member may propose a potential PMC member.
@@ -102,7 +102,7 @@ our praise and welcome messages in public.
Other notes about the process are available on the main [Apache
site](https://www.apache.org/dev/pmc.html#newpmcmember).
-<a name="NewPMCMember-EmailTemplates"></a>
+<span id="NewPMCMember-EmailTemplates"></span>
## Email Templates
* [PMC member vote](/templates/pmc-member-vote.txt)
