Hi,
There was no significant change in Malayalam language support since 2013 in
operating systems. Last OS which has incomplete Malayalam support was
Windows XP (without any service package), so it is irrelevant. There was no
prior notification about this removal. Malayalam webfonts were simply
unilaterally removed from Malayalam projects (just like it's deployment).
We Malayalam wikimedians like to know the substantial changes in
circumstances which lead to removal of Malayalam fonts from ULS. Please
also note that so many other languages which are much bigger in number of
speakers and well supported in OSs even before Malayalam, are still serving
webfonts in ULS (eg: Arabic, Tamil, Kannada etc).
There was occasion when a webfont imposed (maintained upstream by ULS
developer) on Malayalam community. User community members were asked
consensus for each and every word about this imposed webfont font. Once
Wikipedia editing was entirely impaired for weeks by removing typing tool
(ULS removed by misreading the bug) after these 'skirmishes'. Users were
abused and even humiliated based on their tribe by 'sidekicks' in public
mailing lists and forums. As a small community who lost a significant
number of users and thus growth, because of the problems in the deployment
of webfonts and antipathy, we believe we have the right to know the
circumstance/study/reason about this removal.
Related links:
https://phabricator.wikimedia.org/rEULS28c0ba6bca63e658160f772cdef141c2b929…https://phabricator.wikimedia.org/T53019https://phabricator.wikimedia.org/T51894
The fullfilled request for webfonts as an optional feature asked after
community consensus, also broken here.
---
ml:User:Praveenp
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
I've written an RfC to introduce a standardized and recommended way
for re-distributors and packagers of MediaWiki to be able to tune
DefaultSettings.php as appropriate.
You can read more details on-wiki[1], and discuss it on Phabricator[2].
[1]
https://www.mediawiki.org/wiki/Requests_for_comment/PlatformSettings.php
[2] https://phabricator.wikimedia.org/T182020
Thanks!
- -- Legoktm
-----BEGIN PGP SIGNATURE-----
iQJLBAEBCgA1FiEE+h6fmkHn9DUCyl1jUvyOe+23/KIFAlolpwQXHGxlZ29rdG1A
bWVtYmVyLmZzZi5vcmcACgkQUvyOe+23/KL43RAAld/PQ+KcmBks4lkaChAVK21o
7yTCBogPHQpLF73a4pNDIRn+XkHoO0jRmVkoGRIEsE4wTpvyFxxJo1cTbD2QAIKl
K0WKGBPQ8Lyyu4nFodiPwrvSGhhSi0iVvxMQPLq8K/FPF6bO8c331VAcLoJDQjyY
rfuQMnAnvBZ7kOzQPiXYgMkSpWgzFF1hn32h7HXyNuanK5KxjeRKl3ZTjmJj2iIk
zGoUhekJxipeIxgTb6ZT0H3YVMQdXyHuq4fvQFpOsX+KWgKspWOe4u7wbKTfCIN6
OCtRbIypHlSG4AgeQ1Bqcq3cPyvt2YuBaEaKn1ZMgByWKy65jcWt+x0KsVSe3aYm
jxzQI7gXBOIVvQeYHTezz91RSkL6bikI0wdBqg7Lsdr4Mb62CDQcfMmFSI1Iz8dD
ooz7Kcc7VTfU75VokJKNCPnVqdhux7dBgw5EhxBFGFIYfwUu6j8MayIxaZT8uyKj
OLCYOn8hslFEFeiOnSoMGtsS/6m6RR2YiTLC9r/+lGN2T/UeHm9RuCaBviZEaiQl
S9X9CAZlkaRg74zNyPO2e/E2v68F1shbpZDutzylal9QJfA0cEhBKbfQTEPlQwgN
qNxS7ajbb2G96HvF2Tyj8ai4YGENltmhp9M3/NzuJW6jj0fee+KNiNM7sRfMm7p4
nW7bXwXYkK4m4SuWxDM=
=PL+x
-----END PGP SIGNATURE-----
I've just now enable the feature flag on the testing wikis[1][2][3] that
allows MediaWiki to store comments longer than 255 bytes.
The web UI has not been updated to allow longer comments in places where it
enforces a limit, such as the edit summary box. But if you use the API to
edit, or perform page moves or do other things where long comments could be
entered and were truncated, you should now find that they're truncated at
1000 Unicode characters rather than 255 bytes.
Please test it out! If you find errors, or places in core features (not
comments in extensions such as SecurePoll, AbuseFilter, CheckUser, or Flow)
where *new* comments are still being truncated to 255 bytes, or places
where comments aren't showing up at all, please let me know. You can reply
to this message or post a task in Phabricator and add me as a subscriber.
If things go well, we'll look at rolling this out to production wikis once
the schema changes to the production databases are complete. See
https://phabricator.wikimedia.org/T174569 to follow progress there.
If anyone is interested in submitting patches for the web UI to reflect the
changed length limits, please do. I'll try to review them if you add me as
a reviewer.
[1]: https://test.wikipedia.org/wiki/Main_Page
[2]: https://test2.wikipedia.org/wiki/Main_Page
[3]: https://test.wikidata.org/wiki/Wikidata:Main_Page
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
For a while now, Wikimedia has been restricting the different binaries
that we shell out to (mostly image handling things) with firejail[1].
This was a manual process by writing wrapper scripts that invoked
firejail, and pointing MediaWiki to use those "binaries". It was a
pretty manual process, and other users of MediaWiki didn't benefit
from any of the work that was being done.
With [2], it's now possible to have MediaWiki invoke firejail with
restrictions specified in the code rather than configured separately.
For example, I converted the Score extension[3] to use the new shell
restrictions system.
There's more documentation available on-wiki[4]. You can test this out
yourself by installing firejail, and by setting
$wgShellRestrictionMethod = 'firejail';.
Note that firejail is a Linux-specific program, but the restriction
framework itself is abstract enough that it's likely that support for
other restriction software could be introduced.
[1] https://firejail.wordpress.com/
[2] https://gerrit.wikimedia.org/r/#/c/384930/
[3] https://gerrit.wikimedia.org/r/#/c/393830/
[4] https://www.mediawiki.org/wiki/Manual:Shell_framework#Restrictions
- -- Kunal / Legoktm
-----BEGIN PGP SIGNATURE-----
iQJLBAEBCgA1FiEE+h6fmkHn9DUCyl1jUvyOe+23/KIFAlolpfoXHGxlZ29rdG1A
bWVtYmVyLmZzZi5vcmcACgkQUvyOe+23/KI8CBAApq8rMUGf0SKIPYCddyBLJgMO
vL02D6xjA0j1HCmxwynolUh751ZbAi+kgNbEA8gtosxfvQls++vs+V4x1OXfxFWJ
+Fz2Q0WYLv0j0o8pQPbugDknNlMljmILDf5ISxlCyGxw+i6bGLdFOuLWVWVTBsAx
eGlGLiFT6ROZfG72K/V0hgDnT760bwLHMVhBR672zo+Sau3UdY2hGu1uG/9GJbQv
50/9z2JtZs7ZrriqX240DZNSQwi8O7L4ppJRRUo+z+Apc4+QbxUgE0hgbe6RYKCg
K0qLksh2zZwW4c/5rqwq4P85hCS56JeW+++Wq1q7iapQH+PWsCWoztyDc0yZAp1P
+UVVSe9aOEAhudoU6yvoHlxlatAJGJv6H9LcyNHTPTAyKwYJtOc5u30PHMpt65mB
oVHu7KbSljkGTpnTd01d1VY2gLjil40FwjoL76M1LBxIPe1Fx9SFJVDgwXxpK1BM
gY0RcwWSXjzB+vnUOcQL6G4FQ/BYP9+43y4G3OtMTrkK8FkANaqgdpBECM7wJltl
lP6DGluQBBVv0cgXwZ+PKQg2dJkYxbWOR0m1T219REoP6O85EEZjvhyCx3IEaHGG
NAaTc5s93XR85hP4+gjdaC8lAJRIld4y3OjQQ7w4tWVygy7Ve4J/cYiRreWyTiBf
nRgXZj47aHrM92jY2q4=
=HIvI
-----END PGP SIGNATURE-----
Forwarding as engineering@ is rarely used anymore.
Thanks Timo.
----- Forwarded message from Timo Tijhof <ttijhof(a)wikimedia.org> -----
> Date: Fri, 1 Dec 2017 18:42:26 -0800
> From: Timo Tijhof <ttijhof(a)wikimedia.org>
> To: Engineering <engineering(a)lists.wikimedia.org>
> Subject: [Engineering] Wikimedia-log-errors summary - 2017-12-01
>
> Been a while since the last summary, so here is one.
>
> * 168 reported unresolved issues
> * 160 issues without an assignee
> * 10 issues tagged with "Patch-For-Review"
>
> Please check out the breakdown of open issues by project to see which
> errors in your field welcome fixing:
> <https://phabricator.wikimedia.org/maniphest/query/OunXBb3QsLmc/#R>
>
> Or get the latest straight from Logstash:
> <https://logstash.wikimedia.org/app/kibana#/dashboard/mediawiki-errors>
>
> Top 5 by hit count in last 24 hours:
>
> 1. ERROR channel=PageViewInfo "Failed fetching {url}: {error}"
>
> #PageViewInfo
> https://phabricator.wikimedia.org/T181011
>
> 2. ERROR channel=error "Fatal error: Call to exists() on a non-object"
>
> #ProofreadPage
> https://phabricator.wikimedia.org/T181868
>
> 3. WARNING channel=XMP "XMPReader::parse .. "
>
> #Multimedia #MediaWiki-File-management
> https://phabricator.wikimedia.org/T118799
>
> 4. WARNING channel=session "Metadata merge failed: {exception}"
>
> #MediaWiki-Authentication #CentralAuth
> https://phabricator.wikimedia.org/T158365
>
> 5. WARNING channel=session "Metadata has an anonymous user, but a non-anon"
>
> #MediaWiki-Authentication #CentralAuth
> https://phabricator.wikimedia.org/T181869
>
> -- Timo
> _______________________________________________
> Engineering mailing list
> Engineering(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/engineering
----- End forwarded message -----
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
Hi,
The Technical Collaboration team proposes the creation of a developer
support channel focusing on newcomers, as part of our Onboarding New
Developer program. We are proposing to create a site based on Discourse
(starting with a pilot in discourse-mediawiki.wmflabs.org) and to point the
many existing scattered channels there.
This is an initial proposal for a pilot. If the pilot is successful, we
will move it production. For that to happen we still need to sync well with
Wikimedia Cloud Services, Operations and the Wikimedia technical community.
Please check https://www.mediawiki.org/wiki/Discourse and share your
feedback.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Am 01.12.2017 21:31 schrieb "Corey Floyd" <cfloyd(a)wikimedia.org>:
> Hi all,
>
> The experimental Trending Service[1] will be sunset on December 14th, 2017.
>
> We initially deployed this service to evaluate some real time features in
> the mobile apps centered on delivering more timely information to users.
> After some research [2], we found that it did not perform well with users
> in that use case.
>
> At this point there are no further plans to integrate the service into our
> products and so we are going to sunset the service to reduce the
> maintenance burden for some of our teams.
>
> We are going to do this more quickly than we would for a full stable
> production API as the usage of the end point is extremely low and mostly
> from our own internal projects. If you this adversely affects any of your
> work or you have any other concerns, please let the myself or the Reading
> Infrastructure team know.
>
> Thanks to all the teams involved with developing, deploying, researching
> and maintaining this service.
>
> P.S. This service was based off of prototypes Jon Robson had developed for
> detecting trending articles. He will be continuing his work in this area. I
> encourage you to reach out to him if you were interested in this project.
>
> [1] https://en.wikipedia.org/api/rest_v1/#!/Feed/trendingEdits
> [2]
> https://meta.wikimedia.org/wiki/Research:Comparing_most_
> read_and_trending_edits_for_Top_Articles_feature
>
>
>
> --
> Corey Floyd
> Engineering Manager
> Readers
> Wikimedia Foundation
> cfloyd(a)wikimedia.org
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l