Write an account created template mail for fishbowl and private wikis
Open, Needs TriagePublic
Actions

Assigned To

None

Authored By

	Dereckson
	Jul 18 2017, 8:37 AM

Description

Twice a row, users requesting a new wiki and getting it as fishbowl/private was puzzled they don't have any administrator capability.

They ignored the bureaucrat is basically only a promote account and others rights belong to administrator, and as they thought any bureaucrat was administrator, they didn't promote themselves or asked their group for that.

There are also two other elements to communicate:

change your password
if you've an exception, ask on IRC for live debug, or give the error id if any

So we should prepare a mail with all this content, publish it somewhere on wikitech as a template to use.

Event Timeline

Dereckson created this task.Jul 18 2017, 8:37 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 18 2017, 8:37 AM

Another way is to run mwscript createAndPromote.php --wiki=wiki --sysop
--bureaucrat instead of only --bureaucrat. I really think this is more easy
than requesting selfpromotions.

Why assume the person we trust to create accounts want / have the support
of the local group for a sysop access?

In the traditional power balance of Wikimedia projects, the responsibility
to promote sysops are shared between stewards and local bureaucrats, but
not devs/sysadmins/etc.

If we trust somebody to be able to promote users to sysop status we must
trust him to be a sysop.

Reasons:

He can promote himself at any time
At a lot of public wikis there is a rule that a bureaucrat must have sysop expierence previously to be able to request the rights

In another words we can't assume the user group wish somebody to be a
bureaucrat and don't want the same somebody to be a sysop.

Okay. Furthermore, would they want to create another user to give sysop
right, they need for that to be sysop.

biplabanand subscribed.Jul 18 2017, 11:55 AM

Then just do not give them any accesses or just give them sysop but not bureaucrat access. Giving them bureaucrat permissions allows the user to self-promote themselves and promote anyone they wish as @Urbanecm rightly pointed, so I don't see the issue with only sysop access as what we're doing currently not only allows the user to grant sysop to himself but to anyone else. Not that it is much of a concern as fishbowl wikis are managed by their closed groups on the other hand. If the script supports the option and we want to play safe, maybe the account should be created with no special rights so it can just create accounts and ask stewards to promote accounts once it is verified that the user has indeed support to fulfill that role?

Hello $username,

An account at $sitename has been created for you as requested with the following login credentials:

* Username: $username
* Temporary password: $password

The first time you login you'll need to change this temporary password. This is important.

Since the wiki has just been created it is possible that you run into errors or system exceptions. If you experience any of those please get in touch with us at $phabricator_createtask_link (prefered) indicating the full error message you receive, or you can ask for live debug at $irc_channel_link

This message has been sent by an automated process. Do not reply to it.

Kind regards,
$sysadmin name

Write an account created template mail for fishbowl and private wikisOpen, Needs TriagePublicActions

Description

Event Timeline

Write an account created template mail for fishbowl and private wikis
Open, Needs TriagePublic
Actions