(change visibility) 18:08, 22 June 2017 MarcoAurelio (talk | contribs | block) changed status for global account "User:SJ81 bis@global": set locked; unset (none) (as per user request in phab:T167982 due to security concerns)
@bd808 It currently reads on the Main Page: Wikimedia Cloud Services. Hosting environment for community managed software projects, tools, and data analysis. If there's another wording you'd like to use, please let me know. Regards.
If it is modifying the main page or one of its protected pages I can do it or we can grant you temporary adminship to do it yourself, or if you have a staff account with the appropriate rights I think it'd not be an abuse to do it from that account either (but you should check with your manager that).
@jrbs There's a script in MediaWiki core that allows resetting username and password for an account. If the problem is that you cannot be convinced by the evidence of the edit linked here that this account belongs to the requestor then I have no objections but if it is for technical restrictions then please have a look at resetUserEmail.php and changePassword.php.
Thu, Jun 15
Question: all other requests to have 2FA or credentials reset (at least those I've participated in) where marked as private. Should we mark this as private too? I'm looking for some sort of standard criteria for further requests. Thanks.
Unfortunately busy days are ahead and I'll not be able to handle this request. My plan is to decide if we really want to rename, and if so, then coordinate with @Marostegui so the renamer and him can be around checking DBs and all that.
Tue, Jun 13
Mon, Jun 12
Was there any discussion when they set it to pt? No.
No comments on that thread means the patch can go forward?
- create the ACL requested at T167584: Create several (sub)projects for Wikimedia Venezuela
- set rWMVE edit/push to repo-admins and that acl.
Sun, Jun 11
Adding Phabricator as only admins can create ACLs, as the options for that are locked for regular users.
- Description: Coordinate technnical tasks in Wikimedia Venezuela' Servers
- Type: Group
- Project policies: ACL Project (can edit/join: Allow members of #wikimedia-ve-tech)
@White-Master So you need a project called #Wikimedia-VE-tech and their members allowed to manage that project, right?
Thu, Jun 8
Global rename is now done. Thanks to @Marostegui for his help during the rename for supervising the DBs.
Being handled in a minute.
Wed, Jun 7
Tue, Jun 6
If 'RecipientUser' => null, how https://nl.wikipedia.org/wiki/Speciaal:Contactpagina delivers the messages then? I've been looking for the config for that project but couldn't find it. Thanks.
Mon, Jun 5
Thu, Jun 1
Wed, May 31
As the route indicates, it's a problem with the script located in the shared pywikibot files of Tool Labs, or at least it seems to me that. Thanks.
Tue, May 30
May 20 2017
We use centralauth-log-entry-chgstatus since several years now. I'd certainly prefer using old messages but it is what it is. I've tried to search the commit where the new message was introduced, but without success. Maybe others know how to. Closed as invalid.
May 18 2017
Those messages are deprecated and are kept for backwards compat iirc.
May 15 2017
The flow-bot right exists on flow.dblist wikis that have the
flow-create-board permission. I don't think there's a need to create a new
group nor assign it globally to anyone. Just rename flow-bot to
flow-creator or assign flow-create-board permissions to administrators on
May 10 2017
I'm not sure how I can provide any answer. I am not a coder, developer or mantainer of the extension.
Change broke namespaces (things that worked and now ain't was a valid rationale for UBN tasks). This should be reverted and/or fixed in the next SWAT window if at all possible.
May 8 2017
May 7 2017
Hello. What's the status of this one? It'd be interesting to have our mailing lists system updated. Regards.
May 4 2017
T131963: Complete eswiki edit quality campaign is the same as this one. Suggesting to merge this one onto ***63 as duplicate.
Questions that come to mind
- How do people know that they need to sign a document online?
As former acl*otrs-admins member, signatures can be viewed and verified at the https://phabricator.wikimedia.org/legalpad/signatures and using the "Query" button, you can filter which document signatures you'd like to see and check. I've had a bit of interaction with the feature so if there's any question I'm able to answer feel free to ask. Regards.
May 3 2017
May 2 2017
Portal / Portal discusión
I think users should be free to decide what to do with their directories as long as they don't violate labs ToU. The right to fork policy is not automatic but conditional in that the committee has to approve it, and certainly some of us only use of Labs to run a bot and whose only "original" files are those who ain't included or avalaible to fork or our privacy would be compromised. Given that use, it makes perfect sense to have a directory closed notwithstanding your problem in that if you ever run into problems you cannot be helped so much. But that's the owner's choice. In the case a tool is misbehaving or being harmful, any admin can shut it down and look into it, which are really the people we trust to help mantain Tool Labs run smoothly and that can have access already in a need-to-know basis. Thank you.
The task is already finished with the template replaced so I'm done here. Thank you to everyone who have helped. Maybe T154011 is the solution for this, I don't know.
@zhuyifei1999 Sorry but I'd like to keep my project closed to my eyes only and the admins if they ever need to see what's going on there. However you can see in the description which command I'm using for the task and to submit the job. I'll repeat it here nonetheless.
@Jseddon Given that Phabricator forms do exist now, we could request one from @mmodell. Projects are not normally subscribers of a task, but watchers of a project will receive a mail/notification if/when a task in this board is created or changes.
Boldly closing since the campaing is resolved.
I think this campaign has already finished.
Thanks @Legoktm. I am not sure if there's a pywikibot option for the template.py script or others that forces the bot to retry when they trigger the readonly error. I didn't knew that maxlag thing you mention. Following mw:Maxlag, I decided that '3' was a nice value given that '5' was the standard one. I can try reduce it from 3 to 2 or 1 if that'd help, and also make the bot wait more time between edits, although I think 15 seconds between each is acceptable. Maybe we should have @jcrespo investigate if there's something that is lagging the eswiki DB so much, and I'd also appreciate if @Xqt or @jayvdb, which are very experienced python developers could weight in and see if an option for retrying a job when the readonly error is triggered is already there or could be developed. Regards.
May 1 2017
StewardBot parses the log using a regex which detects which permissions got
added and removed. If we were to implement that it'd require a rewrite of
that and that's something I do not know how to do as I have no idea of
Python, in which the bot is written. Stalled for now. Being realistic the
only maintence happening on this project has been me and @bd808 when
required. Being myself retired from MediaWiki development, at least
temporary, unless Bryan figures out a way to achieve this, this will not be
resolved soon. IIRC a whole rewrite for the bot was planned but I don't
know the status of that goal.
Apr 25 2017
@Dvorapa: would you please tell me how to do that? I am new to the PAWS
Apr 24 2017
Please advice if usermerge or local usurpation is desired here.