Hello, one of our sites is looking to improve our entity browser field and this is exactly what we are looking for but notice no D11 release.

I'm offering to help co-maintain this module. Currently I maintain/co-maintain 50+ modules and in addition am a sub-maintainer for a few components of Drupal core.

My strategy is usually to start a new branch for 10.4/11 for modern php and a gitlab that checks several versions.

Would just need permission to do releases and maybe edit the description page, I currently get 2 paid days a month to manage modules just have to put the company that's paying me.

Let me know!

Comments

smustgrave created an issue. See original summary.

smustgrave’s picture

Contacted maintainer james hawthorn-byng just now

avpaderno’s picture

Category: Plan » Support request
abhinesh’s picture

Hi everyone,

I’ve already worked on adding Drupal 11 support for this module and also reached out to the current maintainer about three months ago, but it seems they’ve been inactive for a while.

I’m also very interested in helping with co-maintainership to ensure ongoing updates and compatibility. Happy to collaborate on creating a new branch and keeping the module aligned with modern PHP and core updates.

Thanks!

avpaderno’s picture

Project: Entity Browser - Table Layout » Drupal.org project ownership
Version: 8.x-1.x-dev »
Component: Miscellaneous » Co-maintaining offer
Assigned: Unassigned » avpaderno
Category: Support request » Task

Since smustgrave confirmed on Slack he is still interested in becoming co-maintainer, I am moving this issue to the Drupal.org project ownership queue.

avpaderno’s picture

avpaderno’s picture

Title: Offering to co-maintain Entity Browser - Table Layot » Offering to co-maintain Entity Browser - Table Layout

This is the message I sent.

Hello James,

I am contacting you because Stephen (https://www.drupal.org/u/smustgrave) offered to become co-maintainer for Entity Browser - Table Layout (https://www.drupal.org/project/entity_browser_table), a project you created for which you are project owner and sole maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3549789 about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
Without a comment posted on that issue in the next 14 days, Stephen will be probably made co-maintainer.

Project moderators will not remove the existing maintainers/co-maintainers; the project owner will not be replaced either. Maintainers cannot change the project owner; co-maintainers/maintainers can only be removed/added by people who have the permission to administer co-maintainers/maintainers.

As last note: This offer is about being co-maintainer, which is different from being a maintainer. A co-maintainer is a person who does not have all the drupal.org permissions on a project. Even though being co-maintainers could mean having just a single permission, we expect a co-maintainer to have the following permissions on the project: Write to VCS, Edit project, Maintain issues, Administer releases.
If there is any reason for not giving all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3549789. We need this to know it was intentional and not a misunderstanding on what the offer required.

Best regards,
Alberto Paderno
-- Drupal.org project moderator
-- Drupal.org site moderator

avpaderno’s picture

Status: Active » Postponed

The status is Postponed because we are waiting for a reply.

Please post a comment after 14 days, if your offer has not been declined. It will show you are still interested in maintaining this project and it will serve as reminder that a project moderators' action is required.

avpaderno’s picture

Status: Postponed » Fixed

I added smustgrave as co-maintainer, since he today confirmed on Slack he still wants to be co-maintainer.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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