uuid:
  - value: 2492a986-0932-437a-a7b4-414dbebb4a2a
langcode:
  - value: en
type:
  - target_id: daily_email
    target_type: node_type
    target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
revision_timestamp:
  - value: '2025-05-11T09:00:55+00:00'
revision_uid:
  - target_type: user
    target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
revision_log: {  }
status:
  - value: true
uid:
  - target_type: user
    target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
title:
  - value: 'Being a Drupal contribution mentor'
created:
  - value: '2022-09-21T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:55+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2022/09/21/being-drupal-contribution-mentor
    langcode: en
body:
  - value: |
      <p>This week is DrupalCon Prague, and although I'm not at this event, I'd like to write about some my experiences at DrupalCon - in particular about being a contribution mentor.</p>

      <h2 id="my-first-drupalcon">My first DrupalCon</h2>

      <p>The first DrupalCon that I attended was in 2013, also in Prague.</p>

      <p>I was enjoying the session days when I stopped at the mentoring table to find out more about the contribution sprints that were happening on the Friday.</p>

      <p>I didn't have any commits in Drupal core but had already worked on and released some of my own contributed modules, so I was familiar with the tools and the Drupal.org contribution workflow. In short, I was signed up to be a mentor during the sprints.</p>

      <p>I remember being involved in the preparation too, sitting in a hotel lobby, identifying potential issues for new contributors to work on, alongside people who I'd previously interacted with in the issue queues on Drupal.org.</p>

      <p>On the day, I helped new contributors get their local environments up and running, select issues to work on, and perform tasks like creating and re-rolling patch files and submitting them for review.</p>

      <p>One of my highlights at the end of the day was the live commit, when a patch that a new contributor had worked on that day was committed to Drupal core live on stage!</p>

      <p>Whenever I've attended DrupalCon events since, I've always volunteered to be a contribution mentor, as well as mentoring and organising sprints at other Drupal events.</p>

      <h2 id="the-five-year-issue">The Five Year Issue</h2>

      <p>One of the most memorable times mentoring was whilst working with a group of contributors at DrupalCon in May 2015.</p>

      <p>Someone was working on a Drupal core issue that was very similar to <a href="https://www.drupal.org/project/drupal/issues/753898">one that I'd looked at</a> a few years before.</p>

      <p>We focused on the original issue that I'd commented on, reviewed, tested, and re-rolled the patch, fixed a failing test, and marked it as "reviewed and tested by the community".</p>

      <p>A few days after the conference, and just over five years after my original comment, the patch was committed - giving my contributors their first commits to Drupal 8 core, and also <a href="https://git.drupalcode.org/project/drupal/-/commits/9.5.x?search=opdavies">one of mine</a>.</p>

              
    format: full_html
    processed: |
      <p>This week is DrupalCon Prague, and although I'm not at this event, I'd like to write about some my experiences at DrupalCon - in particular about being a contribution mentor.</p>

      <h2 id="my-first-drupalcon">My first DrupalCon</h2>

      <p>The first DrupalCon that I attended was in 2013, also in Prague.</p>

      <p>I was enjoying the session days when I stopped at the mentoring table to find out more about the contribution sprints that were happening on the Friday.</p>

      <p>I didn't have any commits in Drupal core but had already worked on and released some of my own contributed modules, so I was familiar with the tools and the Drupal.org contribution workflow. In short, I was signed up to be a mentor during the sprints.</p>

      <p>I remember being involved in the preparation too, sitting in a hotel lobby, identifying potential issues for new contributors to work on, alongside people who I'd previously interacted with in the issue queues on Drupal.org.</p>

      <p>On the day, I helped new contributors get their local environments up and running, select issues to work on, and perform tasks like creating and re-rolling patch files and submitting them for review.</p>

      <p>One of my highlights at the end of the day was the live commit, when a patch that a new contributor had worked on that day was committed to Drupal core live on stage!</p>

      <p>Whenever I've attended DrupalCon events since, I've always volunteered to be a contribution mentor, as well as mentoring and organising sprints at other Drupal events.</p>

      <h2 id="the-five-year-issue">The Five Year Issue</h2>

      <p>One of the most memorable times mentoring was whilst working with a group of contributors at DrupalCon in May 2015.</p>

      <p>Someone was working on a Drupal core issue that was very similar to <a href="https://www.drupal.org/project/drupal/issues/753898">one that I'd looked at</a> a few years before.</p>

      <p>We focused on the original issue that I'd commented on, reviewed, tested, and re-rolled the patch, fixed a failing test, and marked it as "reviewed and tested by the community".</p>

      <p>A few days after the conference, and just over five years after my original comment, the patch was committed - giving my contributors their first commits to Drupal 8 core, and also <a href="https://git.drupalcode.org/project/drupal/-/commits/9.5.x?search=opdavies">one of mine</a>.</p>

              
    summary: null
field_daily_email_cta: {  }