Could you please rename the module to "module_denylist" or "module_blocklist" (though that might be confused with core's Block system)? There are racial overtones in the word "blacklist" that as a culture we need to move past, especially when there are more appropriate terms available, like "deny list". Given this module is only at an alpha level it should not cause too much confusion at this early point. Thank you.

Comments

DamienMcKenna created an issue. See original summary.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Active » Needs review

How about this: https://www.drupal.org/project/module_denylist

I've cloned the project into a new one with a better name, have renamed everything, created a new branch using semantic versioning, released 1.0.0-beta1, and have given all maintainers of this module full access to the new one. So now it's ready to go.

badjava’s picture

badjava commented

@DamienMcKenna It would have been nice if you gave the chance for maintainers to respond before creating a new module with no discussion. Perhaps they had another name in mind? Perhaps there was a roadmap that you are unaware of with new features and a different name was more important or many other things you are not aware of. This doesn't feel like an open community move. I get that your intentions are good here, but this module has been around for a few years and I doubt you know much about it.

xjm’s picture

xjm
she/her
Primary language English
commented

The existing maintainers also have access to the proposed replacement. I don't think there's anything wrong with @DamienMcKenna making it as easy as possible to accomplish the rename. I assume they've already been contacted.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

@badjava: Yes, I did jump ahead by creating the new project and everything, I honestly should have waited more than the three days for the maintainers to respond, that was my mistake, I am sorry for being so hasty, and I accept responsibility for it.

The module itself is pretty short 'n simple, there isn't a lot to it, and after three years to fix D9 compatibility, so I can't imagine there was a huge unpublished roadmap that's now thrown off by my actions.

Let's see how the maintainers would like to proceed from here.

badjava’s picture

badjava commented

We are looking into adding a module allow list in addition to the deny configuration. In this case, it might make more sense to call it module_allow for example rather than deny or block.