Problem/Motivation

Module name is problematic, especially since it is used repeatedly (23 times in the module description), and in a couple of places, seems to be a sort of play on words to mean "good":

Basic SANE architecture
extensible by SANE plugins

Given the ambition of the module: As you can tell from this description, SANE is the one-stop-shopping for all requirements around subscription and notifications. Well, maybe not yet..

It would be best to move away from ableist language (sane = good, which implies insane = bad). Especially since the acronym seem a little forced.

I'm putting this as major because inclusion is important by community consensus.

Proposed resolution

Find an alternate name that is more inclusive and, ideally, that better describe the functionality of the module

Comments

nod_ created an issue. See original summary.

NickDickinsonWilde’s picture

I very much agree @_nod.
If it helps, might I suggest 'DANSE' - French for dance - as a new acronym:
Drupal Audit, Notification, Subscription and Events

jurgenhaas’s picture

Assigned: Unassigned » jurgenhaas

@nod_ thank you very much for bringing this up. No doubt, all we can do to be better in terms of inclusion will be done. There is no reason to question the necessity.

TBH I wasn't aware at all that SANE could be exclusive. Especially because it's an abbreviation and therefore intentionally only used in all-caps. You call it "a little forced". That's true only because the order of the characters isn't right according the purpose of the module, and we chose that order only to be able to pronounce the name. But even with the best intentions, things can go wrong.

@NickDickinsonWilde thanks for your suggestion of DANSE, which is very nice and our team is OK with it.

Hope you don't mind if we still want to better understand how we got this wrong and I saw that the issue is also posted over in Slack where I'll be asking for some help. This is clearly not to dispute your point, I'd rather like to learn for future cases to avoid such mistakes in the first place.

ressa’s picture

If the project linked to below would be willing to let go of its name, how about calling it just "Subscribe"?

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

ressa’s picture

https://www.drupal.org/project/sub is free, the name could still be "Subscribe" ...

jurgenhaas’s picture

That's interesting @ressa, thanks for your suggestions too. The two names are tempting, on the other hand "subscription" is a smaller part of the module, it's rather notifications that are in the focus.

ressa’s picture

You're welcome @jurgenhaas. I thought about it, and sure -- notifications are an important part of the process. But I also think it is implied in the name "Subscribe", that there will be a notification. At least, that's how I think about it. Without a result, what would be the purpose of subscribing in the first place? :) Just my 2 cents, it would be great if some more people share their thoughts.

jurgenhaas’s picture

@ressa most of the notifications are created without any subscription being involved. Think of an intranet with thousands of users with different roles and departments, where a manager creates a node and wants all users of selected departments being notified. That creates notifications for each of those users, even without any subscriptions.

Such use cases have been the original motivation behind this module, the subscriptions came in later as an after thought, just because it was so simple to add.

But the module is more about authors to push, rather than users to pull.

jurgenhaas’s picture

Step 1 completed: modify text on the project's main page and replace SANE with DANSE.

Step 2 completed: register new project page for DANSE

Next steps:

nod_’s picture

Thank you very much for this :)

jurgenhaas’s picture

Status: Active » Fixed

All the other steps have now been completed as well and I'm closing this issue now.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.