“ Editing of sitewide CSS/JS is only possible for interface administrators from now (Please help translate to your language)
Hi all,
as announced previously, permission handling for CSS/JS pages has changed: only members of the interface-admin (Interface administrators) group, and a few highly privileged global groups such as stewards, can edit CSS/JS pages that they do not own (that is, any page ending with .css or .js that is either in the MediaWiki: namespace or is another user's user subpage) . This is done to improve the security of readers and editors of Wikimedia projects. ”

“ CC-BY 4.0 as default license in upload forms I suggest that CC-BY 4.0 should be the default suggested licensing when using the upload forms in Wikimedia projects for own works, instead of the current CC BY-SA 4.0 license (example at Commons) , sometimes with dual GFDL licensing (example here at Wikisource) . The main difference would be that derivatives are not required to have the same license. Reasons for changing to CC-BY 4.0 are:
It is a more permissive license. It makes it much easier to combine and mix works. ”

“ In the sense you're intending here, there is only one way to transclude works from the Page: namespace to a main namespace page (there are some variations surrounding use of sub-pages for chapters and such) . The syntactical variants you've found are mere technical artefacts: think of them as bugs, in software development terms. You might also want to take a moment to look into what the purpose of Wikisource is. We reproduce the original work faithfully (within reason, and there are unsettled gray areas) , rather than make new editions. ”

“ In order for something to be centered, you need to have a width that is less than the maximum; in mobile you're severely limited in horizontal real-estate anyway, so there's nearly never a reason to use the 'center block' concept because you're artificially forcing a user to scroll by squishing content into a fraction of an already limited area. ”

“ It should never be an issue to have a productive conversation about the components of the headers, and the layouts of the pages. Things evolve (front and back end; desktop and mobile) , and there is occasional design creep, so sounds reasonable discuss components that are problematic. We can lack good skills in css in our populace, or maybe that is those willing and able in css. Also to note that with the new mw:Extension:TemplateStyles there is scope for us to pull elements out of the Template:Header and modules to separate/simplify components. ”

“ If your aims are different from Wikisource's aims, then you are bound to be endlessly frustrated here. Finally, for any given method or bit of "bling", you may safely assume that it is the way it is based on the consensus of the community here that that is how it should be. Some things are certainly better debated than others, but if it is a certain way there's a good chance it's because it has at least de facto consensus. ”

“ Textbooks, manuals and logos, diagrams and screenshots from GFDL software manuals that only use the GFDL license are still allowed. Files licensed with both GFDL and an accepted license like Creative Commons BY-SA are still allowed.
There is no time limit to move files from other projects to Commons. The licensing date is all that counts. It doesn't matter when the file was uploaded or created. Every wiki that allows local uploads should check if bots, scripts and templates that are used to move files to Commons need to be updated. Also update your local policy documentation if needed. ”

“ Any place where people set an explicit width in pixels -- for example, on an image. Anything that relies on hovering -- the {{SIC}} and {{redact}} templates come to mind -- aren't compliant. Heck, the argument I accidentally started a few sections ago about the auxiliary tables of contents is about a non-compliant template. There's just not enough horizontal real-estate on a mobile device to support our layouts because we attempt to mimic and preserve the printed page. ”

“ This group is called interface administrators. Administrators can delete user CSS and JavaScript pages. There will be an A/B test on the Wikipedia mobile website. It starts this week. It tests how we show templates that show information about an article. The test will last two weeks. You can now use different CSS rules for different skins when you edit templates. This is because of TemplateStyles. wp10 in ORES is now called articlequality. When you get a new message on your talk page you get a yellow message in the toolbar. ”

“ So don't try to play the "poor little me" act when you've set yourself up for this by ignoring most of the advice you've been given and flouting established style at every turn. If you're going to refuse to follow convention, then at least be honest about what you're doing. ”

“ Not all changes will affect you. Translations are available.
Recent changes
The Wikimedia Commons mobile app has a new version. Images uploaded using Nearby are now automatically added to the associated Wikidata item. You can browse other images on Commons. You can see your achievements and your upload statistics. It has also fixed some bugs. MediaWiki web requests now have a time limit of 60 seconds for GET requests and 200 seconds for POST requests. Problems
You could not see the menu on the notifications page on the mobile version. ”

“ Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped. There will be code freezes for the weeks of 10 September 2018 and 8 October 2018. Non-essential code deployments will not happen. This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. ”

“ The time when you can't edit might be shorter than an hour. You can read more about this. Because of the data centre test there will be no new version of MediaWiki this week. Changes for this week will come next week instead. Meetings
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 11 Septmber at 18:30 (UTC) . See how to join. You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. ”

“ You can now see moved paragraphs in diffs in the mobile view. It also works on all languages in the desktop view. Bureaucrats on all Wikimedia wikis can now remove the interface admin user right. Problems
Some diffs show lines in the wrong order. The developers are working on fixing it. Changes later this week
The message you see when you thank a user will change. This is to make it easier to understand. AWB will stop adding using AWB in the edit summary. Instead it will add a tag that says AWB. Some abuse filter variables have changed. They are now easier to understand for non-experts. ”

“ As you move down the page, note things like the header object overlapping the first page number (the link to the transcluded page) . Would you like me to screenshot what is visible to everyone? Billinghurst wanted the author in italic and the title not italic, so that is characterised as a 'meta discussion' and therefore never to be fixed. CYGNIS INSIGNIS 02:37, 5 September 2018 (UTC) Mate, stop picking fights, it advances nothing, and turns things difficult. I neither designed nor developed the header, anything that was chosen at the time would have been community consensus. ”

“ Then I get this daunting page that feels like failure (about how the page doesn't exist, blah blah blah) . I use the "Create" or "Create this page" link located at the upper portion of the failure page and if I could spell walah.... The index page that occurs will need some help, but it is pretty cool how the gadget works.--RaboKarbakian (talk) 15:07, 25 August 2018 (UTC) If you have the {{book}} (preferable) or {{information}} template completed at Commons, when you create (action on your part) the Index page will be populated with the appropriate corresponding data fields. ”

“ Go back to the front matter, scroll to the TOC or index, figure out where you were and click the subsequent link? Now that seems like extraneous work. --Mukkakukaku (talk) 03:16, 8 September 2018 (UTC) @Mukkakukaku: What I like is solutions. I do not favour the layout options as a solution to anything but an imagined problem, and the header is a historical legacy that no amount of tweaks and workarounds will fix. I have a solution, but proposing may be futile; it is certain to be resisted because other users already have a substantial investment in the header's problems. ”

“ Do you have an idea for a task and could you imagine mentoring that task? For example, do you have something on mind that needs documentation, research, some gadget or template issues on your "To do" list but you never had the time, and can imagine enjoying mentoring such a task to help a new contributor? If yes, please check out mw:Google Code-in/2018 and become a mentor! Thanks in advance! --AKlapper (WMF) (talk) 13:51, 9 September 2018 (UTC)
Would fixing the edit page tool bars be a suitable task? There are things that are there that shouldn’t be and things that should be that aren’t e.g. ”

“ The developers work on making the wikis work better on mobile phones. There is a list of common problems when making content easier to read in the mobile view. You can add things to the page and ask others to help. Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe. ”

“ Generally with spacing I have just put one empty line between each line, and two empty lines b/w each letter. If you need to centre the Index label, I "noinclude" the formatting as it transcludes poorly. I will also often {{block center}} the entire transcluded set as a left aligned column can look "urk". If you are looking for examples, I have had parked quite a few at user talk:Phe over the years. — billinghurst sDrewth 13:34, 16 September 2018 (UTC)
On the other hand, I never block center/center block indices because I use Layout 2 by default and it looks "urk". ”

“ If it is something we should eventually have, then it can't hurt to set up the project. If others want to follow through, that's on them. BD2412 T 22:31, 19 September 2018 (UTC) Without a lack of clarity of what is needed, I am not certain that we can give specific advice. We can give general advice of 1) Straight transcription belongs at laWS. 2) If scans exist then they can be translated in our Page: ns. 3) If you want it done, it is our experience it will require a team of interested and committed people and a project is the best means to coordinate such. ”

“ Comment On WP they use infoboxes in articles much like we use headers. Would it perhaps be more in keeping with the rest of WS if instead of category infoboxes we introduce category headers that perform similar function? —Beleg Tâl (talk) 23:38, 25 September 2018 (UTC) I'd be mildly opposed to making our categories look like Author, Portal, and Work pages. Also, anyone who uses other projects will arrive with a certain expectation of what categories will look like, and doing something to violate that expectation seems a bad idea to me. ”

“ Even if Google holds no U.S. copyright in the automatic translations produced by its software, how about adding quick links from Wikisource? Perhaps machine translations will be improved, thus evolving.--Jusjih (talk) 01:52, 25 September 2018 (UTC) Tech News: 2018-39
Latest tech news from the Wikimedia technical community. ”

“ Also we have a lot of tables. The older experimental TOC templates do not degrade gracefully for the mobile view. Even things that should never have had tables for layout -- like {{Auxiliary Table of Contents}} in the argument above -- has a table based layout which it simply doesn't need. --Mukkakukaku (talk) 02:25, 13 September 2018 (UTC) From memory it harks back to the issue that we had with centre blocking (see Template talk:Block center) where it didn't work unless it was a table, and was why {{block center}} was a table (and I hadn't noticed that it had stopped being so.) ”

“ I have moved the first added to the 1997 space, though I think that it needs to be moved to the translation namespace, and we need to correct the case and grammar of the title. — billinghurst sDrewth 06:10, 26 September 2018 (UTC) New Wikidata templates The templates {{Reasonator}} and {{Scholia}} are available, for linking from Wikisource pages to representations of Wikidata items, where no suitable Wikipedia page is available as a target. They are modelled on {{WikiDark}}, with the same low-contrast links. Andy Mabbett (Pigsonthewing) ; Talk to Andy ”

“ Hesperian 07:46, 5 September 2018 (UTC)
templates do not work well in small screens / mobile. we could use a refresh. but that would require some coding, and consensus building for a redesign. Slowking4 ‽ SvG's revenge 12:24, 5 September 2018 (UTC) Hesperian. Example one is a mediawiki construct, what are you suggesting instead? What other configurations are available through mediawiki, and how else would you wish to work the issues around subpages and their linking? Example 2, is similarly a mediawiki construct, though it seems to be able to be controlled by class="firstHeading". ”

“ I have copied it (and the required modules and their required modules (ad nauseaum) ) on User:Einstein95/sandbox. I particularly find the "Notable Work" field quite interesting, it might lead people to start adding texts that we don't have if they're fans of authors or genres. -Einstein95 (talk) 06:09, 25 September 2018 (UTC) commons has a structured data on commons, and much work, standardizing metadata in templates. we could increase links from wikisource to wikidata ”