Closed (fixed)
Project:
Drupal.org project ownership
Component:
Maintaining offer
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
4 Apr 2025 at 11:19 UTC
Updated:
19 Jan 2026 at 21:14 UTC
Jump to comment: Most recent
I would like to become a co-maintainer of the Structure Sync module to improve its stability and usability, by going through the issue queue and deal with open bug reports and suggested improvements. We're using this module in every project at the agency I work at, so we're willing to invest time into improving it.
You can view my profile to see my history of work.
Review my profile and, if approved, add me as maintainer with appropriate permissions to merge code, manage issues, and create releases.
Add DieterHolvoet as co-maintainer of Required API.
Comments
Comment #2
dieterholvoet commentedmparker17 and louis-cuny seem to be the only active maintainers in the past 2 years. Only mparker17 has their contact tab enabled, so only sending him a message for now. This is the message:
Comment #3
mparker17Hi @dieterholvoet, thank you for offering to maintain the module!
(I haven't had as much time to maintain the module as I would like recently due to life circumstances; also, the client I'm currently working for doesn't use this module, so I can only contribute as a volunteer)
I have taken a look at some of your recent contributions. I am happy to see that you have experience co-maintaining and contributing to many other modules. Of the contributions that I saw, your code was clear and made good use of APIs, and your interactions with other community members was friendly and thoughtful. I am happy to see that you've written tests, especially in your work on the ECK module. For all of these reasons, I support your request to co-maintain structure_sync!
I would like to hear from at least 1 other maintainer if possible, so I'm going to mark this as RTBC. I work with @sensespidey (another co-maintainer) so I'll ping him in our company instant messenger to review this issue as well. If we don't hear back from any other maintainers by April 18th, then I will grant you maintainership myself.
For me, one of the most important gates to accepting patches for any module that I maintain is for the patch to have tests, because tests make my job as a maintainer SIGNIFICANTLY easier. When responding to a merge request, I have been trying to remember to offer the author help with writing tests; and for high-priority issues, I try to add tests to the merge request myself if they are missing. Thus, my personal request to you as a new co-maintainer, is to try to do the same. Thank you in advance!
Comment #4
avpadernoAs a reminder: These offers can be moved in the Drupal.org project ownership queue, after they have been kept in the project queue for at least 14 days, and none of the maintainers commented to decline the offer, if the person who made the offer is still interested.
Comment #5
dieterholvoet commentedComment #6
avpadernoApart from fidovdbos, the other project maintainers logged in at least once in the past two months.
I will contact them before my dinner.
Comment #7
avpadernoSince mparker17 already commented saying he supports this offer, and since he was waiting for a reply from another maintainer, I will not contact mparker17.
Comment #8
avpadernoThis is the first message I sent.
I am still contacting the other maintainers.
Comment #9
avpadernoI contacted all the maintainers.
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 moderator's action is required.
Comment #10
colanAfter reviewing @mparker17's analysis, I second the request. Please make the requestor a maintainer with full privileges. Thanks!
Comment #11
mparker17I have added dieterholvoet and granted all privileges!