Offering to co-maintain the User subsystem

Adding a merge request

+1 from me (the current user maintainer).

Thanks Moshe! Setting to RTBC then.

+1 for @kristiaanvandeneynde. It has been pleasure collaborating with him on the policy based access related issues.

Thanks @kristiaanvandeneynde! We desperately need a User module maintainer.

To be considered for the role, we need you to confirm that:

• You have read the Drupal core governance, including especially How decisions are made.
• You understand the high-level description of maintainers and are comfortable with it.
• You agree to the subsystem maintainer responsibilities.
• You are committed to providing constructive feedback → as defined in the issue etiquette documentation.

Setting NR to confirm; feel free to re-RTBC if you are comfortable with all that.

Hey @xjm, I just want to confirm that I am applying for the user subsystem, not merely the user module. The code I've written for the Access Policy API goes under \Drupal\Core\Session.

Having said that, I have read the governance document earlier this week when I was made subsystem maintainer for the cache system. It certainly seems as if a subsystem maintainer has a very limited scope of responsibilities compared to a framework, product or release manager and I'm actually happy about that as it's a good way to start as a new core (subsystem) maintainer.

I've bookmarked both the governance and constructive feedback pages and, when in doubt, will not hesitate to consult them. I'm really proud of VariationCache and Access Policy API and being able/allowed to maintain that further down the line seems like a logical next step.

Thanks @kristiaanvandeneynde! Committed to 11.x, 10.2.x, and 10.1.x.

• I verified you have "maintain issues" permission on https://www.drupal.org/node/3060/maintainers → .
• I added you to https://www.drupal.org/about/core/ → which was apparently missed previously.

Hooray!

Awesome, thanks!

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