Offering to maintain Anti-Duplicates

Created on 28 September 2023, about 1 year ago
Updated 9 October 2023, about 1 year ago

Problem/Motivation

This is a very promising and useful module, but the current state is very buggy. I created multiple issues with fixes to improve that, but there hasn't been any response from the maintainer yet. That's why I want to propose becoming a co-maintainer of the Anti-Duplicates module to merge the many outstanding bug fixes in the issue queue. 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 Anti-Duplicates.

📌 Task
Status

Closed: won't fix

Version

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

    I contacted the two maintainers, @matsbla and @teeyo:

    Hi,

    Could you post a comment on my offer to maintain the Anti-Duplicates module
    ( https://www.drupal.org/project/anti_duplicates/issues/3390438 📌 Offering to maintain Anti-Duplicates Active )? I would like
    to become a co-maintainer of this module to improve the stability and
    usability of the module.

    Thanks in advance,
    Dieter Holvoet

  • 🇳🇴Norway matsbla

    Hi! Sorry you had to wait a little on some of the issues! I'm open to collaborate, but maybe we should discuss a little roadmap first? Are you just looking at solving bugs or would you like to make bigger changes on the module?

    I worked with co-maintainers before who are so eager to quickly solve their own issues that they forget to consolidate the solution, and either introduce new bugs or introduce solutions only tailored to their own cases. I personally check everything thoroughly before I commit, I like to have several eyes on it, do some manual checking, and discuss others use cases. I prefer to spend a little longer time to make something solid than work too quickly :)

    My own idea with this module for now is that it should have some more flexible configuration of the result box, and that it should be more configurable for each content type - what are your own thoughts?

  • Status changed to Closed: won't fix about 1 year ago
  • 🇧🇪Belgium dieterholvoet Brussels

    No problem! As long as you're committing to managing the issue queue every now and then, I don't feel the need to become maintainer. This request was just in case the module was being abandoned, I wasn't sure. For now I'm mostly focused on solving bugs, but if you have any feature ideas, feel free to open issues and let me know on Slack. I might be down to help :)

Production build 0.71.5 2024