Talk:Technical communications/Status helper

API

What ever we choose lets make sure it has an API so that we can allow bots, apps, etc to both read/write this data Tfinc (talk) 20:28, 16 April 2012 (UTC)

Script invocation

I realize this was clear in my mind but not clear in the specs: it would be great if the script could be invoked using custom links, besides the one in the sidebar.

We use many templates to display status updates in various places, e.g.:

• [[Template:Wikimedia project index line]] on team hubs
• [[Template:Wikimedia project status line]] on activity pages
• [[Template:Wikimedia engineering report project status]] on monthly engineering reports

Some of these templates include custom edit links to edit the status or add a new one (and ideally all should). It would be great if the script could be invoked by these edit links, which could be constructed by the templates to include parameters. Here's an example of what it would look like:

• The monthly report template currently uses parameters to display the appropriate update ({{Wikimedia engineering report project status|Wikimedia Apps|2012-05-monthly}})
• That template could be modified to create a custom edit link (perhaps something like https://www.mediawiki.org/w/index.php?title=Wikimedia_Apps/status&withJS=User:Robmoen/projectStatusHelper.js&activity=Wikimedia_Apps&date=2012-05-monthly)
• The link would invoke the Status helper which would recognize the parameters and per-fill the Project, date and monthly fields (and the status field if something already exists).

This would allow us to create multiple, more specific points of entry for the script. Would it be difficult to implement? guillom 09:15, 24 May 2012 (UTC)

Note: this is currently being done by RobLa with the data- markers.

Page purge

It would be nice if the page where you are when you load the status helper was purged after the status is saved, so that you don't have to refresh the page manually to see the result of your edit. guillom 15:10, 2 June 2012 (UTC)