Page MenuHomePhabricator

Real version control for banners
Open, MediumPublicFeature

Description

Many of our unmet basic requirements would be satisfied by editing in the wiki interface, for example https://meta.wikimedia.org/wiki/MediaWiki:Centralnotice-template-B12_1227_ThankYou_5pillars

Maybe we can do something similar to the Template editor, where the "Read" version uses some semantic knowledge about banners: quotes banner html correctly, pulls some info from the cn_* tables, and links to the Special:NoticeTemplate edit page.

See also,

  • T33689 - Add comment field for campaign/banner changes
  • T22231 - Allow "archiving" of CentralNotice templates
  • T33595 - CentralNotice banners should exist in their own namespace

Version: master
Severity: major

Details

Reference
bz43491

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 1:11 AM
bzimport set Reference to bz43491.
bzimport added a subscriber: Unknown Object (MLST).

More really missing convenient things:

  • Download and upload raw article (banner) source. API for that.
  • Show the template dependency tree, what I have in mind is downloading a complete dev environment for a given notice.
  • Metadata tags and short path for banner titles. It might be conceptually less sucky if we keep each banner in a path, like "campaign/test/banner". Then, url params like "rev=4" to retrieve a known version. The "campaign/" page could have free-form wikitext explaining what tests were run, their results, and so on...

Use ContentHandler, perhaps? Campaigns in UploadWizard do that.

[No progress / updates here; resetting priority to reality and adjusting severity as per [[mw:Bugzilla/Fields#Severity]] ]

Aklapper changed the subtype of this task from "Task" to "Feature Request".
Aklapper removed subscribers: Tbayer, wikibugs-l-list.