Goal: 
New Core mentoring Coordinators help us to sustain development of the project by coordinating efforts to mentor new contributors. This task describes the process by which we achieve that.
Skills required: 
Mentoring
Wrangling volunteers
Background and reference information: 
Contribute by Mentoring
Detailed steps: 
  1. After acting as a mentoring event coordinator for a DrupalCon or similar-sized event, create a Drupal Core issue asking to be added to the MAINTAINERS.txt file as a Mentoring Coordinator.

  2. Volunteer is invited to become a core mentoring coordinator

  3. Issue is raised in the issue queue, where the invitation is accepted by the volunteer with the following steps:

    1. Accept role as defined in MAINTAINERS.txt: "Mentoring coordinators recruit and coach other mentors. They work on contributor tools, documentation, and processes to make it easier for new contributors to get involved. They organize communications and logistics, and actively participate in mentoring."

    2. Accept role as general maintainer as described in core governance: https://www.drupal.org/contribute/core/maintainers#maintainer-definition
      The acceptance text would normally include "I confirm that I accept the role as described in MAINTAINERS.txt, and the general role of a maintainer as covered in the core governance."

    3. Patch is made to MAINTANERS.txt by provisional core mentor to include a new line in the 'Core mentoring coordinators' with '(provisional) ' followed by their name and D.O. username and D.O. account path.

  4. After a period of 6-12 months there will be a review of the provisional mentors to see if they will continue with the role and move out of the provisional status.

    1. If the current mentoring coordinators are happy to offer to add the provisional mentoring coordinator to the full list, they approach the provisional mentoring coordinator and offer to make the change

    2. If the provisional mentoring coordinator accepts, a representative of the mentoring coordinators makes an issue requesting "(provisional)" to be removed. A reference is made to the original issue that made them a provisional mentoring coordinator.
      The issue should contain the same invitation to accept 

    3. The provisional mentoring coordinator submits a comment, repeating the invitation to accept the role as defined in MAINTAINERS.txt
      The acceptance text should normally include "I confirm that I accept the role as described in MAINTAINERS.txt, and the general role of a maintainer as covered in the core governance."

    4. Patch is made to MAINTANERS.txt by provisional core mentor to remove '(provisional)' from the line for the Mentoring Coordinator in question.

    5. Mentoring coordinators indicate their approval on the issue and set it to RTBC for addition to the Drupal core.