Offering to maintain Structure Sync

Created on 4 April 2025, 3 days ago

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.

💬 Support request
Status

Active

Version

2.0

Component

Miscellaneous

Created by

🇧🇪Belgium dieterholvoet Brussels

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

Comments & Activities

  • Issue created by @dieterholvoet
  • 🇧🇪Belgium dieterholvoet Brussels

    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 💬 Offering to maintain Structure Sync Active )? I would like to become a co-maintainer of the module to help resolve any pending and future issues.

    Thanks in advance,
    Dieter Holvoet

  • 🇨🇦Canada mparker17 UTC-4

    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!

Production build 0.71.5 2024