Dear Wikipedians,
We'd like to announce a major update of the Math (rendering) extension.
For registered Wikipedia users, we have introduced a new math rendering
mode using MathML, a markup language for mathematical formulae. Since MathML
is not supported in all browsers [1], we have also added a fall-back mode
using scalable vector graphics (SVG).
Both modes offer crisp rendering at any resolution, which is a major
advantage over the current image-based default. We'll also be able to make
our math more accessible by improving screenreader and magnification support.
We encourage you to enable the MathML mode in your Appearance preferences.
As an example, the URL for this section on the English Wikipedia is:
https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-rendering
For editors, there are also two new optional features:
1) You can set the "id" attribute to create math tags that can be
referenced. For example, the following math tag
<math id="MassEnergyEquivalence">
E=mc^2
</math>
can be referenced by the wikitext
[[#MassEnergyEquivalence|mass energy equivalence]]
This is true regardless of the rendering mode used.
2) In addition, there is the attribute "display" with the possible values
"block" or "inline". This attribute can be used to control the layout of the
math tag with regard to centering and size of the operators. See
https://www.mediawiki.org/wiki/Extension:Math/Displaystyle
for a full description, of this feature.
Your feedback is very welcome. Please report bugs in Bugzilla against the
Math extension, or post on the talk page here:
https://www.mediawiki.org/wiki/Extension_talk:Math
All this is brought to you by Moritz Schubotz and Frédéric Wang (both
volunteers) in collaboration with Gabriel Wicke, C. Scott Ananian,
Alexandros Kosiaris and Roan Kattouw from the Wikimedia Foundation. We also
owe a big thanks to Peter Krautzberger and Davide P. Cervone of MathJax for
the server-side math rendering backend.
Best,
Gabriel Wicke (GWicke) and Moritz Schubotz (Physikerwelt)
[1]: Currently MathML is supported by Firefox & other Gecko-based browsers,
and accessibility tools like Apple's VoiceOver. There is also partial
support in WebKit.
For your information.
---------- Forwarded message ----------
From: Quim Gil <qgil(a)wikimedia.org>
Date: Thu, Oct 23, 2014 at 6:56 PM
Subject: Bugzilla-Phabricator migration instance ready for review
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Phabricator milestone!
https://bugzillapreview.wmflabs.org/https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Test_instance
(please read)
A test instance is available for review, showing a sample of 10% of all the
Bugzilla reports, automatically migrated. Register with your Bugzilla email
address, wait for your activity to be assigned to you (might take a while),
and try to find problems that we should fix before the real migration
happens.
WE WANT YOUR FEEDBACK
https://phabricator.wikimedia.org/tag/bugzilla-preview/
Check the list of known issues before creating new tasks. We are leaving at
least one week for feedback, or more if there are issues that require fixes
and a second test. At the end of the review period we will be able to
commit to a Bugzilla migration date.
Thank you again to Chase, Mukunda, and Andre for opening a way that nobody
has walked before. Big Thank You also to the growing number of contributors
helping in this complex and terribly interesting migration process!
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hi I am intetested to know more about this recommendation function
------------------------------
On Fri, Sep 12, 2014 8:32 PM CST (China) Jérémie Roquet wrote:
>Hi Steven, hi everyone,
>
>2014-09-05 3:12 GMT+02:00 Steven Walling <swalling(a)wikimedia.org>:
>> we'll be launching a new experiment aimed at helping newly-registered
>> editors, called task recommendations.
>
>It seems that not-so-newly-registered editors are concerned as well,
>and some of them are wondering how to disable this new feature¹. Any
>tip that doesn't involve dirty hacking with JavaScript and CSS?
>
>Thanks!
>
>¹ https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Le_Bistro/12_septembre_2014#Re…
>
>--
>Jérémie
>
>_______________________________________________
>Wikitech-ambassadors mailing list
>Wikitech-ambassadors(a)lists.wikimedia.org
>https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
Hello and welcome to the latest edition of the WMF Engineering Roadmap
and Deployment update.
The full log of planned deployments next week can be found at:
<https://wikitech.wikimedia.org/wiki/Deployments#Week_of_October_20th>
A quick list of notable items...
== Early week ==
* 10% of reader (non-logged-in) traffic will be served by HHVM servers
** see: <https://www.mediawiki.org/wiki/HHVM/About>
== Monday ==
* The IEG Review application will be deployed
** <https://bugzilla.wikimedia.org/show_bug.cgi?id=71597>
== Tuesday ==
* MediaWiki deploy
** group1 to 1.25wmf1: All non-Wikipedia sites (Wiktionary, Wikisource,
Wikinews, Wikibooks, Wikiquote, Wikiversity, and a few other sites)
** <https://www.mediawiki.org/wiki/MediaWiki_1.25/wmf4>
== Thursday ==
* MediaWiki deploy
** group2 to 1.25wmf4 (all Wikipedias)
** group0 to 1.25wmf5 (test/test2/testwikidata/mediawiki)
Thanks and as always, questions and comments welcome,
Greg
--
Greg Grossmeier
Release Team Manager
Hi all,
Due to the POODLE vulnerability in SSL3.0 that's been announced this
week and has made its round through the media, we decided that we
needed to disable SSL3.0 on all our HTTPS services today, to protect
the security of all our users. The bulk of that change has been
deployed today at 15:00 UTC for the wikis, and the remaining HTTPS
services are getting the same treatment throughout the day. Please see
our blog post on this topic for details:
http://blog.wikimedia.org/2014/10/17/protecting-users-against-poodle-by-rem…
If you see or hear about anyone having issues connecting to our sites
over HTTPS or logging in, please direct them at the link above, and
urge them to upgrade their software. Unfortunately due to the nature
of HTTPS we're not able to provide a fallback when users get an error
message due to this. We're still looking into the possibility to
provide affected users with an informative error message upon login
however, before they get redirected from HTTP to HTTPS.
As a side note, we've also deployed Google's SCSV SSL extension[1] on
our servers yesterday, such that the attack surface for such
vulnerabilities will be reduced in the future for clients which
support this extension.
[1] http://googleonlinesecurity.blogspot.nl/2014/10/this-poodle-bites-exploitin…
Thanks,
--
Lead Operations Architect
Director of Technical Operations
Wikimedia Foundation
---------- Forwarded message ----------
From: "Mark Bergsma" <mark(a)wikimedia.org>
Date: Oct 17, 2014 2:05 PM
Subject: [Wikitech-l] SSL 3.0 disabled on Wikimedia sites
To: <wikitech-l(a)lists.wikimedia.org>
Cc:
> Hi all,
>
> Due to the POODLE vulnerability in SSL3.0 that's been announced this
> week and has made its round through the media, we decided that we
> needed to disable SSL3.0 on all our HTTPS services today, to protect
> the security of all our users. The bulk of that change has been
> deployed today at 15:00 UTC for the wikis, and the remaining HTTPS
> services are getting the same treatment throughout the day. Please see
> our blog post on this topic for details:
>
>
http://blog.wikimedia.org/2014/10/17/protecting-users-against-poodle-by-rem…
>
> If you see or hear about anyone having issues connecting to our sites
> over HTTPS or logging in, please direct them at the link above, and
> urge them to upgrade their software. Unfortunately due to the nature
> of HTTPS we're not able to provide a fallback when users get an error
> message due to this. We're still looking into the possibility to
> provide affected users with an informative error message upon login
> however, before they get redirected from HTTP to HTTPS.
>
> As a side note, we've also deployed Google's SCSV SSL extension[1] on
> our servers yesterday, such that the attack surface for such
> vulnerabilities will be reduced in the future for clients which
> support this extension.
>
> [1]
http://googleonlinesecurity.blogspot.nl/2014/10/this-poodle-bites-exploitin…
>
> Thanks,
>
> --
> Lead Operations Architect
> Director of Technical Operations
> Wikimedia Foundation
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
