Jump to content

User talk:Mike Peel

Add topic
From Meta, a Wikimedia project coordination wiki
(Redirected from User talk:Pi admin bot)
Latest comment: 1 month ago by Yodin in topic English Wikisource concerns

Welcome to my talk page. Please post new messages at the bottom of my talk page, use headlines when starting new talk topics and sign and date your entries by inserting ~~~~ at the end. I will generally reply on this page to keep conversations together; please watch this page for a short time after leaving a comment. Uncivil comments will be reverted without response. Thank you.

Start a new talk topic.

If you would prefer to contact me off-wiki, then my contact details and a contact form are available on my personal website.

Pi Bot

[edit]

Can your pi_bot scour Wikisource for "wikidata=" to add entries to Wikidata? See for example wikisource:The History of Polk County, Iowa/Hahnen, J. F. has the Qid at Wikisource, but not at Wikidata. Same for portals. wikisource:Portal:Carl Henry Schneider has the qid at Wikisource and the bot needs to add it Wikidata. Can you ping me, or write me at Wikisource? Also surname categories need to link from Wikidata. See: wikisource:Category:McPheeters (surname). --Richard Arthur Norton (1958- ) (talk) 01:39, 14 November 2024 (UTC)Reply

English Wikisource concerns

[edit]

Dear Mike, I'm contacting you as one of the WMF's community trustees in the hopes that you might be able to help resolve concerns the English Wikisource community have about technical issues that would be caused by the planned deployment of the Vector 2022 skin there next week. This is one of the last Wikis not using the new skin, because of unfixed bugs that were raised months ago and are still not addressed.

I've posted the details to the Wikimedia Foundation Board noticeboard, and understand that the WMF's web team are likely to have many other priorities at the moment, but hope that there's a way to ensure that the Wikisource community's voice is not ignored, and ideally some guarantees that the web team can be given the resources they need to be able to fix the technical issues the community has raised, before Vector 2022 is deployed.

Sorry if this is not the right way to go about this, and any help or advice you and the other community trustees can give would be much appreciated! Many thanks! --YodinT 23:37, 21 November 2024 (UTC)Reply

Thanks for the message. I know your post on the noticeboard has been seen, and there's a Conversation with Trustees call on Wednesday that you might be interested in attending.
With my tech volunteer hat on, I've been investigating some issues blocking Vector 2022 on other wikis, e.g., phab:T366607 for Wikidata. Is there a similar Phab ticket for tracking issues with its deployment on enwikisource? If not, I suggest creating one, since that's the place that the tech development community works at. I also have the skin enabled myself, and haven't spotted any particular issues on enwikisource, but I haven't managed to be active there for a while. In Preferences-> Appearance I recommend turning off "Enable limited width mode", which helps a lot when proofreading pages. Thanks. Mike Peel (talk) 17:15, 22 November 2024 (UTC)Reply
Sorry for the slow reply, and I've now raised the suggestions you made with the rest of the community; I hope that we'll have someone to attend the conversation call (not sure I'd be the best person to do this, but will try if necessary!) Have also made a start outlining what the Phab epic sub-issues would be, and will create it as a ticket if there aren't any objections (unless the Web Team get around to this first!) Thanks for responding and the practical advice; much appreciated. --YodinT 03:19, 25 November 2024 (UTC)Reply