Last modified: 2009-01-02 19:22:19 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 12362 - Use consistent grammar in special page names
Use consistent grammar in special page names
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Lowest trivial with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-12-20 04:08 UTC by Dan Jacobson
Modified: 2009-01-02 19:22 UTC (History)
3 users (show)

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


Description Dan Jacobson 2007-12-20 04:08:59 UTC
Can we please use a uniform grammar here:
# List of blocked IP addresses and usernames
# List redirects

Please use all nouns ("List of redirects") or all verbs,
("List blocked IP addresses and usernames") but don't "mix and match".
Comment 1 Dan Jacobson 2007-12-26 02:07:06 UTC
We observe even a third grammatical category:
# User list
and maybe more. One is afraid to look.
Comment 2 Andrew Garrett 2008-08-08 12:12:32 UTC
We now have them in two categories:
* Verbs describing what the page *does* (e.g. View deleted pages, Block user)
* Nouns describing what the page *is* (e.g. User rights management, Preferences)
* Nouns describing what the page *contains* (e.g. Wanted pages, blocked usernames and IP addresses).

I don't think this inconsistency is particularly problematic.
Comment 3 Aaron Schulz 2009-01-02 19:22:19 UTC

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