Add acbramley as co-maintainer for block content module

Created on 30 November 2023, 7 months ago
Updated 2 December 2023, 7 months ago

Problem/Motivation

@acbramley has been instrumental in several major improvements to the block content module:
🐛 Information disclosure access bypass for revision log fields when the JSON:API module is enabled Fixed
📌 Remove RevisionLogEntityTrait overrides in BlockContent Fixed
🐛 BlockContentAccessControlHandler requires access block library permission for update, delete and revisions operations Fixed
Add Media revision UI Fixed
🐛 Allow reverting block content with "administer block content" permission Fixed
🐛 Revert and Delete actions should not be available for the current revision Fixed
📌 Rename Custom Block terminology in the admin UI Fixed
Move Custom block library to Content Fixed
🐛 Create a redirect for the new Block types path Fixed
Add Block Content revision UI Fixed
Add "edit block $type" permissions Fixed
#3053881: Reverting entity revisions that contain custom blocks erroneously triggers EntityChangedConstraint
#3131126: Can't show 'revision author' on Block content views

I've approached him and asked if he is interested in being a co-maintainer, he has said yes.
I also asked @smustgrave (co-maintainer) and he is supportive too.

Steps to reproduce

Proposed resolution

  1. @acbramley to confirm publicly and confirm that:
  2. patch/MR to maintainers.txt
  3. review
  4. rtbc
  5. commit
  6. update maintainers on node/3060

Remaining tasks

As above

User interface changes

API changes

Data model changes

Release notes snippet

📌 Task
Status

Fixed

Version

10.2

Component
Block content 

Last updated 5 days ago

Created by

🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.69.0 2024