Wikibooks:Reading room/Archives/2019/November

Google Code-In will soon take place again! Mentor tasks to help new contributors!
Hi everybody! Google Code-in (GCI) will soon take place again - a seven week long contest for 13-17 year old students to contribute to free software projects. Tasks should take an experienced contributor about two or three hours and can be of the categories Code, Documentation/Training, Outreach/Research, Quality Assurance, and User Interface/Design. Do you have any Lua, template, gadget/script or similar task that would benefit your wiki? Or maybe some of your tools need better documentation? If so, and you can imagine enjoying mentoring such a task to help a new contributor, please check out mw:Google Code-in/2019 and become a mentor. If you have any questions, feel free to ask at our talk page. Many thanks in advance! --Martin Urbanec 07:28, 5 November 2019 (UTC)

Development environment for this wiki (take 2)
If I make a (Vagrant or Docker or VirtualBox) development for this wiki, would you be interested in including


 * 1. all gadgets or only some (if so then which)
 * 2. all extensions or only some (if so then which)
 * 3. all content or only some (if so then what part)
 * 4. all settings or only some (if so then which ones)

Also what extensions, or improvements to existing extensions, would you like to see developed if someone volunteers to do it. Is there a wish list.

Thanks, --Gryllida 05:10, 12 November 2019 (UTC)
 * It seems pretty simple to start from Docker, add the gadgets and import https://dumps.wikimedia.org/enwikibooks/ in an entrypoint. It would create a site which would reset easily to make some JS crash tests for example.
 * Actually I've just started a new book fr:Docker from scratch last month, and am willing to translate it here when the time will come. This exercise would create a good chapter of example. JackPotte (discuss • contribs) 21:12, 12 November 2019 (UTC)

Community Wishlist 2020
The 2020 Community Wishlist Survey is now open! This survey is the process where communities decide what the Community Tech team should work on over the next year. We encourage everyone to submit proposals until the deadline on November 11, 2019, or comment on other proposals to help make them better.

This year, we’re exclusively focusing on smaller projects (i.e., Wikibooks, Wiktionary, Wikiquote, Wikisource, Wikiversity, Wikispecies, Wikivoyage, and Wikinews). We want to help these projects and provide meaningful improvements to diverse communities. If you’re a member of any of these projects, please participate in the survey! To submit proposals, see the guidelines on the survey page. You can write proposals in any language, and we will translate them for you. Thank you, and we look forward to seeing your proposals! IFried (WMF) 19:30, 4 November 2019 (UTC)

Add a new template for internal book navigation
Dear all,

I'm new to Wikibooks but familiar with the German Wikiversity and the mediawiki software.

I'd like to add a new template (Template:OERlabs_Openbook: Template:Navigation) for internal book navigation like I did here (but I'm not sure if this is the way things are done here on the English version). Nevertheless, the system won't let me create it since my en.wikibooks.org account apparently is too young even though I've been editing on the German Wikiversity for some months.

Would it be possible to either give me the rights to create it myself or create a navigation template for me? I'd like to migrate the book in the next few days.

Oerlabs (discuss • contribs) 23:08, 26 November 2019 (UTC)


 * I see v:de:Projekt:OERlabs Openbook/Getting in/Getting on using template v:de:Projekt:OERlabs Openbook: Vorlage:Navigation. On English Wikibooks, Project:OERlabs Openbook would be an unusual name for a book; but, supposing for a moment that the book were in fact named that, the template would typically be called either Template:Project:OERlabs Openbook or Template:Project:OERlabs Openbook/navigation (or perhaps "nav" instead of "navigation").  For a similar example, see Template:Wikijunior:Solar System. --Pi zero (discuss • contribs) 04:31, 27 November 2019 (UTC)
 * I would like to add that you can't create templates yet as you are not autoconfirmed yet; it takes four days to happen, and after that you shouldn't have a problem. The MediaWiki:Titleblacklist blocks new users from doing so. I think the best thing to do is to wait for this to happen, but if you have problems please ask. -- Jules (Mrjulesd) 11:30, 27 November 2019 (UTC)

Bug in source code highlighting
The inline comment (from the line above) causes incorrect highlighting on the second  instruction.

Compare:

I haven't been able to reproduce the anomaly for other languages. GUYWAN (t &middot; c) 13:52, 23 November 2019 (UTC)
 * I can see it too, so we should report it on Phabricator. JackPotte (discuss • contribs) 13:54, 23 November 2019 (UTC)
 * What's weird is I can't see it, all the "push ax" and "push bx" examples look correct to me. But in the "mov ax, 006Ah" statement, the "006" bit is grey and the "Ah" is red, which doesn't seem right. Also looking at x86 Disassembly/Objects and Classes, many of those examples use the lang=asm attribute, and the coloring is all over the place. So there are definite problems that need reporting. But its strange that we're getting different things, and I think we must be getting different things from different servers.
 * Looking at the HTML, the push statements for me all seem to use the push ax or bx coding. Is this different for you?-- Jules  (Mrjulesd) 15:48, 23 November 2019 (UTC)


 * What's weird is I can't see it ... That's because put the comment on a new line, probably accidentally. Can you see it now? I can see the greyed-out "006", which is another issue I forgot to report. Regards, GUYWAN (t &middot; c) 15:23, 27 November 2019 (UTC)
 * oh yes that explains it. It is now visible to myself. It also shows up in the HTML. So in all its a pretty poor parser, it makes numerous errors both here and on other pages, and needs to be looked at by the Mediawiki folks. -- Jules (Mrjulesd) 00:17, 28 November 2019 (UTC)

Reported: GUYWAN (t &middot; c) 14:38, 28 November 2019 (UTC)


 * (A side remark on this, with apologies for the digression: I feel it's a microcosm for a profound conceptual error by the Wikimedia Foundation.  Their impulse is to maximize centralized control of things &mdash; a natural (unless consciously resisted) consequence of their structural role in the sisterhood &mdash; and that is fundamentally contrary to the nature of wikis.  A key property of a wiki is that if you're passing by and seem something wrong, you can just fix it; Wikipedia (for a classic example) could never have been built if anyone seeing a typo in need of fixing had to then petition a centralized body to please correct it.  Yet here we are, we see a problem and we have to petition a central org.  That's just not how it should be.) --Pi zero (discuss • contribs) 16:11, 28 November 2019 (UTC)