Last modified: 2014-03-19 16:03:03 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T45491, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 43491 - Real version control for banners
Real version control for banners
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
CentralNotice (Other open bugs)
master
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-28 21:53 UTC by Adam Wight
Modified: 2014-03-19 16:03 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Adam Wight 2012-12-28 21:53:18 UTC
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,
* Bug 31689 - Add comment field for campaign/banner changes
* Bug 20231 - Allow "archiving" of CentralNotice templates
* Bug 31595 - CentralNotice banners should exist in their own namespace
Comment 1 Adam Wight 2012-12-28 22:07:56 UTC
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...
Comment 2 Yuvi Panda 2013-09-24 15:09:27 UTC
Use ContentHandler, perhaps? Campaigns in UploadWizard do that.
Comment 3 Andre Klapper 2014-03-19 16:03:03 UTC
[No progress / updates here; resetting priority to reality and adjusting severity as per [[mw:Bugzilla/Fields#Severity]] ]

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links