New initiative leads for the PHPUnit initiative

It's an honor for me to be asked!

I've been working a lot on the PHPUnit initiative and have come to really care a lot about it.

For the last 7 years I have worked with (and loved) Drupal almost each day. I started with Drupal 5 and have seen the massive steps Drupal has made over the last few years. I have worked on several large and complex websites and always have had a focus on quality.

I got into the Drupal community itself since Drupal 8, only fairly recent. I started with some minor issues (conversions of BrowserTestBase to JavascriptTestBase) and quickly worked my way up to working on changes to the core testing framework. I worked on several random failures and did a lot of research into the proper usage of the JavascriptTestBase tests.

I really care about the initiative because I see a huge value in the move from Simpletest to PHPUnit. I also see that it lacks a bit of sexyness and general interest, that's one of the reasons I got into it.

I'm not sure if many things will change for me once I'm lead, in a good way :) I have been involved in the more advanced tasks in the initiative and have started to focus more on the planning and general management of the issue queue. To me that's what beeing a lead is: keeping the initiative on the right track and making sure the right things get done at the right time.

Is short: I really look forward to this and I will certainly try my very best for the initiative!

I've seen miechielnugter and Lendude work together seamlessly. They are enthusiastic about the initiative and know their way around testing. They also have proven themselves by making Views better and better all the time.

You guys have my endorsement!

I would be happy to step in. Like @michielnugter I believe the PHPUnit Initiative is a great move forward and would be happy to keep spending my time on it with a little shift in focus.

I think at DevDays Seville we showed that we can help the Initiative by mentoring and getting people enthusiastic about helping out.

++
I think the PHPUnit Initiative would be in great hands with michielnugter and Lendude.

Patch for MAINTAINERS.txt. Added us to the PHPUnit initiative and the provisional membership as proposed by LenDude.

Well, that's what I was thinking as well, but looking at the rest it doesn't seem like it. I assumed sort by Drupal-seniority :)

Although is almost clear form #2, to make this formal we need confirmation from @michielnugter that he has read and would like to take on the responsibilities outlined in https://www.drupal.org/contribute/core/maintainers and particularly https://www.drupal.org/contribute/core/maintainers#initiative

Thank you for pointing me to the article, it has made the lead role a lot clearer.

I have just read the article and I understand and accept the described responsibilities. I'm really looking forward to assuming the role (which I'm already moving toward) and working on making the PHPUnit initiative a succes!

I been following @michielnugter progress during this week and his job really adds a lot of value to the phpunit initiative. It seems there's consensus from other community members here too.

@dagmar: Thanks for the kind words!

I'll be sure to continue doing my best to make the PHPUnit initiative a succes.

With initiative lead changes we need a +1 from Dries.

I'm comfortable with this patch being committed. Thanks for stepping up to help Len and Michiel!

Thanks Dries! I'm really glad to see us adding provisional initiative leads. :)

One small concern is that I don't think this is formatted clearly. I don't think the names should be listed twice. When applied, the patch looks like this:

Initiative coordinators
-----------------------

The Drupal Core Initiative coordinators oversee approved projects that
re-architect or otherwise improve large areas of Drupal core. See
https://www.drupal.org/community-initiatives/drupal-core for more information on
their responsibilities. The initiative coordinators for Drupal 8 are:

Workflow Initiative
- Dick Olsson 'dixon_' https://www.drupal.org/u/dixon_

PHPUnit Initiative
- Daniel Wehner 'dawehner' https://www.drupal.org/u/dawehner
- Len Swaneveld 'Lendude' https://www.drupal.org/u/lendude
- Michiel Nugter 'michielnugter' https://www.drupal.org/u/michielnugter

Layout Initiative
- Tim Plunkett 'tim.plunkett' https://www.drupal.org/u/tim.plunkett
- Emilie Nouveau 'DyanneNova' https://www.drupal.org/u/dyannenova

Media Initiative
- Janez Urevc 'slashrsm' https://www.drupal.org/u/slashrsm

Provisional membership:
- Len Swaneveld 'Lendude' https://www.drupal.org/u/lendude
- Michiel Nugter 'michielnugter' https://www.drupal.org/u/michielnugter

This makes it look like Lendude and michielnutger are both full initiative leads for PHPUnit, and provisional initiative leads for Media.

For core committers (the only other section with provisional members), the formatting is a bit different already:

Drupal 8
- Alex Bronstein 'effulgentsia' https://www.drupal.org/u/effulgentsia
  (Framework Manager)
- Dries Buytaert 'dries' https://www.drupal.org/u/dries
  (BDFL, Product Manager)
- Angela Byron 'webchick' https://www.drupal.org/u/webchick
  (Product Manager)
- Nathaniel Catchpole 'catch' https://www.drupal.org/u/catch
  (Framework Manager, Release Manager)
- Jess Myrbo 'xjm' https://www.drupal.org/u/xjm
  (Release Manager)
- Alex Pott 'alexpott' https://www.drupal.org/u/alexpott
  (Framework Manager)
- Scott Reeves 'Cottser' https://www.drupal.org/u/cottser
  (Framework Manager - Frontend)

Provisional membership:
- Lauri Eskola 'lauriii' https://www.drupal.org/u/lauriii
  (Framework Manager - Frontend)
- Gábor Hojtsy 'Gábor Hojtsy' https://www.drupal.org/u/gábor-hojtsy
  (Product Manager)
- Chris McCafferty 'cilefen' https://www.drupal.org/u/cilefen
  (Release Manager)
- Roy Scholten 'yoroy' https://www.drupal.org/u/yoroy
  (Product Manager)

It's not quite the same since product, framework, and release management are roles rather than a particular part of core, so it's not a great model for initiatives.

Maybe the provisional membership could be indented under the initiative, like we have for the DB subsystem?

(Come to think of it, the committer section as currently formatted is also getting hard to read as we add new members and grow the team but that's out of scope here.) :)

Thank you @Dries for your confidence in us!

@xjm:

Did you mean something like this? I does make it a lot clearer like this. Though I love the API-first Initiative I have my plate full with the PHPUnit initiative right now :)

Yep, I think that looks good. Thanks @michielnugter!

Hope I'll have better luck with the actual work :)

Rerolled the patch after #2874043: Node module should have a listed maintainer.

#21 should not have required a reroll? It's in a totally different part of the file. Weird...

I wanted to commit this given signoff by @Dries and @xjm. Went ahead and granted issue maintainership role on the Drupal project to Lendude and michielnugter. However as per https://www.drupal.org/core/maintainers/provisional-committers I should not commit MAINTAINERS.txt changes as a provisional core committer, so I guess I cannot complete this.

Committed/pushed to 8.4.x and cherry-picked to 8.3.x. Thanks!

This was added to the API-first Initiative section instead of the PHPUnit Initiative section.

#17 was correct, but the rebase in #21 moved it to the wrong location.

Here's a patch with the additions in the right place.

Git doesn't do so well with this file because of all the repetition.

Lol. That's kinda my bad for RTBCing it.

Committed and pushed 1fbc766 to 8.4.x and 5960157 to 8.3.x. Thanks!

Wow, sorry about that and thanks for fixing it!

Git doesn't do so well with this file because of all the repetition.

Yep, this is mostly on git, for not using enough context :)