Use a consistent package name for all info.yaml files

Created on 3 June 2025, 3 days ago

Problem/Motivation

At the moment the three modules for PII are placed in two different groups on admin/module. The PII module can be found in the Custom group, while the pii_api and pii_ui are placed within the PII group. Ideally modules/submodules of the same module should ideally be placed within the same group, so they are in close proximity to avoid modules go unnoticed. when i've enabled pii for the first time and was then exploring the ui for ui elements i've not found any trace on content types. i then went back to the modules list page and stopped searching/scrolling after i've found the custom group containing the installed pii module - that way i've missed that i still had to install the pii_ui module. having all modules within the same group would have prevented that problem. and second, it should be avoided to use acronyms as the group label. for the person installing a module it is fine but if someone else is visiting the module page afterwards the pii group might be cryptic if ones focus is solely on the group labels scanning through the list. and in general, if modules are adding their module specific groups, the modules list gets fragmented and barely skim-able.

Steps to reproduce

Proposed resolution

I would suggest to use the same package name on all three info.yaml files. Instead of using the module name i would go with Privacy instead. That would avoid the acronym and a module specific group name, plus other modules like Klaro could use that group as well then.

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Active

Component

Code

Created by

🇩🇪Germany rkoller Nürnberg, Germany

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @rkoller
  • 🇩🇪Germany rkoller Nürnberg, Germany

    After a brief discussion at todays monthly track meeting i'Ve changed the suggestion from Privacy to Privacy & Data protection per the recommendation from @jurgenhaas. According to him, the scope of the term privacy alone would have been too narrow.

    the only detail, looking at the screenshot, the module names might need some adjustment as well, the three look sort of inconsistent.

  • 🇩🇪Germany rkoller Nürnberg, Germany

    and on a side note while going through the info files i've noticed too more detail probably out of the scope for this issue.

    in pii_ui.info.yaml the second dependency is pii:pii_ui shouldnt that be just pii? and i guess it might make sense to also remove the requirement for drupal 9 in pii_ui.info.yaml and pii_api.info.yaml

  • 🇩🇪Germany rkoller Nürnberg, Germany
Production build 0.71.5 2024