I've been attending the past couple of JavaScript weekly meetings, and something that's come up is that would help accelerate things and reduce burnout is having another JS subsystem maintainer who can kind of run point with the folks doing development work, who attends the weekly meetings, can do real-time communication in Slack, etc.

@justafish was recommended both by the JS team in attendance as well as core committers back in Vienna as a suitable candidate. I spoke with her and she agreed to put her name forward. @drpal states her qualifications as:

- excellent communication/human skills.
- advanced knowledge of modern javascript issues.
- works with React daily.
- funny. (which... I see your funny and raise you "effing hilarious")

This initiative is critical to Drupal's future, so I'd love to help set it up for success any way we can. This wouldn't change our normal flow of deferring to specific subsystem maintainers if they've raised a problem, but would simply add to the pool of people able to review with some authority any JavaScript-touching patches, which seems like a great idea to me.

What say you?

CommentFileSizeAuthor
#4 js-maintainers-plus-plus.patch483 byteswebchick

Comments

webchick created an issue. See original summary.

GrandmaGlassesRopeMan’s picture

GrandmaGlassesRopeMan
he/him
Primary language English
Location 🌎
commented

←✌️→

Obviously ➕1️⃣ from me.

nod_’s picture

nod_
Primary language French
Location Lille
commented

+1

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Status: Active » Needs review
StatusFileSize
new js-maintainers-plus-plus.patch483 bytes

Ok, well! Here's a patch then. :)

eatings’s picture

eatings
he/him
Primary language English
Location San Francisco, USA
commented

NB: justafish is pronounced 'Hoos-taw-feesh'.

Not a maintainer myself, but def. a supporter of this change.

effulgentsia’s picture

effulgentsia commented

https://www.drupal.org/contribute/core/maintainers#decisions says:

If the change involves adding a new subsystem maintainer, a product, framework, or release manager must approve or refuse it (depending on the subsystem).

+1 from me as a backend framework manager. However, I think this should also get approval from a frontend framework manager who's involved with JS patch reviews; in other words, @lauriii.

justafish’s picture

justafish
she/her
Primary language English
Location London, UK
commented

🤗 💃 🎉

lauriii’s picture

lauriii
he/him
Primary language Finnish
Location Finland
commented
Status: Needs review » Reviewed & tested by the community

I would be happy to see @justafish work as a JavaScript subsystem maintainer. Marking this RTBC since there's support from other JavaScript subsystem maintainers, a backend framework manager, a product manager and most importantly from @justafish herself.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

🎉

e0ipso’s picture

e0ipso
Primary language Catalan
Location Can Picafort
commented

Yes!

+1

xjm’s picture

xjm
she/her
Primary language English
commented

BWAHAHA finally got her! Thanks @webchick and thanks @justafish.

justafish is pronounced 'Hoos-taw-feesh'.

Wait, really?

  • xjm committed 4204b0b on 8.5.x 
    Issue #2928433 by webchick, nod_, drpal, effulgentsia, justafish,...

  • xjm committed 44a37eb on 8.4.x 
    Issue #2928433 by webchick, nod_, drpal, effulgentsia, justafish,...
xjm’s picture

xjm
she/her
Primary language English
commented
Status: Reviewed & tested by the community » Fixed

Committed and pushed to 8.5.x and 8.4.x. Yay! I've also:

  • Added issue maintainer privileges to 3060 (congrats, you too now get to wade through a giant "Assigned" field).
  • Added her membership for groups.drupal.org/core so she can post announcements about the subsystem.

Thank you @justafish for being awesome, and welcome to the core maintainer team. 💃🏻

Status: Fixed » Closed (fixed)

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