Last updated September 3, 2016.
What is core mentoring?
Drupal core mentors inspire, enable, and encourage new core contributors. They also work on the core tools, process, and community to make it easier for new contributors to get involved.
Staying in contact with mentors
- Follow @drupalmentoring for reminders of office hour times and other mentoring events.
- Join mentoring group for people who do: following post related to IRC core mentoring office hours, mentor at sprints, self-identify as mentors or are interested in the general principles of mentoring in the Drupal community
Mentor issues, tag, queues
- The mentoring meta issue tracks improvements we are making to mentoring.
- We have an tag Core mentoring on d.o
- And an issue queue for things mentors want to do (not for tracking tasks for mentoring participants).
Tasks for mentoring participants
See the child pages, especially:
We hold the Drupal core contribution mentoring ("office hours") each week in #drupal on freenode:
- First Wednesday of each month, 16:00 - 18:00 UTC (what time is that for me?)
Core contribution mentoring calendar #
Subscribe to iCalendar feed. Paste this URL in your calendar app:
https://www.google.com/calendar/ical/7ss54o2foktlc8b75d1gest4do%40group.calendar.google.com/public/basic.ics to subscribe. Downloading this file is not the same as subscribing (calendar will not automatically update when events are added).
Add to Google Calendar: paste this string:
email@example.com into the "Add a friend's calendar" field in the Other Calendars section.
During core contribution mentoring hours, IRC channel topic usually reflects participating mentors. If that does not happen, or you are not sure whom to ask, look for the following mentors (listed in alphabetic order):
Core mentors facilitate new contributor workshops and mentored sprints at every DrupalCon and at many Drupal Camps. Check out Mentored Core Sprints. for more information.
Why contribution mentoring?
Core contribution mentoring addresses two complementary issues:
- The Drupal core issue queue contains a large number of unresolved issues, and we need the help of more volunteers to address these issues efficiently. While all Drupal users rely on Drupal core, only a fraction participate in the core issue queue. New contributors bring fresh energy and a diversity of perspectives, and can both reduce the burden on longtime contributors and improve the experience of all Drupal.org users who file or follow core issues.
- Contributing to Drupal core can seem unapproachable, both because there are so many issues and because the process for resolving core issues is more rigorous and involved than it is for contributed modules or smaller open source projects. It can be difficult to know where and how to start contributing, or what it will take to get a specific issue fixed.
How will core mentoring help?
Benefits for new and potential contributors
If you've been wanting to get involved in Drupal core development, but aren't sure where to start, come to the office hours. You will find experienced contributors who will help you to find something to work on.
If you have patches or bug reports against Drupal core, and want to get your patch reviewed or figure out where to take the issue next, this should be a good time of the week to trade reviews on IRC.
Benefits for mentors
Mentors find a new rewarding interaction with the issue queue, and learn new skills along with new contributors. Mentoring gives contributors the opportunity to both scale their contributions manyfold.
Benefits for the Drupal community
New contributors are essential to the health of the project. Involving new contributors in a structured way enriches core development, helps reduce miscommunications in the issue queue, and gives would-be contributors a chance to familiarize themselves with core contribution before they tackle deeper topics.
Things we will do
Office hours are for both experienced contributors and developers as well as newcomers, expect some of the following:
- Triaging the core queue - understanding status, priority of issues, closing duplicates etc.
- Co-writing issue summaries.
- Co-writing change notifications for needs work issues tagged with "Needs change notification".
- Writing tests for bug reports that don't have them.
- Swapping patch reviews.
- and more... new contributor tasks
To help mentor, just attend the office hours and say: "I want to help".
See the original proposal for historical discussion.