In order to address a security issue, we are patching and rebooting many
physical Labs hosts. The next round of this will begin at 15:00 UTC on
Friday, which is 8:00AM San Francisco time.
Interruptions will include:
- A labs-wide network outage
- Wikitech downtime
- Horizon downtime
- Possible failures in new instance creation
None of the above should last more than a few minutes. For the most
part Labs instances will be unaware of the outages, and no action is
required from users.
Apologies for any inconvenience caused!
-Andrew
Hi everyone,
For [this week's ArchCom-RFC meeting][E325], let's talk about SVG.
As you probably know, MediaWiki optionally allows for SVG uploads,
which is allowed on many Wikimedia wikis (e.g. on Commons). However,
in order to make this preference safe to use, we need to validate the
SVG.
One thing that's allowed in the SVG spec is to embed fragments of
XHTML inside the SVG. This isn't just a obscure spec feature; this is
understood to be the best way to embed a caption for a diagram that
allows for word wrap when the image is scaled. Having XHTML support
also would allow for greater compatibility between MediaWiki and
real-world SVG editing tools (e.g. like draw.io)
matmarex made a suggestion in [the bug for this][T138783]:
> We have a HTML validation library (the Sanitizer class) and it could
> probably be hooked up to validating HTML in SVG file uploads. But it
> would definitely require some work.
It's not officially an RFC, but I suggested it as a discussion topic
in [last week's ArchCom planning meeting][3], and no one objected.
Let's see if we can answer a couple of questions:
1. Is this a good idea in theory? i.e. is it possible/likely that an
experienced developer could implement something that can pass security
review, or is it conceptually flawed?
2. Is matmarex's suggested approach a good one?
3. Should we turn our SVG validation code into a proper library?
4. (if there's time) Let's step through the [brion's June 30 comment][4]
This week it will be the usual time (Wednesday 21 UTC, 14 PDT, 23 CEST)
and place (#wikimedia-office). Next week, things get complicated
because of the end of [Summer Time in Europe][5]; an announcement
about next week's meeting will hopefully find its way to the
[ArchComStatus page][6].
Rob
[E325]: <https://phabricator.wikimedia.org/E325>
[T138783]: <https://phabricator.wikimedia.org/T138783>
[3]: <https://www.mediawiki.org/wiki/Architecture_committee/2016-10-19>
[4]: <https://phabricator.wikimedia.org/T138783#2419210>
[5]: <https://en.wikipedia.org/wiki/Summer_Time_in_Europe>
[6]: <https://www.mediawiki.org/wiki/ArchComStatus>
On Saturday Oct 29, at 8 am UTC, the web server for the dumps and other
datasets will be unavailable due to maintenance. This should take no
longer than 10 minutes. Thanks for your understanding.
Ariel
A security bug [1] has been fixed in CentralAuth; the bug caused logouts to
silently fail if the local account on the central login wiki was
unattached. That does not happen under normal circumstances, so the
vulnerability can only be exposed if some other error causes attaching
accounts to fail; nevertheless you are advised to update your
installations. The fix has been backported to all supported versions (those
for MediaWiki 1.23, 1.26 and 1.27).
Gergő
https://www.mediawiki.org/wiki/User:Tgr_(WMF)
[1] https://phabricator.wikimedia.org/T137551
_______________________________________________
MediaWiki announcements mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
Hello all,
There is a new internship opportunity in the Community Engagement
department for a Technical Design Intern. We are looking for a candidate
who works and/or studies in the field of computer science and information
systems, has experience in advanced wiki markup and design skills for web,
and the ability to excel in a fast-paced, multitasking environment, among
other qualifications. Knowledge and or experience with Wikimedia Projects
a plus!
The Technical Design Intern will work closely with the Communications and
Outreach Coordinator (that would be me!) on the Wikimedia Resource Center,
the redesign of the Evaluation Portal on Meta Wikimedia, and migration and
archiving of L&E portal pages from existing namespaces to new namespace,
among other tasks. You can find the complete job description here:
https://boards.greenhouse.io/wikimedia/jobs/488570#.WBE6X-ErKRs
If you are interested, please apply. If you know someone who might fit this
position, please forward the email to them!
Cheers,
*María Cruz * \\ Communications and Outreach Coordinator, L&E Team \\
Wikimedia
Foundation, Inc.
mcruz(a)wikimedia.org | Twitter: @marianarra_
<https://twitter.com/marianarra_>
Hi,
I have an extension that change some of the default system messages for
example "talk" to "comment", but since upgrading to 1.27 these messages
no longer change. I've tried rebuildmessages.php and
rebuildLocalisationCache.php but nothing seems to allow me to override
these default messages any more. New messages that the extension
introduces can be changed no problem.
Does anyone here know the proper procedure for doing this?
Thanks,
Aran
After extensive testing over the last several months using a new search
query scoring method called BM25 (Best Matching) [1], we recently completed
a limited
production
release to the following top languages: English, German, Spanish, Russian,
Portuguese, French, Italian, Polish, Dutch and Arabic. This new release is
replacing the older search method called tf-idf (term frequency-inverse
document frequency) [2].
We have
additional
testing to do [3,4] to figure out if BM25 will work in languages that
don’t use spaces in-between their words
,
i.e.: Japanese, Chinese, etc.
The Discovery team announces much of
our
completed work in weekly status updates [5
, 6
], but some of the work isn’t actually obvious to anyone who uses our
search engine
- t
hat is because it isn’t actually ‘live’ until a complete re-index of the
servers occur. We’ve created a recurring ticket in Phabricator [
7
] to keep track of the work that goes live
in production
after a re-index, such as the one we’ve also just completed. A few
highlights
of the
recent
re-index
are implementing ascii-folding for the French language and
fixing
several
bugs
for French ÿ, and Russian ’Е’ and 'Ё' when
those characters are
entered in a search query.
Cheers from the Discovery Search Team!
[1] https://en.wikipedia.org/wiki/Okapi_BM25
[2] https://en.wikipedia.org/wiki/Tf%E2%80%93idf
[3] https://phabricator.wikimedia.org/T147495
[4] https://phabricator.wikimedia.org/T147501
[5]
https://www.mediawiki.org/wiki/Wikimedia_Discovery#Updates
[
6
] https://www.mediawiki.org/wiki/Discovery/Status_updates
[
7
] https://phabricator.wikimedia.org/T147505
--
deb tankersley
Product Manager, Discovery
irc: debt
Wikimedia Foundation