Last modified: 2014-11-17 10:36:11 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 43302 - Drop the term "autoconfirmed" from user interface
Drop the term "autoconfirmed" from user interface
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Low enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: design, i18n
Depends on:
Blocks: messages
  Show dependency treegraph
Reported: 2012-12-20 17:11 UTC by Nemo
Modified: 2014-11-17 10:36 UTC (History)
8 users (show)

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


Description Nemo 2012-12-20 17:11:57 UTC
(Split from bug 43272 comment #13)
> Yes I would prefer changing it everywhere where it is used, and it can be
> done
> as separate thing. We already have similar case for sysop -> Administrator so
> it is possible.

The problem is that we don't have a non-jargon term for "autoconfirmed", for the very good reason that all community members are supposed to be autoconfirmed, although some wikis are more restrictive than others and stretch the concept a bit more (too much).
We have some established terms for non-autoconfirmed, though: 'newbie' (also valid in code), [[m:Newly registered user]].

In core:
'group-autoconfirmed' => 'Autoconfirmed users',
'group-autoconfirmed-member' => '{{GENDER:$1|autoconfirmed user}}',
'grouppage-autoconfirmed' => '{{ns:project}}:Autoconfirmed users',
'protect-level-autoconfirmed' => 'Block new and unregistered users',

Note that Wikimedia projects also have a "confirmed" group by default (that can be added by stewards).
Comment 1 Platonides 2013-01-10 22:54:54 UTC
Bug 43272 suggested "Established users" as a replacement for Autoconfirmed.

Note that newbie is everyone not autoconfirmed (or with an equivalent access permission), defined as such by core mediawiki (User::isNewbie).

It is also mentioned in:
'group-autoconfirmed.css' => '/* CSS placed here will affect autoconfirmed users only */', # only translate this message to other languages if you have to change it
'group-autoconfirmed.js' => '/* Any JavaScript here will be loaded for autoconfirmed users only */', # only translate this message to other languages if you have to change it

Although those entries are more technical.
Comment 2 Matthew Flaschen 2013-01-17 16:38:06 UTC
It's definitely jargon, and probably somewhat unfriendly to new users.  A term like "established" could be better, but we need to make clear that it still has a special technical meaning (not just a subjective view of who is established)

Also, we would need to decide about the confirmed group.  Do we distinguish "established" and "autoestablished", or perhaps "manuallyestablished" and "established"?
Comment 3 Platonides 2013-01-28 09:55:13 UTC
This is a personal preference but... I find manuallyestablished an ugly word :)
Comment 4 Matthew Flaschen 2013-01-28 16:41:31 UTC
I agree. :) It wasn't meant to be an ideal term, but mainly food for thought.

However, "confirmed" (the current equivalent to "manuallyestablished") isn't used that much in practice, so the term doesn't need to be perfect.
Comment 5 Nemo 2013-01-28 17:41:58 UTC
"Confirmed" isn't used much, but perhaps should be used more; in my experience, very few know what it is about. Clearer terms would surely be a good thing.
Comment 6 Dan Garry 2014-04-29 14:43:14 UTC
Perhaps the User Experience team might have some ideas.

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