bbrala has been very active for some time in the JSON:API issue queue, answering questions in Slack and moving things along in the decoupled space. He has also been maintaining the most significant contrib module related to JSON:API for the last ~year. He has the full support of the current maintainers and we are all very excited to have his help.

For convenience: here's a link to the requirements of a sub-system maintainer: https://www.drupal.org/contribute/core/maintainers#subsystem

Issue fork drupal-3220184

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:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

gabesullice created an issue. See original summary.

gabesullice’s picture

+1 !!

Per this issue comment, I think we will need a framework manager review for this along with the other maintainers (and @bbrala ofc).

gabesullice’s picture

Issue summary: View changes
gabesullice’s picture

Issue summary: View changes
e0ipso’s picture

I have had the pleasure to witness the work Bjorn has brought to JSON:API Extras. I think getting him aboard is an awesome opportunity for Drupal.

Let's do it!

+1

bbrala’s picture

Thanks for considering me. I love helping others and feel like JSON:API is an essential part of keeping Drupal relevant in the future. I'm super excited to be able to support Drupal in this role and keep the positive momentum of jsonapi moving forward. ^^

I've read the guidelines and will adhere to them and reserved time weekly to focus on jsonapi and the surrounding ecosystem.

gabesullice’s picture

Status: Active » Needs review
dmsmidt’s picture

+1

I know for a fact that Björn has the experience and ambission to bring lot's of goods. He takes his responsibility and has thought this through (employer and family are in).

Wim Leers’s picture

+1!

I have not had the pleasure of working directly with @bbrala yet, but I blindly trust @gabesullice and @e0ipso, and they have had that pleasure.

In the conversations leading towards this issue getting created it also was very apparent that @bbrala is not only enthusiastic but also very considerate. A very important trait while working in Drupal core. I can't wait to see the impact of @bbrala's enthusiastic guidance 😊

gabesullice’s picture

Status: Needs review » Reviewed & tested by the community

Looks like we have enthusiastic +1's from all the current maintainers and some outside support as well.

xjm’s picture

Status: Reviewed & tested by the community » Needs work
Issue tags: -Needs framework manager review

Any core-the-CMS committer can sign off on adding a subsystem maintainer, not just framework managers. :)

Great to have you, @bbrala! That said, we need either a patch or MR here adding the change to MAINTAINERS.txt. :)

bbrala’s picture

Thanks xjm :) I'll post a patch tonight.

bbrala’s picture

Status: Needs work » Reviewed & tested by the community

  • xjm committed 1a2eb13 on 9.3.x
    Issue #3220184 by bbrala, gabesullice, Wim Leers, e0ipso, xjm, dmsmidt:...

  • xjm committed 06107e4 on 9.2.x
    Issue #3220184 by bbrala, gabesullice, Wim Leers, e0ipso, xjm, dmsmidt:...
xjm’s picture

Version: 9.3.x-dev » 9.2.x-dev
Status: Reviewed & tested by the community » Fixed

Awesome, thanks!

Generally we order the usernames alphabetically by last name within the role, with provisional folks at the end. JSON:API is already out of order, but I fixed the ordering on commit.

Committed to 9.3.x and cherry-picked to 9.2.x. Thanks!

Status: Fixed » Closed (fixed)

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