Hello!
MediaWiki-CodeSniffer 14.1.0 is now available for use in your MediaWiki
extensions and other projects. This release features improves to the
documentation-related sniffs and new upstream releases. 14.0.0 was
tagged, but 14.1.0 should be used as it includes a newer upstream
version. Here's the changelog since 13.0.0
* Update PHP_CodeSniffer to 3.1.1 (Paladox)
* Add sniff for @params instead of @param (Umherirrender)
* Better distinguish "one space before brace" and "brace on same line"
(Florian Schmidt)
* Typo fix in docs (MarcoAurelio)
* Unwrap types in function docs from {} (Umherirrender)
* Update PHP_CodeSniffer to 3.1.0 from 3.0.2 (Paladox)
* Validate doc syntax (Umherirrender)
Libraryupgrader and Umherirrender submitted patches for most Gerrit
repositories :)
Thanks,
-- Legoktm
Hello everyone,
I would like to share the first edition of the New Developers Quarterly
Report <https://www.mediawiki.org/wiki/New_Developers/Quarterly/2017-10>
that the Developer Relations team has produced. This report covers metrics,
survey analysis and lessons learned from new developers focused activities
in the previous quarter (July-September 2017).
If you have questions and feedback that you would like to share with us,
please add them on the discussion
<https://www.mediawiki.org/wiki/Talk:New_Developers/Quarterly/2017-10>
page.
To receive a notification when a new report is published, subscribe here
<https://www.mediawiki.org/wiki/Special:Newsletter/11/subscribe>.
We plan to release a report every quarter and take action items identified
from the key findings for improving our existing methods and processes. The
next release will be in January 2018.
If you have any questions, comments, and concerns, we will be more than
happy to hear them!
Thanks,
Srishti
--
Srishti Sethi
Developer Advocate
Technical Collaboration team
Wikimedia Foundation
https://www.mediawiki.org/wiki/User:SSethi_(WMF)
Hello All,
For those of you that had shown interest in attending the IRC Tech Debt SIG
kickoff meeting, my apologies for having to cancel it last minute. I had a
minor family emergency to attend to. Unfortunately, the email I sent out
only went to the internal email distribution lists.
I've not yet reschedule the meeting as I was actually thinking of having
the Tech Debt SIG kickoff be a topic during the first, yet to be scheduled,
Code Health office hours.
If you'd prefer that I set up a separate time for the IRC Tech Debt SIG
kickoff, please let me know. Otherwise, please hold tight as I will be
scheduling the Code Health office hours by Tuesday of next week.
Cheers,
JR
How many years into the future is it reasonable to expect that MySQL will remain a recommended database server for "production use" along with MariaDB now that the Foundation has switched to using MariaDB internally? I know that MariaDB claims to be drop in compatible with MySQL, but the list of variances seems to be slowly growing. References...
* Compatibility - [[mw:Compatibility]]
* MariaDB support? - [[mw:Topic:R1hqki3kaytylml4]]
* https://mariadb.com/kb/en/library/mariadb-vs-mysql-compatibility/
Other than [[mw:Compatibility]] on mediawiki.org is there anywhere else (wiki pages, Phabricator tasks/tags, etc.) that I should check for technical roadmap information before emailing wikitech-l?
Thank you!
Michael
---------- Forwarded message ----------
From: Volker Eckl <volker(a)wikimedia.org>
Date: Tue, Oct 17, 2017 at 6:41 PM
Subject: OOjs UI 0.24.0 release (breaking change)
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Hello everyone,
We've released OOjs UI 0.24.0, today. It will be in MediaWiki core from
1.31.0-wmf.4, which will be deployed to Wikimedia production in
the regular train, starting on Tuesday 24 October. As there are five
breaking
changes in this release, at least nominally, please carefully consider if
they
affect your code.
Breaking changes since last release:
* Drop 'MediaWiki' backwards-compatibility theme (James D. Forrester)
To better indicate usage focus, 'MediaWiki' theme got renamed to
WikimediaUI'
in v0.22.0. The remaining backwards-compatible alias has been dropped
in this release.
* icons: Drop 'stripeSideMenu' (James D. Forrester)
'stripeSideMenu' was renamed to 'draggable' and moved to 'movement' pack
in v0.22.2. It's now completely dropped. Use it with it's new name from
'movement' instead.
* icons: Remove 'eye'/'eyeClosed' icons (Volker E.)
We want to use 'alerts' pack more deliberately in major products and
moved 'eye'/'eyeClosed' out. They were deprecated in v0.23.0 in 'alerts'.
Use icons from 'accessibility' pack instead.
* icons: Remove 'signature' icon (Volker E.)
Similar to above, we deprecated 'signature' in v0.23.0 in 'alerts'.
Use icon from 'editing-advanced' pack instead.
* icons: Remove 'sun' (James D. Forrester)
'sun' icon isn't in use in any of our products or products known to us,
nor is it planned to be used. In order to keep things small, the icon,
deprecated in v0.23.0,
now has been removed.
Please update your icon pack references accordingly in case you're
using one of those
icons.
Additional details on the 4 new features, 29 code-level and
accessibility changes,
24 styling and interaction design amendments, and all improvements
since v0.23.0 are in
the full changelog[0]. If you have any further queries or need help dealing
with breaking changes, please let me know.
As always, library documentation is available on mediawiki.org[1],
and there is some comprehensive generated code-level documentation and
interactive demos hosted on doc.wikimedia.org[2].
[0] - https://phabricator.wikimedia.org/diffusion/GOJU/browse/
master/History.md
[1] - https://www.mediawiki.org/wiki/OOjs_UI
[2] - https://doc.wikimedia.org/oojs-ui/master/
Best,
Volker
--
Senior UX Engineer, Contributors
Wikimedia Foundation
volker.e(a)wikimedia.org | @Volker_E
Today's RFC discussion was T172165, a proposal for MediaWiki 1.31 to
require PHP 7.0. There was no consensus on that proposal, due to the
opinion from Ops that it is not feasible to migrate all application
servers to Debian Stretch and PHP 7.0 by the expected release date of
June 2018.
However, there was consensus on the lesser goal of requiring PHP 5.6.
So, we have created a new RFC for PHP 5.6 (T178538) and are hereby
placing it into Last Call.
The proposal is: MediaWiki should bump its PHP requirement to 5.6 as
soon as possible, and at the latest in time for the 1.31 branch point
(i.e. April 2018).
"As soon as possible" means as soon as the few remaining uses of PHP
5.5 in the WMF cluster have been migrated to PHP 5.6 or later, or to
HHVM. We'd like to see this migration work be given a high priority.
If you have any objection to this proposal, please raise it on
Phabricator before the end of the Last Call period, which will be
October 31.
https://phabricator.wikimedia.org/T178538
-- Tim Starling
Curious what the Community Tech team has been up to for the past few
months? Come to our showcase presentation at 2pm PDT (9pm UTC) in room 112
(the super big conference room), or watch it on the public YouTube stream:
https://www.youtube.com/watch?v=Cm02V1ytJ0Y
We will be covering:
* CodeMirror (syntax highlighting)
* LoginNotify
* Global Preferences
* XTools
* Popular Pages Bot
* Internet Archive Upload Tool
* Unicode Section IDs
* and ACTRIAL
Hey folks,
We were way overdue for an update, so we just put one together. In the
last 3 months, we added new language support for Bengali, Greek, and Tamil.
New advance edit quality support for Albanian and Romanian. We cleaned up
the old 'reverted' models where better support is available. We're working
on moving to a new dedicated cluster. We improved some models by exploring
new sources of signal and cleaning datasets. We started work on JADE and
presented on The Keilana Effect at Wikimania.
Read more on our blog
https://phabricator.wikimedia.org/phame/post/view/77/status_update_october_…
-Aaron
On Sat, Jun 3, 2017 at 3:28 PM, Aaron Halfaker <aaron.halfaker(a)gmail.com>
wrote:
> Hey folks,
>
> I'll be starting to post updates here on our new blog[1], but if you'd
> prefer to be notified via the mailing lists we used to post to, that's OK.
> I'll make sure that the highlights and the link to these posts gets pushed
> there too.
>
> We had a big presence at the Wikimedia Hackathon 2017 in Vienna. We kicked
> off a lot of new language focused collaborations (Greek, Tamil, Bengali)
> and we deployed a new Item Quality model for Wikidata.
>
> French and Finnish Wikipedias now have advance edit quality prediction
> support!
>
> ORES is available through api.php again via rvprop=orescores and
> rcprop=oresscores.
>
> Wiki labels now has a new stats reporting interface. Check out
> https://labels.wmflabs.org/stats
>
> We had a major hiccup when failing over to CODFW, but we worked it out and
> ORES is very happy again.
>
> See more details on our new blog: "Score all the things"
> https://phabricator.wikimedia.org/phame/blog/view/8/
>
> -Aaron
> Principal Research Scientist @ WMF
> Head of the Scoring Platform team
>