Problem/Motivation

Some of #2457875: [policy] Evolving and documenting Drupal core's structure, responsibilities, and decision-making relates to maintainers.txt. But does not address the Core Mentoring Initiative and Leads.

http://cgit.drupalcode.org/drupal/tree/core/MAINTAINERS.txt?h=8.0.x#n473

At the April Mentoring Meta Meeting (https://groups.drupal.org/node/460608)
we discussed updating the mentor lead section of maintainers.txt, and it came up that it would help to better document the tasks mentoring leads do.

Proposed resolution

Documenting Drupal Core Mentoring lead responsibilities, in the style used in #2457875: [policy] Evolving and documenting Drupal core's structure, responsibilities, and decision-making

Remaining tasks

  • (done) wait a couple days for some feedback from the mentoring meeting
  • (done)draft up something in a google doc Mentoring Leads
  • (done) organize the doc (maybe into sections: skills and tasks/responsibilities
  • (done) get feedback
  • (done) copy a draft here

User interface changes

N/A

API changes

N/A

Draft

The Drupal Core mentors inspire, enable, and encourage new core contributors.
See https://www.drupal.org/core-mentoring for more information about mentoring.

Drupal Core mentoring coordinators do mentoring strategy, mentor recruitment, and mentor-mentoring. They work on contributor tools, documentation, and process, to make it easier for new contributors to get involved. They organize communications and logistics. And, they actively participate as a mentor.

Drupal Core mentoring coordinators are responsible for:

  • Organizing IRC mentoring office hours.
  • Organizing mentoring at DrupalCons.
  • Communicating the principles of mentoring.
  • Responding to inquiries about mentoring to local organizers.
  • Being available to other mentors.

Current Membership

The canonical list of the coordinators can be found in MAINTAINERS.txt in the Drupal core source code.

Provisional Membership

None at this time.

Tasks

Mentoring strategy, mentor recruitment, and mentor-mentoring

  • Recruit mentors
  • Mentor mentors (for IRC, GSW, camps, cons, sprint leads, etc.)
  • Strategy for integrating mentoring with core priorities, processes, and release management
  • Facilitating/supporting the transition from novice to regular contributor, and enabling/empowering/supporting regular contributors
  • investigate/contact for official mentoring inside companies
  • thoughtful about messaging in terms of diversity, paid/unpaid, access,
  • advice and strategy for docs, posts, presentations, tools
  • mentoring meta meeting: schedule, announce, run, take notes
  • core conversations, camp sessions, etc. about mentoring (this is also communications I guess)
  • drafting stuff like this document. ;)

Contributor tools, documentation, and process facilitation/administration

  • Contributor task document maintenance
  • Core handbook maintenance
  • Dreditor maintenance
  • Testbot administration
  • IRC channel administration
  • mentorbot administration

Contributor process, documentation, and tool improvements

  • Process improvements
  • mentoring-related d.o issues

Communications

Logistics

  • DrupalCon planning and organization (spreadsheet, signups, webpages, DA liaison, booth, drupalcon workshop) https://drupal.org/node/2232047
  • Global Sprint Weekend planning
  • IRC mentor signups

Active participation as a mentor

  • Regular IRC mentoring
  • In-person mentoring at camps and/or cons
  • Core mentoring workshop
  • Global Sprint Weekend mentoring
  • Triaging novice issues
  • Reviews in issues
  • Identifying contributor tasks in issues

Comments

YesCT’s picture

Issue summary: View changes
YesCT’s picture

Issue summary: View changes

google doc: https://docs.google.com/document/d/1N0vDZwpoKb2LhWJ6-rMKIknFfEJBS7uUSP1m...

updated remaining tasks in issue summary

YesCT’s picture

Issue summary: View changes

I went through it a bit. copying from the doc into the summary.

YesCT’s picture

also made a handbook page, cause I dont think we want all those tasks listed in the governance or maintainers.txt

https://www.drupal.org/core-mentoring/mentoring-coordinator

YesCT’s picture

I dont know if we should open an issue in https://www.drupal.org/project/governance
to add something to https://www.drupal.org/governance/core

davidhernandez’s picture

You want a separate H2 on that page? "What does it mean to be a mentoring coordinator?"

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Project: Drupal core » Mentoring
Version: 9.5.x-dev »
Component: documentation » Documentation

I asked out this issue in #mentoring. volkswagenchick immediately thought it was outdated but then later suggested it could be moved to the mentoring project. I am not confident to close this so I will move to the mentoring project.

Cheers.