Wikibooks:Reading room/Archives/2022/May

css element
Does anybody know the name of the edit box element? I want to increase font-size. Thanks. L10nM4st3r / Roar at me 11:19, 6 May 2022 (UTC)


 * Sorry I don't quite follow you. Do you mean like mw:Extension:InputBox? I don't think you can alter the text size with it.
 * If this is incorrect please give me an example. -- Jules (Mrjulesd) 11:32, 6 May 2022 (UTC)
 * I mean the edit box when you click "edit", like when you edit a section or the whole page. It's the big one where you edit page content. I don't know if I can narrow that down any further. (Not the edit summary box) L10nM4st3r / Roar at me 12:04, 6 May 2022 (UTC)


 * oh I see. Well you have got some options available at Special:Preferences, but they don't affect the font size. Have you got browser zoom? On Firefox I can press  which zooms in on the browser window, and increases font size.
 * Otherwise it might be able to alter this in .  So in  your CSS something like   might work. -- Jules  (Mrjulesd) 13:06, 6 May 2022 (UTC)
 * I can zoom-in, but it doesn't keep that zoom once I leave the edit page, press reload or show preview. Even if I zom in, the whole page zooms in, instead of text size increasing, meaning that the text doesn't "wrap-around", if you know what I mean. It's not a massive deal. I made the "body" wider but comes with the side-effect that I can no-longer easily tap the place I want to. I will experement, however. L10nM4st3r / Roar at me 14:03, 6 May 2022 (UTC)
 * My device is grayscale, so redlinks look just like every other link. What is the id for those ones? Or how would I otherwise select it to change its style?L10nM4st3r / Roar at me 08:29, 10 May 2022 (UTC)
 * Red links seem to use the class = "new". So something like Example (looking at the HTML). -- Jules (Mrjulesd) 23:14, 10 May 2022 (UTC)
 * For those with a similar question, use  to select a redlink. L10nM4st3r / Roar at me 09:11, 11 May 2022 (UTC)
 * Not technical related, but please can you delete User:L10nM4st3r/monobook.css as its content has been copied onto my global meta css file. Please also delete User:L10nM4st3r/monobook.js.L10nM4st3r / Roar at me 09:25, 11 May 2022 (UTC)
 * ✅. -- Jules (Mrjulesd) 09:37, 11 May 2022 (UTC)

Editing news 2022 #1
Read this in another language • Subscription list for this multilingual newsletter

The New topic tool helps editors create new ==Sections== on discussion pages. New editors are more successful with this new tool. You can read the report. Soon, the Editing team will offer this to all editors at the 20 Wikipedias that participated in the test. You will be able to turn it off at Special:Preferences.

Whatamidoing (WMF) 18:55, 2 May 2022 (UTC)

Questionable embellishment
Hi, within the last year several embellishments & complications have appeared. These are some.
 * (1) At the top of every page there's a notice about video game strategy guides. Video gaming has no particular relevance to the pages I read and edit. I wonder why the notice is given precedence above most other information on every Wikibook page. Wouldn't a notice on the home page suffice?
 * (2) Previously (originally?) the left margin contained a list of links "Main Page, Help, Browse, Cookbook" & etc. Now a second possibility is to have the page contents there. But contents at the top of a page suffices. The expanding contents in mobile view also works. Is the contents in the left margin really beneficial?
 * (3) The page title is now at the top of the display, regardless of the location of the display in the page. An unfortunate consequence: when a link is used to position the display in the page, the title can obscure content. The front page of the Oberon book provides examples. The page URL is always displayed by the browser. Why should the title persist as a page is scrolled?
 * (4) JavaScript can be used when implementing new features. But JavaScript requires processing and processing requires time. Therefore new features can bring noticeable latencies in rendering.

The justification for new features is questionable. My general impression is that new features are beginning to interfere with content and rendering. Is there discussion or a vote before a new feature is implemented? Who implements a new feature? Salaried staff? Volunteers?

Sorry for ranting but this is an emerging concern. Regards, ... PeterEasthope (discuss • contribs) 18:09, 2 May 2022 (UTC)

Hi Peter


 * (1) Yes perhaps that's a bit unnecessary. It was brought in because we suddenly started accepting video game guides. Its been there a while now. But as an alternative, you could press the dismiss button to the right of the message get rid of it from your system.
 * (2) I think having the sidebar is valuable as it gives quick links on every page on the Wikibooks site, and I don't think it takes up a huge amount of space.
 * (3) on Oberon you are using to overwrite the default title. Is that what you mean? When I scroll the page the page title does disappear on my system.
 * (4) we do get some lags at times here. But I don't think that is due to Javascript, but rather due to bandwidth problems fom the servers (most likely).

Usually when new features are proposed and implemented here there is a discussion at Reading room/Proposals. But sometimes changes are brought in by the WMF that can't be questioned much. -- Jules (Mrjulesd) 20:01, 2 May 2022 (UTC)


 * (2) The sidebar is tolerable for links "Main Page, Help, Browse & etc." In 2022 Vector skin, page contents is also in the sidebar rather than at the top of the page.
 * (3) Yes, DISPLAYTITLE provides a title more meaningful than just "Oberon". To illustrate my observation, I go to footnote 43 at the bottom of the page. Click on "c". The display is relocated intending to show the text where footnote 43 is invoked. In my case, the title obscures the link "43". A screenshot is at http://easthope.ca/OberonWikibookScreenshot.png. The phenomenon is not specific to this footnote. The page has many instances.


 * The DISPLAYTITLE title follows down the page when I'm logged in and have 2022 Vector skin. When logged in with legacy Vector skin or not logged in, DISPLAYTITLE has effect only at the top of the page. (?) Strictly speaking, obscuration of a footnote citation is a bug, avoidable by staying with the Vector legacy skin. Then I question the benefit of multiple skins. Testing various skins and finding bugs wastes time. Why not simplify to one skin which works well? Appears that a volunteer or salaried employee wanted to do some programming.


 * According to Web principles, content is provided by the server. Style of presentation is the responsibility of the client. MediaWiki has become far too involved in presentation. An acceptable way to help readers with presentation is to provide style sheets. An ever-growing lists of user preferences is not good practice.


 * Thx, ... PeterEasthope (discuss • contribs) 14:40, 3 May 2022 (UTC)


 * [2] yes that's true.
 * [3] I think that is a problem with the 2022 vector skin in combination with using DISPLAYTITLE. It means when you press the footnote 43c link the resulting text is obscured as in your screenshot. There are three workarounds I can think of: (a) go back to Vector Legacy as your skin. (b) Stop using DISPLAYTITLE, which isn't strictly necessary and obscures the text. (c) Move text off the main Oberon page to a subpage (e.g. Oberon/Introduction), where you shouldn't get this problem. I think personally that the main book page should just be a table on contents, as I've done at Brief History of Europe. -- Jules (Mrjulesd) 18:33, 3 May 2022 (UTC)
 * [3] I think that is a problem with the 2022 vector skin in combination with using DISPLAYTITLE. It means when you press the footnote 43c link the resulting text is obscured as in your screenshot. There are three workarounds I can think of: (a) go back to Vector Legacy as your skin. (b) Stop using DISPLAYTITLE, which isn't strictly necessary and obscures the text. (c) Move text off the main Oberon page to a subpage (e.g. Oberon/Introduction), where you shouldn't get this problem. I think personally that the main book page should just be a table on contents, as I've done at Brief History of Europe. -- Jules (Mrjulesd) 18:33, 3 May 2022 (UTC)


 * [3] (a) I've switched to Vector Legacy. (b) Will investigate alternatives to DISPLAYTITLE. (c) The front page entirely a table of contents is a good idea, technically. Pictures mitigate drabness and inspire interest. The photo of the Brandenburger is impressive. Will think about changing the Oberon book. Thx, ... PeterEasthope (discuss • contribs) 19:06, 3 May 2022 (UTC)

New competition on English Wikipedia and related SiteNotice request
A popular article writing competition CEE Spring (about Central and Eastern Europe; now with special subcategory about Esperanto) is happening on the English Wikipedia until the 31st May 2022. I warmly invite you to participate, write some article and win a valuable prize! If you have question, I will happily answer it on the competition page talk.

Also, for more wide outreach, I have just asked for a CentralNotice, which should appear also in this project. If you have a comment on the request, you are welcome to write it on the request page. --KuboF Hromoslav (discuss • contribs) 18:29, 3 May 2022 (UTC)

Wikimedia Foundation Board of Trustees election 2022 - Call for Election Volunteers

 * You can find this message translated into additional languages on Meta-wiki.
 *  m:Special:MyLanguage/Movement Strategy and Governance/Election Volunteers/2022/Call for Election Volunteers • 

The Movement Strategy and Governance team is looking for community members to serve as election volunteers in the upcoming Board of Trustees election.

The idea of the Election Volunteer Program came up during the 2021 Wikimedia Board of Trustees Election. This program turned out to be successful. With the help of Election Volunteers, we were able to increase outreach and participation in the election by 1,753 voters over 2017. Overall turnout was 10.13%, 1.1 percentage points more, and 214 wikis were represented in the election.

There were a total of 74 wikis that did not participate in 2017 that produced voters in the 2021 election. Can you help increase the participation even more?

Election volunteers will help in the following areas:
 * Translate short messages and announce the ongoing election process in community channels
 * Optional: Monitor community channels for community comments and questions

Volunteers should:


 * Maintain the friendly space policy during conversations and events
 * Present the guidelines and voting information to the community in a neutral manner

Do you want to be an election volunteer and ensure your community is represented in the vote? Sign up here to receive updates. You can use the talk page for questions about translation.  --Mervat (WMF) (discuss • contribs) 08:32, 10 May 2022 (UTC)

Let's talk about the Desktop Improvements
Hello!

Have you noticed that some wikis have a different desktop interface? Are you curious about the next steps? Maybe you have questions or ideas regarding the design or technical matters?

Join an online meeting with the team working on the Desktop Improvements! It will take place on 17 May 2022 at 12:00 UTC and 19:00 UTC on Zoom. Click here to join. Meeting ID: 86217494304. Dial by your location.

Agenda


 * Update on the recent developments
 * Questions and answers, discussion

Format

The meeting will not be recorded or streamed. Notes will be taken in a Google Docs file. Olga Vasileva (the Product Manager) will be hosting this meeting. The presentation part will be given in English.

We can answer questions asked in English, Italian, Polish; also, only at the first meeting: Farsi, Vietnamese; only at the second meeting: Portuguese, Spanish, Russian. If you would like to ask questions in advance, add them on the talk page or send them to sgrabarczuk@wikimedia.org.

At this meeting, both Friendly space policy and the Code of Conduct for Wikimedia technical spaces apply. Zoom is not subject to the WMF Privacy Policy.

We hope to see you! SGrabarczuk (WMF) (talk) 05:02, 14 May 2022 (UTC)

Report on Voter Feedback from Universal Code of Conduct (UCoC) Enforcement Guidelines Ratification
Hello all,

The Universal Code of Conduct (UCoC) project team has completed the analysis of the feedback accompanying the ratification vote on the Universal Code of Conduct Enforcement Guidelines.

Following the completion of the UCoC Enforcement Guidelines Draft in 2022, the guidelines were voted on by the Wikimedian community. Voters cast votes from 137 communities, with the top 9 communities being: English, German, French, Russian, Polish, Spanish, Chinese, Japanese, Italian Wikipedias, and Meta-wiki.

Those voting had the opportunity to provide comments on the contents of the Draft document. 658 participants left comments. 77% of the comments are written in English. Voters wrote comments in 24 languages with the largest numbers in English (508), German (34), Japanese (28), French (25), and Russian (12).

A report will be sent to the Revision Drafting Committee who will refine the enforcement guidelines based on the community feedback received from the recently concluded vote. A public version of the report is published on Meta-wiki here. The report is available in translated versions on meta-wiki. Please help translate to your language

Again, we thank all who participated in the vote and discussions. We invite everyone to contribute during the next community discussions. More information about the Universal Code of Conduct and Enforcement Guidelines can be found on Meta-wiki.

On behalf of the Universal Code of Conduct project team --Mervat (WMF) (discuss • contribs) 21:39, 23 May 2022 (UTC)

Next steps on the Universal Code of Conduct (UCoC) Enforcement guidelines
Hello all,

I’d like to share an update on the work on the Enforcement guidelines for the Universal Code of Conduct.

In 2022 May, the Universal Code of Conduct (UCoC) project team completed a report on the 2022 March ratification vote about the guidelines. Voters cast votes from at least 137 communities. At least 650 participants added comments with their vote. A report is available on Meta-Wiki. (See full announcement)

Following the vote, the Community Affairs committee (CAC) of the Wikimedia Foundation Board of Trustees asked that several areas be reviewed for improvements. A Revision Drafting Committee will refine the enforcement guidelines based on community feedback.

To help the Revisions committee, input from the community is requested. Visit the Meta-wiki pages (Enforcement Guidelines revision discussions, Policy text revision discussions) to provide thoughts for the new drafting committee. (See full announcement)

Let me know if you have any questions about these next steps. --Mervat (WMF) (discuss • contribs) 07:24, 28 May 2022 (UTC)

Invitation to join the Movement Strategy Forum
Hello everyone,

This is an invitation to all Movement Strategy participants to try out a new space for truly multilingual collaboration: https://forum.movement-strategy.org/

We are starting a community review period of two months. If the community feedback is positive, the Forum will launch in August 2022 before Wikimania. If not, we will follow the feedback received, changing the proposal or closing it.

https://meta.wikimedia.org/wiki/Movement_Strategy/Forum/Proposal

Looking forward to your first impressions!

Mervat (WMF) (talk) 10:01, 31 May 2022 (UTC)

Copyright problems at cookbook
Hi and anyone else this is relevant to:

Unfortunately we have had to delete some recently created pages as copyvios (copyright violations):


 * Cookbook:Bitterleaf soup(ofe onugbu), as a copyvio of https://www.allnigerianrecipes.com/soups/bitterleaf-soup/
 * Cookbook:Gbegiri (Yoruba Bean Soup), as a copyvio of https://shop4younow.com.ng/en/south-western-cuisine/163-eforiro-edikainkongshoko-soup.html
 * Cookbook:Ogbono soup, as a copyvio of https://mamaspalms.wordpress.com/2016/08/09/ogbono-soup/

As far as I'm aware none of these pages have compatible licenses with ours, so direct copying is prohibited.

Please be aware of our Copyrights policy. When you create a cookbook page you get an edit notice that states "STOP NOW from directly copying a published recipe. Doing so is a copyright violation, and it WILL BE DELETED, and administrative action can be taken against offenders. Over half of recipes created here are copyright violations and end up deleted. If you claim to own the copyright please follow the instructions at WB:DONATE first. "

Please share this message with cookbook contributors this may affect. -- Jules (Mrjulesd) 23:49, 4 May 2022 (UTC)


 * @Mrjulesd Thanks for the notice. I and @B.Korlah has brought it to their attention. Well will take further actions to ensure it doesn't happen again. Edriiic (discuss • contribs) 06:18, 5 May 2022 (UTC)

Hi @User:Mrjulesd, thank you for this information, this information has been passed across to new editors of Wikibook:Cookbook, I hope that would stop from henceforth. Kind regards — Preceding unsigned comment added by B.Korlah (talk • contribs)


 * thanks very much for that. For what is allowed please see https://copyrightalliance.org/are-recipes-cookbooks-protected-by-copyright/ . Basically, direct copying of recipe text (copy/paste or otherwise) is generally prohibited, although copyright protection doesn't cover the ideas expressed in recipes. In other words, recipes should always be in the own words of contributors, unless the source has a compatible license (which isn't usually the case). -- Jules (Mrjulesd) 08:24, 5 May 2022 (UTC)