Page MenuHomePhabricator

Listadmins for commons-l
Closed, ResolvedPublic

Description

The listadmin is atm Avatar [Commons-l list run by wikipedia-listadmin at computerkultur.org]. He is inactive (desysopped because inactivity time ago - https://meta.wikimedia.org/w/index.php?oldid=1593048#Inactive_.40_Commons) not responding to mails etc.

I request to set up two new listadmins.

Thank you


Version: wmf-deployment
Severity: enhancement

Details

Reference
bz68680

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 3:41 AM
bzimport set Reference to bz68680.
bzimport added a subscriber: Unknown Object (MLST).

(In reply to Steinsplitter from comment #0)

The listadmin is atm Avatar [Commons-l list run by wikipedia-listadmin at
computerkultur.org]. He is inactive (desysopped because inactivity time ago

not responding to mails etc.

I request to set up two new listadmins.

Thank you

Hey Steinsplitter,

For a change like this we generally need some kind of community consensus. I'm open for debate if someone feels otherwise but I personally would be happy with a consensus of those interested either on the mailing list itself or on wiki since it's a project based list.

I don't like to start a RFC because of a list. Not sure if it make sense to have someone as listadmin who has edited 2012 the last time and who is no longer a commons sysop.

(In reply to Steinsplitter from comment #2)

I don't like to start a RFC because of a list. Not sure if it make sense to
have someone as listadmin who has edited 2012 the last time and who is no
longer a commons sysop.

Please calm down. I guess the RFC is asked to decide the *new* listadmins, and not to remove the current inactive one.

The bug, as it is now, can't be worked, because you requested to set up two new listadmins, but you didn't say *who* are those new listadmins. The decision of who should be listadmin is what requires community consensus.

Sorry? Please note i am not native speaker and i was never claimed up.
I did not think that it requires so much bureaucracy. O_o

It's not "much bureaucracy" (plus bureaucracy traditionally is not a bad word). It's about creating public consensus who should be list admin *instead*.

(In reply to James Alexander from comment #1)

For a change like this we generally need some kind of community consensus.
I'm open for debate if someone feels otherwise but I personally would be
happy with a consensus of those interested either on the mailing list itself
or on wiki since it's a project based list.

Agreed. Well said.

My recommendation would be to find two to three list moderator candidates and start a discussion on the associated mailing list. If there are no objections and the candidates seem broadly acceptable to the mailing list participants, the candidates should be made list moderators.

(There may be a subtle distinction between "list administrators" and "list moderators" though who knows.)

wikipedia wrote:

Hi guys,

Avatar here - Casey Brown notified me about this discussion. Sorry if I'm hard to reach. If there is anything I can do from my side to ease up the situation/help let me know. Due to time restraints I won't be able to restart "active duty" as listadmin but happy to "hand over the torch" when we do have some consensus.

Bye, Avatar.

(In reply to Tim Bartel from comment #7)

Hi guys,

Avatar here - Casey Brown notified me about this discussion. Sorry if I'm
hard to reach. If there is anything I can do from my side to ease up the
situation/help let me know. Due to time restraints I won't be able to
restart "active duty" as listadmin but happy to "hand over the torch" when
we do have some consensus.

Bye, Avatar.

Thanks Avatar,

Once new admins are found (I know a discussion has been started on list) if you're able to help that would be great. Essentially you would need to hand them the password (since it's shared) and without you I would have to create a new password and reset it.

Hey guys, was this dealt with? (so we can close it) I know in July a discussion was going to happen on the list.

Hey guys, was this dealt with? (so we can close it) I know in July a discussion was going to happen on the list.

There was only one reply to my mail (https://lists.wikimedia.org/pipermail/commons-l/2014-July/007270.html) :(

how about we just add Steinsplitter and Jalexander then ?

14:16 -!- Channel Commons created Sat Nov 25 22:43:08 2006
14:16 -!- Irssi: Join to Commons was synced in 1 secs
14:16 < mutante> he, we need some list admins for commons-l
14:17 < mutante> any volunteers could say so on https://phabricator.wikimedia.org/T70680

Just for the record, I'd volunteer as a stand in as I'm experienced with Wikimedia's mailman (list creator as well) so while Commons decide on an actual list admin - I wouldn't mind managing it and then implementing the consensus if any is reached.

[if needed]

Hi!

If you need more volunteers to manage the list, add me.

Alan

PS: Steinsplitter, this task has your name :-P

I keep an eye on commons-l and would be happy to help moderate it. I know how to use the system from managing other lists.

Hi all, thanks for volunteering, that worked out nicely:) I would add all 3 of you, but i need email addresses please, and unlike in BZ i can't see them here.

I added John Lewis and Steinsplitter as temp. admins, because i knew their email from Gerrit and John has done a lot of mailman related things. He can handle it from here and reset/share the pass. Note there is only a single admin pass that needs to be shared between you guys.

This comment was removed by Alan.

Perfect! will be good admins! :-)

i reset the password to something generated and sent it to commons-l-owner@lists.wikimedia.org

people added as admins can be reached under that alias automatically

Dzahn claimed this task.