* Should Mailman collapse multipart/alternative to its first part content?
* Should Mailman convert text/html parts to plain text? This
conversion happens after MIME attachments have been stripped.
These mailman options are both enabled for this list. I would argue
that they should both be disabled. It is nice to write emails with
cutting-edge features like client-side word wrapping and links.
Are there any objections to this change?
-- Tim Starling
Hi all,
Tomorrow we will be issuing a security and maintenance release to all
supported branches of MediaWiki.
The new releases will be:
- 1.34.3
- 1.31.9
This will resolve eight issues in MediaWiki core (two of which aren't
applicable to MediaWiki 1.31), and also includes some fixes previously
committed to git, including minor security and hardening patches along with
bug fixes included for maintenance reasons.
For those of you waiting on MediaWiki 1.35.0, this will also come either
tomorrow, or at latest Friday (depending on CI load), including the
security fixes applied to these other supported release branches. We thank
you for your patience; the current global situation means things have taken
longer than would have been expected, but it has meant more bug fixes being
incorporated from testing across the board. It also meant not having a
security 1.35.1 release followup only a couple of weeks after 1.35.0 coming
out. Which, for many people would mean extra work to upgrade again, and it
was decided to avoid this.
We will make the fixes available in these respective release branches, and
also master. Tarballs will be available for the above mentioned point
releases as well.
A summary of some of the security fixes that have gone into non-bundled
MediaWiki extensions will also follow.
As per the MediaWiki Version lifecycle [1], November 2020 is the scheduled
EOL date for the REL1_34. 1.34.3 will therefore potentially be the final
release of the MediaWiki 1.34 branch, barring any unforeseen issues. As per
above, MediaWiki 1.35.0 will be released this week, and will be supported
until at least September 2023, and would be the recommended upgrade path.
[1] https://www.mediawiki.org/wiki/Version_lifecycle
Hi, is there an example that shows how to reject writeapi edits made using scripts unless the edit has a required tag? For example, changes made using Visual Editor are labeled with “(Tag: Visual edit)”.
Thank you!
Hello all!
Over the past few months we've reached the ignominious milestone of
the most open tasks of all time on the wikimedia-production-error
dashboard[0].
Background: The wikimedia-production-error dashboard is a workboard of
tasks created while digging through the Wikimedia production error
logs. All tasks there are log messages that have originated on
production servers.
The number of new tasks being created with this tag in a given week is
outpacing the number of tasks being closed in a given week: this past
week we added 41 tasks and only closed 22.
This is beginning to be unsustainable :(
There are currently 281 open tasks filed for errors in production.
Although we're triaging this workboard weekly, we rely on the
expertise of developers most familiar with the error messages to
triage them, prioritize them, and "fix" them (for whatever value of
"fix" is appropriate).
Below is a smattering of selected issues that could use some attention:
1. PHP Fatal error: Out of memory in cdb/src/Reader/DBA.php[1]
2. Uncaught ReferenceError: collectionCall is not defined[2]
3. Flow: PHP Notice: Undefined index: flow-workflow-change[3]
4. PHP Warning: unpack(): Type H: not enough input, need 4, have 0[4]
5. TypeError: undefined is not an object (evaluating 'this.getMIMEType')[5]
6. Elastica\Exception\ResponseException from line 56 of
GeoData/includes/Searcher.php[6]
7. Wikimedia\CSS\Objects\ComponentValueList may not contain tokens
of type "[".[7]
Please help to triage or resolve these problems or any of the other
166 tasks needing triage[8] if you are able.
<3
-- Tyler
[0]: <https://phabricator.wikimedia.org/tag/wikimedia-production-error/>
[1]: <https://phabricator.wikimedia.org/T260234>
[2]: <https://phabricator.wikimedia.org/T259809>
[3]: <https://phabricator.wikimedia.org/T259739>
[4]: <https://phabricator.wikimedia.org/T259592>
[5]: <https://phabricator.wikimedia.org/T259419>
[6]: <https://phabricator.wikimedia.org/T258641>
[7]: <https://phabricator.wikimedia.org/T258093>
[8]: <https://phabricator.wikimedia.org/maniphest/query/LW5WTEnToXDn/#R.>
It's time for Wikimedia Tech Talks 2020 Episode 8! This talk will take place
Tuesday 22 September 2020 at 17:00 UTC.
Title: (Modern) Event (Data) Platform
Speaker: Andrew Otto, Staff Site Reliability Engineer
Summary:
Wikimedia's Event (Data) Platform provides a foundation for building
loosely coupled event driven software systems. This talk will go over why
we built Event Platform and give an overview of its components and how they
work.
The link to the Youtube Livestream can be found here:
<https://www.youtube.com/watch?v=jNNy8ALGjaE>
https://www.youtube.com/watch?v=Tb_9gOYsWJQ
During the live talk, you are invited to join the discussion on IRC at
#wikimedia-office
You can browse past Tech Talks here:
https://www.mediawiki.org/wiki/Tech_talks
If you are interested in giving your own tech talk, you can learn more here:
https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Te…
Note: This is a public talk. Feel free to distribute through appropriate
email and social channels!
Kindly,
Sarah R. Rodlund
Senior Technical Writer, Developer Advocacy
<https://meta.wikimedia.org/wiki/Developer_Advocacy>
srodlund(a)wikimedia.org