Last modified: 2014-04-26 13:54:48 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 8994 - Quality assurance by adding some sysop-space to articles.
Quality assurance by adding some sysop-space to articles.
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-02-15 13:23 UTC by Nux
Modified: 2014-04-26 13:54 UTC (History)
0 users

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


Description Nux 2007-02-15 13:23:12 UTC
The idea is to add some space editable only by sysops (or some other group).
This space would be merged with the article so it would be shown on top of the
article. This could contain some messages about the article that would have to
be change by some selected group of users. There would also be some triggers
that would fill this field automatically:
* on new-page fill with "{{warn newpage}}" (text changeable trough MediaWiki:)
* on change by IP fill with "{{warn IP change}}"
* on change by some-group fill with "{{warn some-group change}}"

Of course communities could decide to blank the text to be inserted on some
events (through MediaWiki namespace). Note that this functionality would also
assure that when some important template or some administrative category is
inserted it will stay there, so no backlogs or stuff like would be needed.

Technically it wouldn't have to be long so it could be a simple varchar(255)
field or even smaller (though not too short so long category names could be
inserted). Adding this restriction would also stop some users from moving the
real article's content to this field.
Comment 1 Andre Klapper 2014-04-22 07:54:06 UTC
Nux: Why are existing Special: pages not sufficient so that such information should be displayed in the article itself?
Comment 2 Nux 2014-04-26 13:54:48 UTC
I think that after adding review options this is not really important anymore.

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