Problem/Motivation

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.

Proposed resolution

Review my profile and, if approved, add me as maintainer with appropriate permissions to merge code, manage issues, and create releases.

Remaining tasks

Add DieterHolvoet as co-maintainer of Required API.

Comments

dieterholvoet created an issue. See original summary.

dieterholvoet’s picture

mparker17 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:

Hi,

Could you post a comment on my offer to co-maintain Structure Sync (https://www.drupal.org/project/structure_sync/issues/3517380)? I would like to become a co-maintainer of the module to help resolve any pending and future issues.

Thanks in advance,
Dieter Holvoet

mparker17’s picture

Status: Active » Reviewed & tested by the community

Hi @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!

avpaderno’s picture

As 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.

dieterholvoet’s picture

Project: Structure Sync » Drupal.org project ownership
Version: 2.0.8 »
Component: Miscellaneous » Maintaining offer
avpaderno’s picture

Assigned: Unassigned » avpaderno
Category: Support request » Task
Status: Reviewed & tested by the community » Active

Apart from fidovdbos, the other project maintainers logged in at least once in the past two months.

I will contact them before my dinner.

avpaderno’s picture

Since mparker17 already commented saying he supports this offer, and since he was waiting for a reply from another maintainer, I will not contact mparker17.

avpaderno’s picture

This is the first message I sent.

Hello Colan,

I am contacting you because Dieter (https://www.drupal.org/u/dieterholvoet) offered to become maintainer for Structure Sync (https://www.drupal.org/project/structure_sync), a project for which you are maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3517380 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, Dieter will be probably made maintainer.

Matt already commented and said he supports the offer, but he wanted a reply from another 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.

I am contacting all the people who can administer co-maintainers/maintainers for the project.

As last note: This offer is about being maintainer, which is different from being co-maintainer. A maintainer is a person who has all the drupal.org permissions on a project: Write to VCS, Edit project, Administer maintainers, Maintain issues, Administer releases. A person who does not have all those permissions is a co-maintainer.
If there is any reason for not giving all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3517380. 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

I am still contacting the other maintainers.

avpaderno’s picture

Status: Active » Postponed

I 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.

colan’s picture

After reviewing @mparker17's analysis, I second the request. Please make the requestor a maintainer with full privileges. Thanks!

mparker17’s picture

Status: Postponed » Fixed

I have added dieterholvoet and granted all privileges!

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.