Page MenuHomePhabricator

Notify users about deletion tags being added to pages they created
Open, Needs TriagePublic


Users should be automatically notified, using the notification system, when any page they created is tagged for deletion, For recognition of deletion tags, a MediaWiki: namespace page could be created (similar to the way disambiguation pages used to be recognized for certain autogenerated lists of pages), or a magic word could be used (similar to the way the disambiguation pages are recognized now).

Proposed in Community-Wishlist-Survey-2016. Received 31 support votes, ranked #49 out of 265 proposals. View full proposal with votes and discussion here.

New Notification Request Form

Filling out this form will help developers and product people understand your idea and will provide the information required to implement it. To see examples of the types of answers required, have a look at this sample form. To understand unfamiliar terms, visit the glossary. 

Basic information

  - Purpose of the notification:  
  - Notification name:  
  - What triggers notification?: 
  - "Notice" or "Alert"?:  
  - Notification type (standard, bundled, expandable bundle):  


For a single message

  • Header: 
  • Body:  

For Bundled Messages

  • Main, bundling message:
  • Subsidiary, bundled message:


  - Primary link target:
  - Primary link label (for email display only):

  - #1 secondary link target: 
  - #1 secondary link label:

  - #2 secondary link target:
  - #2 secondary link label:


  - Icon name:  
  - Link to graphic/example: 

Event Timeline

OdMishehu raised the priority of this task from to Needs Triage.
OdMishehu updated the task description. (Show Details)
OdMishehu added a project: Notifications.
OdMishehu added a subscriber: OdMishehu.
Restricted Application added subscribers: StudiesWorld, Aklapper. · View Herald Transcript

This is tagged PageCuration, so noting that they already are, but only if they add the tag through PageCuration.

This task was proposed in the Community-Wishlist-Survey-2016 and in its current state needs owner. Wikimedia is participating in Google Summer of Code 2017 and Outreachy Round 14. To the subscribers -- would this task or a portion of it be a good fit for either of these programs? If so, would you be willing to help mentor this project? Remember, each outreach project requires a minimum of one primary mentor, and co-mentor.

I'm thinking this should apply to major editors of a page as well. I regularly run into articles tagged for deletion where the creator is long gone, but editors who touched it quite a bit along the way are still around. The current approach of maybe sometimes the creator being notified (like if Twinkle is used) has led to charges of our delete processes being sneaky. See

Would anyone be interested in being a point of contact/ mentor/ available to answer questions for this task during the Wikimedia-Hackathon-2017? I would like to list your name here: T154988 cc @Mattflaschen-WMF @jmatazzoni

I've pasted the New Notification Request Form into the description. Filling this out will help you fully define your project and will give developers and others the info they need to effectively comment on the plan and make it happen.

I think notifying watchers instead of creators is much more effective and useful.

I think notifying watchers instead of creators is much more effective and useful.

Good thought, although we want to be careful here, as who's watching a page is supposed to be private.

Yes, but Notifications are private as well.

Yes, but Notifications are private as well.

Oh, I missed "using the notification system". I was thinking in terms of the current approach, using talk page messages to "notify".

Izno added a subscriber: Izno.

In its current shape and form, this project does not feel ready to be promoted via Outreach-Programs-Projects. Also as it is now under Growth-Team's umbrella as well, removing the tag.

PageTriage usually notifies the creator via notification and via user talk message. Twinkle usually notifies the creator via user talk message. I think this covers a majority of use cases on enwiki, so that's good.

The remaining use case is an editor who chooses not to use those two power tools adding a deletion template and then not posting on the creator's user talk. To catch these, we'd probably need an update to core or the creation or update of an extension. And to avoid making it enwiki-specific, we'd need a place to program in the list of templates to listen for on each wiki.

I guess I'll leave this tagged PageTriage for now, as that would be one way to implement it.