User talk:BDavis (WMF)/Archives/2019
|Please do not post any new comments on this page. This is a discussion archive first created in 2019, although the comments contained were likely posted before and after this date. See current discussion or the archives index.
Timeless Newsletter • Issue 4
Welcome to the fourth issue of the Timeless newsletter, with a cat! Or maybe not.
Un chat qui miaule???
It's true! The angry cat, a fundamental part of Timeless, has resulted in confusion and bug reports all across the projects and phabricator. And now it shall be immortalised forever in the new, shiny Timeless logo.
After putting off the project for three months because I got hit in the head with a flight of stairs, and then putting off the project for another two months while working out what the status of the grant was, I have now put off the project even more in order to focus on my other project for a bit. So progress lately has been a bit whims-based as a result:
- The project now has a logo. For some reason.
- The angry cat in the background is now customisable! Behold: not a cat. What would you like to replace it with on your project?
- I broke, unbroke, and then sort of sideways broke all the form styles. Help.
- The French Wiktionary voted to set Timeless as their default skin, with results possibly as you might expect: I ran away and hid, and the WMF said no. A bit of discussion later and we largely agreed that all else aside, this is a bit of a branding issue, but we love the enthusiasm! Also the bug reports that inevitably come out of such a discussion. I'm still working on properly going through those.
- Theme support is still stuck in limbo, but now we have another skinning RfC. tl;dr, we wanna replace the entire skinning system, and Skizzerz'll write a prototype later.
I will be fully resuming work on Timeless next week, or maybe the week after, depending on what madness (or illness) comes out of the Hackathon in Prague. Please come talk to me there to discuss strategy!
Regarding approved OAuth apps for Gdrive-to-Commons app
Thank you for approving all the OAuth consumers which were created while developing https://toolsadmin.wikimedia.org/tools/id/google-drive-photos-to-commons. However, I was trying to get them removed from the system somehow actually. Awaiting for https://phabricator.wikimedia.org/T65712 to happen so that I can revoke my consumers myself. In the meantime, can we have the following consumers revoked/deleted ?
Said that, the one we are trying to get approved is: https://meta.wikimedia.org/w/index.php?title=Special:OAuthListConsumers/view/bf7acc95275ac2e73380b7a039f14891&name=&publisher=01tonythomas&stage=0. This is the one pointing to the instance at https://tools.wmflabs.org/google-drive-photos-to-commons. Tack. 01tonythomas (talk) 11:03, 25 May 2019 (UTC)
Dear Bryan Davis,
Thank you for approving my application for Toolforge. However, when I click on https://toolsadmin.wikimedia.org/tools/ , it still suggest me to apply for membership. Can you tell me how can I access the tool? --Wmr-bot (talk) 08:48, 31 July 2019 (UTC)
- @Wmr-bot: this is a bit of a bug in the toolsadmin interface. The fix is to log out there and then log back in. The application only updates your account's rights on login. --BDavis (WMF) (talk) 15:28, 31 July 2019 (UTC)
Hi @BDavis (WMF):, thank you for approving the app https://meta.wikimedia.org/wiki/Special:OAuthListConsumers/view/63edb156c538d3328d5aca509937472c (WikiLoop Battlefield Dev Local). A wikipedian expressed interest in helping out the project, can I share the Oauth application permission with them? Xinbenlv (talk) 18:25, 29 August 2019 (UTC)
- @Xinbenlv: I think that is a reasonable thing to do. They can also make their own localhost grant request as well, but there is some precedent for development teams sharing a set of localhost grants to make on-boarding folks to assist in a project easier. Do be aware that anyone you share the grant's secrets with has the potential ability to make edits to the wikis as anyone who has authorized the grant to work with their account, so treat the secrets as secrets when sharing them with others and make sure that you all agree on the level of trust/protection needed to maintain trust in your project. --BDavis (WMF) (talk) 18:32, 29 August 2019 (UTC)
Timeless Newsletter • Issue 5
Welcome to the fifth and final issue of the Timeless newsletter!
Progress was made. True story.
I am happy to announce that after about a year, this delightful project in which absolutely nothing has gone according to plan is coming to a close. Or at least, the grant-funded portion is. Which means we will now be resuming our regular schedule of random whims-based development, you probably won't notice any difference whatsoever unless you use MonoBook, and there's a report.
What's new from the past two months:
A lot less than we'd hoped, frankly. We:
- Fixed various bugs, some of which even weren't for stuff I'd just broken two patches previously.
- Resolved sundry compatibility issues for other extensions, templates onwiki, whatever, largely by removing dumb crap from the css.
- Implemented some shiny new features you'll probably hate or just never use or actually see, like click-toggled dropdowns, icons everywhere, and options to select a default layout or set an image for the site header wordmark.
- Brought the total number of open tasks on the Timeless workboard down to 70.
We also wound up with:
- Patches resulting in RelatedArticles working in MonoBook, and FlaggedRevisions showing up in Minerva, unless someone actually managed to turn that off as well. (Blame T181242.) It's possible we went a little overboard with the whole 'let's close all the tasks!' sprint.
- An unfortunate repeated discovery that themes (the Night/Winter variants I keep insisting will happen at some point) are still pretty far off on the horizon. Um.
- Possibly a quite a few more bugs coming your way. This month, and especially the past week, have been a bit of a mess, development-wise. While hopefully none of the worse issues make it to production, please keep the reports coming for whatever you do find and we'll get it fixed as soon as we can. Y'all've been amazing about this, and it's really appreciated.
And I guess that's that. I'm really bad at reporting, and this is a report. For the purposes of the grant, this was a requirement, but do you want me to keep trying to send these out?
tools forge pip
I want to convert jpg to pdf for uploading to Wikimedia Commons. The convert command in Linux always breaks down and I want to use img2pdf (pip install img2pdf). However, pip is not installed. Is there a way to install pip and img2pdf? Do I have to get a super user rights?--Wmr-bot (talk) 10:37, 5 September 2019 (UTC)
- @Wmr-bot: you need to create a Python virtualenv environment so that you can use pip local to that environment rather than global to the virtual machine you happen to be using. We do not seem to have really great documentation on doing this in a general case, but wikitech:Help:Toolforge/Web#Using_virtualenv_with_webservice_shell covers a specific way to setup a virtualenv that works with Python3 webservices. --BDavis (WMF) (talk) 15:01, 5 September 2019 (UTC)
Although there are 8 cores in the server, it runs much slower then my own laptop. Any idea on how to speed it up? I am already using multiprocessing in python to speed up.--維基小霸王 (talk) 12:15, 22 September 2019 (UTC)
- @維基小霸王: The 8 cores are shared with a number of other processes (how many depends on where your job is running and what other workloads are running at the same time). Your tool's $HOME is also located on an NFS server that is handling I/O for all other Toolforge tools at the same time. This access is rate limited on each exec node in an attempt to prevent the NFS server's disks from being monopolized by a single tool. Things that need to read/write to $HOME will be slower than any single user system like a local laptop by design.
- One of the main things to think about is how to make it so that your tool can do the work it needs to do slowly, but continuously rather than quickly and immediately. That is a more "scalable" way to think about building tools. --BDavis (WMF) (talk) 21:32, 23 September 2019 (UTC)