Google Code-in 2016 ended today.
Our students resolved a total of 424 Wikimedia tasks. Thanks to our 46
mentors for being available, also on weekends & holidays. Thanks to
everybody on IRC for your friendliness, patience, and help provided.
Some latest students' achievements:
* jQuery.suggestions used to add reason suggestions to block/delete/protect forms
* Created a {{PAGELANGUAGE}} magic word
* The Newsletter extension received more fixes and improvements
* Integrated SwaggerUI with the service template
* Special:PageLanguage allows a user to enter a reason/comment
* More MediaWiki code removed that was marked for removal in a past release
* More updated screencast videos on the Phabricator help pages
* More split videos of Wikimedia's CREDIT showcases
* https://meta.wikimedia.org/wiki/Research_on_open_source_team_communication_…
The Grand Prize winners & finalists will be announced on January 30th.
Do you have any ideas or feedback what to improve for next time?
Add it to https://phabricator.wikimedia.org/T154620 !
Again congratulations everybody, and thanks for your hard work!
See you around on IRC, mailing lists, Gerrit, and Phabricator!
Cheers,
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
Hello,
I have a login system that extends the
AbstractPrimaryAuthenticationProvider and uses an AuthenticationRequest
that returns an empty fields array so that the login form is bypassed
completely and login is determined by some other environmental
parameters. But in 1.27 this does not bypass the login form.
What is the proper way I should be making the login page determine login
without a login form?
Thanks,
Aran
Hi all!
This is a Final Call for Comments on the RFC on Content Model Storage [1][2]. If
no new and serious objections are raised within a week, the Architecture
Committee will approve this RFC and drive its implementation.
The RFC on Content Model Storage was originally approved in 2015, but was then
postponed in favor of another RFC, which proposes to create a separate content
meta-data table [3] as part of the move towards multi-content revisions (MCR) [4].
However, MCR in turn got stuck on database performance concerns. So we now
propose to go ahead with implementing the original RFC. The idea is to assign a
number to every content model (and content format), and then use these numbers
to refer to the models and formats in the database, instead of repeating the
same string millions of times (which is my fault btw, sorry about that).
Since the original RFC was already approved, and the situation does not seem to
have changed since then, we see no need for another round of discussions. If
nobody raises any new and serious objections within a week, this should be good
to go.
Cheers,
Daniel
[1] https://phabricator.wikimedia.org/T105652
[2] https://www.mediawiki.org/wiki/Requests_for_comment/Content_model_storage
[3] https://phabricator.wikimedia.org/T142980
[4]
https://www.mediawiki.org/wiki/Multi-Content_Revisions/Content_Meta-Data#Da…
--
Daniel Kinzler
Senior Software Developer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.
Hi.
Re: https://phabricator.wikimedia.org/T99483
This is a task proposing dividing XML dumps by the numeric page namespace
ID (such as 2 for User pages). Please share your thoughts on the task.
It's currently unclear whether implementing this task would result in
getting rid of the "pages-articles" dump. We could keep generating it, but
it costs a non-negligible amount of disk space to do so. If you regularly
use the "pages-articles" XML dump format and have thoughts about keeping
it as-is or changing it, please comment on the task.
If someone could forward this e-mail to the xmldatadumps-l and
wiki-research-l mailing lists, I would very much appreciate it.
MZMcBride
Hello,
The Wikimedia Jenkins system now uses NodeJS version 6 (was 4).
That is part of a plan to upgrade the Wikimedia cluster to 6 which is
tracked on: https://phabricator.wikimedia.org/T149331
If you see any issue with the *node-6-jessie Jenkins jobs, please fill
them as sub tasks of T149331 and add in #contint Phabricator project.
Thanks Paladox for the CI configuration change and everyone that has
been involved in ensuring our most important softs are compatibles.
--
Antoine "hashar" Musso
That's right! At the Wikimedia Developer Summit we decided to organize a
Developer Wishlist Survey, and here we go:
https://www.mediawiki.org/wiki/Developer_Wishlist
The Wikimedia technical community seeks input from developers for
developers, to create a high-profile list of desired improvements. The
scope of the survey includes the MediaWiki platform (core software, APIs,
developer environment, enablers for extensions, gadgets, templates, bots,
dumps), the Wikimedia server infrastructure, the contribution process, and
documentation.
The best part: we want to have the results published by Wednesday, February
15. Yes, in a month, in order to have a higher chance to influence the
Wikimedia Foundation annual plan FY 2017-18.
There's no time to lose. *Propose your ideas before the end of January,*
either pushing existing tasks in Phabricator or creating new ones. You can
find instructions in the wiki page. Questions and feedback are especially
welcome in the related Talk page.
The voting phase is expected to start on February 6 (tentative). What this
space (or even better, the wiki page).
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hashar did some magic and replaced our use of `puppet doc` with yard
which is now generating prettier and more useful documentation of the
roles and other Puppet components in the MediaWiki-Vagrant project. Go
check them out if you are interested:
<https://doc.wikimedia.org/mediawiki-vagrant/>. Try searching for
"role::" to get the list of all roles.
Bryan
--
Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org>
[[m:User:BDavis_(WMF)]] Sr Software Engineer Boise, ID USA
irc: bd808 v:415.839.6885 x6855