Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 3-4 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Hi everyone,
The reponsive MonoBook project is being deployed next week with the
normal MediaWiki train. It gives MonoBook a mobile layout for smaller
screens, so we can use the same code base to support both layouts (same
as Timeless).
There are some more details on Phabricator[1]. You can test this out on
the Beta Cluster[2] before it gets deployed.
[1] https://phabricator.wikimedia.org/T195625
[2] https://en.wikipedia.beta.wmflabs.org/wiki/Main_Page?useskin=monobook
Thanks,
-- Legoktm
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **today, Wednesday 3-4 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 3-4 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Hi everyone.
The Readers web team has recently begun working on exposing issue
templates on the mobile website. [0] Currently, details about issues
with page content are generally hidden on the mobile website. This
leaves readers unaware of the reliability of the pages they are
reading. The goal of this project is to improve awareness of
particular issues within an article on the mobile web. We will do this
by changing the visual styling of page issues.
So far, we have drafted a proposal on the design and implementation of
the project. [1] We were also able to run user testing on the proposed
designs. [2] The tests so far have positive results. Here is a quick
summary of what we learned:
* The new treatment increases awareness of page issues among
participants. This is true particularly when they are in a more
evaluative/critical mode.
* Page issues make sense to readers and they understand how they work
* Readers care about page issues and consider them important
* Readers had overwhelmingly positive sentiments towards Wikipedia
associated with learning about page issues
Our next step would be to start implementing these changes. We wanted
to reach out to you for any concerns, thoughts, and suggestions you
might have before beginning development. Please visit the project page
where we have more information and mockups of how this may look. [1]
Please leave feedback on the talk page. [3]
[0] https://www.mediawiki.org/wiki/Reading/Web/Team
[1] https://www.mediawiki.org/wiki/Reading/Web/Projects/Mobile_Page_Issues
[2] https://www.mediawiki.org/wiki/Reading/Web/Projects/Mobile_Page_Issues/Rese…
[3] https://www.mediawiki.org/wiki/Talk:Reading/Web/Projects/Mobile_Page_Issues
Yours,
Chris Koerner
Community Liaison
Wikimedia Foundation
(cross-post)
Dear all,
we are really happy to announce that the new AdvancedSearch interface got
deployed as a beta feature to all wikis just now. [1]
The search has great options to perform advanced queries e.g. by using
keywords like "hastemplate" or "intitle", but often even experienced
editors don't know about it - this is what we found out in a workshop
series on advanced searches in 2016 and this is why we have built the
AdvancedSearch extension. [2]
AdvancedSearch enhances Special:Search through an advanced parameters form.
It serves as an interface for some of the search options that the Wikimedia
Foundation's search team has been implemented over the past years. The way
the interface works, users don't have to know the syntax behind each search
field, but they can learn about it if they want to.
*From small beta to full beta*
The feature already has been a beta feature on deWP, arWP, huWP, faWP and
mediawiki.org for more than 5 months. During this "small beta phase" (=
base version with a set of features, deployed to a few wikis, both ltr and
rtl wikis) support for more search options got added (searches in
categories and sub categories, searches for content in a specific language
in wikis that have the translate extension enabled, searches for subpages
of a page), the way how to select and configure namespaces got improved and
several bugs were fixed.
Everyone is invited to test the now full beta feature!
If you want to give us feedback or if you find a bug, please use the main
feedback page (or file a ticket in phabricator):
https://www.mediawiki.org/wiki/Help_talk:Extension:AdvancedSearch
If you want to learn more about the project, the functional scope of the
AdvancedSearch extension and the usage, please see
* the help page: https://www.mediawiki.org/wiki/Help:AdvancedSearch
*the main project page: https://meta.wikimedia.org/
wiki/WMDE_Technical_Wishes/AdvancedSearch
* the list of supported search options:
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/AdvancedSearch/Functi…
*Thanks, thanks, thanks :-)*A huge thanks to everyone who has tested the
feature and gave feedback over the last 5 months and to everyone who has
translated software messages and announcements - this is much appreciated!
And a huge thanks to the WMF's search team who has done all the backend
work and has built great options for advanced search queries that now can
be accessed through the AdvancedSearch interface. It was and is great to
work with you :-)
Looking forward to more testing and feedback to further improve the feature,
Thanks a lot,
Birgit
(for WMDE's Technical Wishes team)
[1] https://phabricator.wikimedia.org/T193182
<https://phabricator.wikimedia.org/T180147>(Deployment ticket)
[2] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/AdvancedSearch
/Workshop
<https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/AdvancedSearch>
--
Birgit Müller
Community Communications Manager
Software Development and Engineering
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 3-4 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
A recent change to MediaWiki software seems to have broken templates
everywhere. The syntax
[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]
used to work on a template to generate a link to a page in the same
namespace, typically used on templates related to move (rename) discussions.
However this has stopped working as of last month, causing lots of
[[::ABC|ABC]] to be displayed in plain-text everywhere when this syntax is
used in the main namespace.
We figured for now at yue.wp that
[[{{NAMESPACE}}:{{{1}}}|{{{1}}}]]
(notice the deletion of the colon at the beginning) works and would like to
know if this is the recommended solution. This doesn't seem to have been
picked up by Linter.
Related discussion on yue.wp:
https://zh-yue.wikipedia.org/w/index.php?title=Wikipedia%3A%E5%9F%8E%E5%B8%…
Deryck
[[User:Deryck Chan]]
Sysop & ambassador, yue.wp
Hello everyone,
*TL:D**R;*
As you are aware from previous postings on this list [1] [2] [3] [4] [5]
[6], we have been progressively replacing Tidy with RemexHtml on all
wikis on the wikimedia cluster. As of today, about 650 wikis have made
the switch that include a number of large wikis. We aim to complete this
switch over on the remaining 250 wikis by end of June 2018. Another 40
or so wikis will be switched on May 2nd.
There are a few large wikis (es, pt, uk, zh especially) that could use
more attention addressing Linter issues so that when we make the switch
end of June, some pages on these wiki don't render differently from how
they do now.
*
*
*Details:*
I started investigating more closely where the remaining large wikis are
with respect to the linter issues (high priority categories on the
Special:LintErrors page) that are pertinent to these wikis. I am listing
below results from running sql queries on quarry.wmflabs.org for these
wikis. If you are a community member on any of these wikis, do try to
address these on your wiki.
_15 other large wikis:_
See https://quarry.wmflabs.org/query/26474 for counts of linter issues
for each of the 9 categories in the main namespace.
__
* *es, pt, uk, zh* wikis have total error counts over 10K and in some
cases, it is usually one category which needs attention.
* *vi, ro, sr, sh, ar, tr, id* are not too bad but don't seem to have
seen a lot of change which indicates that these wikis aren't looking at
linter issues.
* fr, hu, ja, pl wikis seem to be in good shape overall. There has been
a steady fixing of issues and I think all these will will be in fairly
decent shape for replacing Tidy by end of June.
https://www.mediawiki.org/wiki/Parsing/Replacing_Tidy/FAQ#Simplified_instru…
has some summarized instructions for fixing issues in different categories
_English Wikipedia:_
See https://quarry.wmflabs.org/query/25665 for counts of linter issues
for each of the 9 categories in the main namespace.
English wp has been making slow and gradual progress. I think overall,
despite there still being ~8300 instances (not pages) that need fixing,
enwp is in pretty good shape for replacing Tidy by end of June.
__Commons:__
See https://quarry.wmflabs.org/query/25693 for counts of linter issues
for each of the 9 categories in the File (ns6), Gallery (ns0), and
Template (ns10) namespaces.____
The vast majority of html5-misnesting errors on commons seem to come
from the use of the {{lang}} template which uses a <span> tag to wrap
content. However, it seems to be extremely common to pass content with
paragraphs into the {{lang}} template. Right now, this doesn't cause any
visible rendering issues and could be ignored temporarily, but we
strongly recommend fixing lang to use <div> or on pages which misuse
{{lang}} this way, replace use of {{lang}} by creating a new template
({{lang-block}} maybe?) that uses a <div> tag.
*
Some tips:*
1. On some wikis, fixing templates usually fixes the problem. Over the
last 6 months, I've personally spent many hours fixing 100s of templates
on 10s of different wikis and can personally attest to the efficacy of
that strategy.
2. A lot of the html5-misnesting errors seem to be from incorrectly
using a <span> tag to wrap content that has paragraphs, lists, tables.
In all these cases, changing them to <div> almost always fixes the problem.
If you need any assistance, please leave a message on
https://www.mediawiki.org/wiki/Help_talk:Extension:Linter. Between 8 am
- 4pm PST, you can also usually find us on IRC on #mediawiki-parsoid.
Thanks,
Subbu.
(on behalf of the Parsing team @ Wikimedia Foundation)
1.
https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2017-July/001625…
2.
https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2017-August/0016…
3.
https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2018-January/001…
4.
https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2018-February/00…
5.
https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2018-March/00180…
6.
https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2018-March/00182…