The Drupal Core Mentoring Coordinators are delighted to invite Chris Darke (ChrisDarke) to the list of Provisional Mentoring Coordinators, listed in MAINTAINERS.txt

We have discussed the responsibilities of the role and, indeed, agreed that a primary task for those joining as provisional members in this update will be to better document the processes we follow.

Issue fork drupal-3187239

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

rachel_norfolk created an issue. See original summary.

chrisdarke’s picture

chrisdarke commented

Really looking forward to continuing to help out with mentoring and the planning of contribution mentoring in events! Great to be part of the team!!

rachel_norfolk’s picture

rachel_norfolk
Primary language English
Location UK
commented
Issue tags: +Europe2020

Hey, I’m at DrupalCon Europe 2020 so adding the tag!

chrisdarke’s picture

chrisdarke commented
Status: Active » Needs review

Taking a leaf out of AmyJune's book (https://www.drupal.org/project/drupal/issues/3187240#comment-13931149), moving this issue to Needs Review for community feedback.

xjm’s picture

xjm
she/her
Primary language English
commented

Hey @ChrisDarke, congrats, and I look forward to collaborating with you in the future!

The next step is for @ChrisDarketo confirm on the issue that they accept the role as described 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.

As well as the general maintainer role as described in the core governance.

And we'll need a patch against MAINTAINERS.txt. :)

chrisdarke’s picture

chrisdarke commented

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.

Do I push up the patch? Don't want to get ahead of myself on that one, if it's meant to be done by someone else?
(I guess in this case we aren't doing a merge request)

xjm’s picture

xjm
she/her
Primary language English
commented

@ChrisDarke You are welcome to create the patch or make a MR! An MR might actually avoid having commit conflicts between the three issues, and there's no CS validation or anything that needs to happen for this so I'm not worried about the outstanding problems there. See the formatting notes I posted on the other issue:

The correct formatting is to add the name to the list above, with the word (provisional) in front of it. See the PHPUnit Initiative section for an example.

Probably we can group the provisional names at the end.

chrisdarke’s picture

chrisdarke commented

OK cool.. wasn't sure if a MR for a small change like this was appropriate. But sure! :)

ChrisDarke opened merge request !136

annikaC’s picture

annikaC commented
Status: Needs review » Reviewed & tested by the community

Congratulations Chris :)

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
commented
Version: 9.2.x-dev » 9.1.x-dev
Status: Reviewed & tested by the community » Fixed

Committed and pushed 85f8da8cea to 9.2.x and 278d00317c to 9.1.x. Thanks!

Congratulations @ChrisDarke!

  • alexpott committed 84fb997 on 9.2.x 
    Issue #3187239 by ChrisDarke: Add Chris Darke (ChrisDarke) as a...

  • alexpott committed 566ffb5 on 9.1.x 
    Issue #3187239 by ChrisDarke: Add Chris Darke (ChrisDarke) as a...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

nicxvan closed merge request !136