Could someone clarify the intention behind adding Community-Tech to this task?

In T148154#2717963, @Aklapper wrote:

Could someone clarify the intention behind adding Community-Tech to this task?

It's not something that this team currently works on, but as far as I understand, this is a kind of task that may interest them some day. Feel free to remove it if it's unhelpful.

@Amire80 Feel free to propose it on the upcoming wishlist survey. :)

Note that this is complicated, because it would be easy to mis-use, similar to trolls spamming !admin in IRC. The template-workaround enables an easy opt-out (remove your username from the template). This needs some deep thought.

In T148154#2761357, @Quiddity wrote:

Note that this is complicated, because it would be easy to mis-use, similar to trolls spamming !admin in IRC. The template-workaround enables an easy opt-out (remove your username from the template). This needs some deep thought.

Sure, no rush at all.

Just mentioning that there's demand for something like this.

Copying across the new comment, that led to my merging the task:

In T110306#8705440, @ChristianKl wrote:

Wikidata's data quality seriously suffers because it currently is not possible to ping all people of big Wikiprojects to advance discussions and agree on common data modeling.

For context, see https://www.wikidata.org/wiki/Template:Ping_project
and further related discussion in the other merged task T200350: Impossibility to use Ping project on projects over 50 participants

This was identified as a really important thing to solve during the Wikidata WikiProjects Days.

Some thoughts that came up during the discussion for how to mitigate abuse:

• only let members of the group ping the group
• have a way to moderate the pings
• limit the numbers of pings that someone can do within a given timeframe
• limit pinging groups to users with a specific right

This ticket was discussed at "WikiProjects Days 2026"; see https://etherpad.wikimedia.org/p/WikidataWikiProjectsDays2026

I left a brief comment in the WikiProject Days BBB session chat, which I would like to expand on here.

In my view, the current architecture that we are trying to improve is somewhat outdated. Within the framework of a stable SUL environment, these notifications should be designed as a user-centric feature, consolidated into a single interface—perhaps as a dedicated tab in user preferences or as an extension of the existing "Notifications" settings—rather than being fragmented across numerous local lists that require ongoing maintenance.

Instead of maintaining manual lists, WikiProjects could provide an entry point (for example, a “Click here to receive notifications as a project member” link) that would add the relevant project name to a user's personal notification settings. The layout of this feature could appear similar to the section "Muted pages for page link notifications", for example.

Such an approach would also make it much easier to gather quick up.to.date metrics on participation and project membership, more granular access control for different user groups, as has already been suggested. Ideally, it might also allow users to decide whether their subscriptions to WikiProjects should be publicly visible or remain private.

• only let members of the group ping the group

It will make it useless,

• limit pinging groups to users with a specific right

this is much better.