Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 4-5 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting: https://www.mediawiki
.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Work has begun to upgrade the base distribution for MediaWiki-Vagrant
to Debian Stretch [0]. The Wikimedia production cluster is preparing
for a similar upgrade [1] which will in part allow the Wikimedia wikis
to migrate to PHP 7 [2].
== What's new in the stretch-migration branch? ==
* Debian Stretch (Debian 9) base image
* Default PHP runtime is Zend PHP 7.0 (HHVM available via role)
* Database is MariaDB 10.1
* Provisioning via Puppet 4
Setting up a basic wiki (no roles enabled) seems to work pretty well.
Additional roles need testing and may require updated Puppet manifests
(Puppet syntax updates, erb syntax updates, package name changes,
additional packages). Help is needed to test roles, file bugs, and
submit patches. With some help I think we can be ready to switch to
Stretch as the default base image in early/mid January.
== Testing the Stretch base image and Puppet profiles ==
Its recommended to test with a fresh MediaWiki-Vagrant checkout so if
things go badly you can easily switch back to your original install
and keep working.
$ git clone --recursive
https://gerrit.wikimedia.org/r/mediawiki/vagrant mwv-stretch
$ cd mwv-stretch
$ git checkout stretch-migration
$ ./setup.sh
$ vagrant up
You can run `vagrant roles list -e -1` to get a nice list of the roles
you have enabled on your normal Trusty VM install to copy over to your
Stretch testing VM. This one-liner liner might even do it for you:
$ cd mwv-stretch
$ vagrant roles enable $(cd ../vagrant; vagrant roles list -e -1)
$ vagrant provision
[0]: https://phabricator.wikimedia.org/T181353
[1]: https://phabricator.wikimedia.org/T174431
[2]: https://phabricator.wikimedia.org/T176370
Bryan
--
Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org>
[[m:User:BDavis_(WMF)]] Manager, Cloud Services Boise, ID USA
irc: bd808 v:415.839.6885 x6855
(The HTML version of this announcement can be found at
https://discourse-mediawiki.wmflabs.org/t/welcome-to-wikimedia-developer-su…
)
https://discourse-mediawiki.wmflabs.org/
Wikimedia Developer Support offers a support channel for all developers
working with MediaWiki or other Wikimedia related technologies: APIs,
extensions, skins, gadgets, templates, bots, tools, apps, data sets… If you
need help with a technical problem, just ask.
This website is based on Discourse. If you have questions about how to use
it, check https://www.mediawiki.org/wiki/Discourse/Help
Your feedback about this website is very important! Bug reports, feature
requests and other suggestions are very welcomed.
IMPORTANT
Wikimedia Developer Support is a pilot project running on a test
instance. This is not the final deployment. More about this project at
https://www.mediawiki.org/wiki/Discourse
* Although the migration of users and content to the production server is
theoretically possible, at this point it is not guaranteed (T184461).
* The authentication system for this test instance is not what will be used
if this project makes it to production.
* If you have a Wikimedia account, use the same email when registering
here. This is how your username and content will remain yours if/when
Wikimedia single sign-on is implemented (T124691).
* Do not reuse your “real” passwords when creating an account in this test
instance.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Awesome, thanks for making it happen and the update!
Cheers
Lydia
On Jan 9, 2018 07:56, "Manuel Arostegui" <marostegui(a)wikimedia.org> wrote:
On Tue, Jan 9, 2018 at 6:50 AM, Manuel Arostegui <marostegui(a)wikimedia.org>
wrote:
> Hello,
>
> We are starting in 10 minutes
>
> On Wed, Jan 3, 2018 at 10:36 AM, Manuel Arostegui <
> marostegui(a)wikimedia.org> wrote:
>
>> Hello everyone
>>
>> Happy new year!
>>
>> This is a reminder.
>>
>> Next Tuesday 9th January at 6:00AM UTC we will have a read only time on
>> s5 for 30 minutes (https://phabricator.wikimedia.org/T181645 ), to
>> proceed and split wikidata onto its own hardware and make the new s8 shard
>> live (https://phabricator.wikimedia.org/T177208).
>>
>> Amir and Katie have kindly agreed to help us with testing and any
>> possible troubleshooting from the code side.
>>
>> Communication and coordination will happen on #wikimedia-operations if
>> anyone else is around and willing to provide another pair of eyes, that
>> would be, of course, much appreciated!
>>
>> Thanks
>> Jaime, Manuel
>>
>>
>>
>>
>>
>>
Hello,
The failover to split s5 and s8 was done successfully (https://phabricator.
wikimedia.org/T177208#3885585)
So now dewiki lives on s5 (not changed) and wikidata has its own set of
servers in a new shard called s8.
Thanks everyone who helped out!
Jaime,Manuel
On Tue, Jan 9, 2018 at 6:50 AM, Manuel Arostegui <marostegui(a)wikimedia.org>
wrote:
> Hello,
>
> We are starting in 10 minutes
>
> On Wed, Jan 3, 2018 at 10:36 AM, Manuel Arostegui <
> marostegui(a)wikimedia.org> wrote:
>
>> Hello everyone
>>
>> Happy new year!
>>
>> This is a reminder.
>>
>> Next Tuesday 9th January at 6:00AM UTC we will have a read only time on
>> s5 for 30 minutes (https://phabricator.wikimedia.org/T181645 ), to
>> proceed and split wikidata onto its own hardware and make the new s8 shard
>> live (https://phabricator.wikimedia.org/T177208).
>>
>> Amir and Katie have kindly agreed to help us with testing and any
>> possible troubleshooting from the code side.
>>
>> Communication and coordination will happen on #wikimedia-operations if
>> anyone else is around and willing to provide another pair of eyes, that
>> would be, of course, much appreciated!
>>
>> Thanks
>> Jaime, Manuel
>>
>>
>>
>>
>>
>>
Hello,
The failover to split s5 and s8 was done successfully (
https://phabricator.wikimedia.org/T177208#3885585)
So now dewiki lives on s5 (not changed) and wikidata has its own set of
servers in a new shard called s8.
Thanks everyone who helped out!
Jaime,Manuel
Forwarding to Wikitech-l and MediaWiki-l for the benefit of technical
people who may be interested in this subject and not subscribed to the
general WikimediaAnnounce-l.
As has been the case for awhile, WikimediaAnnounce-l is not automatically
forwarding to Wikimedia-l, so I'm forwarding this email manually to that
list also.
Have a good weekend.
Pine <https://en.wikipedia.org/wiki/User:CatherineMunro/Bright_Places>
---------- Forwarded message ----------
From: Markus Glaser <glaser(a)hallowelt.com>
Date: Mon, Dec 18, 2017 at 2:36 AM
Subject: [Wikimedia Announcements] Annual report 2017 for MediaWiki
Stakeholders' Group
To: "wikimediaannounce-l(a)lists.wikimedia.org" <wikimediaannounce-l@lists.
wikimedia.org>
Hello,
here is the annual report of the MediaWiki Stakeholders' Group:
https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_
Group/Annual_Report_2017
Best,
Markus Glaser
_______________________________________________
Please note: all replies sent to this mailing list will be immediately
directed to Wikimedia-l, the public mailing list of the Wikimedia
community. For more information about Wikimedia-l:
https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
_______________________________________________
WikimediaAnnounce-l mailing list
WikimediaAnnounce-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikimediaannounce-l
Hello,
test2wiki [0] used to be a group0 wiki, meaning it used to get new
deployments at Tuesday of every week, at the same time that other test
wikis get deployments.
Recently, a major bug in Wikibase was introduced by yours truly [1]. It
happened when changes in Wikibase repo (aka Wikidata) transmitted to a
Wikibase client (aka all other wikis) while repo has the newer version of
mediawiki than the client. Any changes to the way repo transmits changes to
client must stay backward compatible for at least a minor release (=one
week). As you might guess, sometimes it's hard to test these cases.
The decision to prevent such problems in the future was to have one of our
test client wikis (that is connected to test.wikidata.org) kept back for
deployments for one day so we can have a test repo-client connection with
different mediawiki versions. You can read more in about reasoning in the
phabricator task: [2]
So starting from his week, test2wiki will get new releases a day later (in
Wednesdays).
[0]: https://test2.wikipedia.org/wiki/Main_Page
[1]: https://phabricator.wikimedia.org/T182243
[2]: https://phabricator.wikimedia.org/T182326
Best
--
Amir Sarabadani
Software Engineer
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
I often get emails that someone is trying to get into my accounts. I guess
there are just some trolls, trying to login into my Wikipedia account. So
far, these have been unsuccessful.
Now I got an email that someone asked for a temporary password for my
account.
So far so good. What I am wondering is whether that password reset trial is
actually even more dangerous now given Spectre / Meltdown?
Thoughts?
(I probably should set up 2FA right now. Have been too lazy so far)
Happy new year,
Denny
Hello all!
Here are the minutes from this week's meeting:
* Last Call for Comments: Introduce page creation log
<https://phabricator.wikimedia.org/T12331>. If no pertinent issues remain
unaddressed by January 17, this RFC will be approved for implementation. Patch:
<https://gerrit.wikimedia.org/r/#/c/399897/>
* Last Call for Comments: Introduce PlatformSettings.php
<https://phabricator.wikimedia.org/T182020>. If no pertinent issues remain
unaddressed by January 17, this RFC will be approved for implementation.
* First major MCR patches going live next week. The Revision class is now
deprecated, use RevisionStore or RevisionRecord instead.
<https://gerrit.wikimedia.org/r/#/c/399174>
* Patch for MCR database schema is also merged, new tables are not used yet.
<https://gerrit.wikimedia.org/r/#/c/378724/>
* There was an issue with increased response times for several days over the
holidays, the cause is still unknown. Ops is investigating.
* The #architecture project on phabricator has been archived, since nobody was
using the associated workboard. Could be revived as a plain “yellow” tag if needed.
* TechCom to use next week’s meeting for going over old/stale RFCs
You can also find our meeting minutes at
<https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes>
See also the TechCom RFC board
<https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>.
--
Daniel Kinzler
Principal Platform Engineer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.
Hello all!
Addshore last night merged the patch[1] that is the first major step towards
Multi-Content-Revisions[2]: it completely guts the Revision class and turns it
into a thin proxy for the new RevisionStore service. The new code is now live
on beta.
This is our second attempt: The first one, on December 18th, thoroughly
corrupted the beta database. It took us some time and a lot of help from Aaron
and especially Roan to figure out what was happening. A detailed post-mortem by
Roan can be found at [3].
Anyway - this stage of MCR development introduces the new multi-revision capable
interface for revision storage (and blob storage) [4]. It does not yet introduce
the new database schema, that will be the next step [5][6]. While doing the
refactoring, I tried to keep the structure of the existing code mostly intact,
just moving functionality out of Revision into the new classes, most importantly
RevisionRecord, RevisionStore, and BlobStore.
Beware that with the next deployment (due January 2nd) the live sites will start
using the new code. Please keep an eye out for any strangeness regarding
revision handling. Adam greatly improved test coverage of the relevant code
(thanks Adam!), but it's always possible that we missed some edge case, maybe
something about archived revisions that were partially migrated from on old
schema or something similarly fun.
Exiting times!
Cheers
Daniel
[1] https://gerrit.wikimedia.org/r/#/c/399174/
[2] https://www.mediawiki.org/wiki/Requests_for_comment/Multi-Content_Revisions
[3] https://phabricator.wikimedia.org/T183252#3853749
[4] https://phabricator.wikimedia.org/T174025
[5] https://phabricator.wikimedia.org/T174024
[6] https://phabricator.wikimedia.org/T174030
--
Daniel Kinzler
Principal Platform Engineer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.