Handling modules with similar names / descriptions

Created on 1 December 2022, about 2 years ago
Updated 28 September 2024, 3 months ago

There is a growing trend lately where projects are being posted to drupal.org with very similar titles and project namespaces.

Here is a recent example:

https://www.drupal.org/project/projects_browser

This is not the "Project Browser" module and initiative which is happening here: https://www.drupal.org/project/project_browser - but someone recently reported in Slack they had mistakenly downloaded Projects Browser.

The first module has an 's' added at the end. I have seen this on a handful of other modules, where either its made plural or singular, depending on the original project name.

This is confusing to end users. Non technical people may often not know the difference, a simple typo with Composer can have you downloading the wrong module while thinking you have the correct one. In the cases where people are copying modules and making minor trivial changes (I.e. Menus Attributes) this potentially breaks any upgrade path from previous versions of Drupal instead of being made to merge the effort with the original project.

Here are a few other cases where I have noticed this that I can recall off the top of my head:

There are likely others...

Is there a way to 'detect' this kind of behavior? In this very specific case (Project Browser), this only seems like it could get more confusing for users when results contain items of the same name, with the same description, etc.

💬 Support request
Status

Active

Component

Policy

Created by

🇺🇸United States kevinquillen

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    We are already asking to list similar projects that already exist, even in the case the similarity is in the project name, or in the project purpose.

    The only way to detect such cases would be in a submission handler for the form to create new projects, but I am not sure it would worth implementing it. There are surely cases where similar project names or project machine names are legitimate.
    For example, the Imagick module and the ImageMagick module both implement an image toolkit, both based on the ImageMagick library, although the latter module could also use the GraphicsMagick library. The difference is that the first module uses a PHP extension, while the latter uses a CLI executable. I take this as example because I always picked up the wrong one: I went to the ImageMagick project page when I wanted to download and use the Imagick module. That would not be a reason for asking to one of the projects to change name, though. Any other name for those projects would be more confusing than their actual, similar, names.

  • Status changed to Fixed 14 days ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    I am closing this issue, since it is a support request which got answered.

Production build 0.71.5 2024