This is now done and deployed in production! Thanks to everyone involved.
Special thanks to Tyler and Chad for their help with the rather
unexpectedly messy deployment.
The next step would be to break the MobileFrontend dependency on the
Minerva skin. I've setup an epic
to be filed as I find them) and would appreciate help doing this if anyone
is looking for a fun side project and interested in improving our skin
There is a milestone on the MinervaNeue project tracking all open bugs:
Your help is welcomed and appreciated!!
On Tue, Jul 4, 2017 at 10:46 AM יגאל חיטרון <khitron(a)post.bgu.ac.il>
Hi. The link  is dead.
2017-07-04 20:45 GMT+03:00 Gergo Tisza <gtisza(a)wikimedia.org>rg>:
Nice! Thanks for working on this.
On Mon, Jul 3, 2017 at 7:03 PM, Jon Robson <jrobson(a)wikimedia.org> wrote:
Back in 2014, Legoktm made the sensible suggestion  that we should
the skin portion of code from the MobileFrontend
I've spent the last few months making it possible and I now plan to make
this a reality. I now plan to make this change on the 12th&13th July
Chad (RainbowSprinkles) .
I'm writing to give notice; answer questions and minimise the disruption
that may cause. A while back when Vector was pulled out of MediaWiki
there was a little bit of pain so I'm keen to
help people avoid this.
make sure you update vagrant. Vagrant will install the new skin
part of the MobileFrontend role and provided you
do `vagrant git-update`
you will not experience any breakage.
If you are not using Vagrant, please install the new skin  and load
using wfLoadSkin (after including MobileFrontend
MobileFrontend stops working thats a sign you need to pull the latest
*3rd parties who are using MobileFrontend in deployed wikis*
aware of this change when updating MobileFrontend. To be safe
you should install the MinervaNeue skin  as part of your deploy
and keep an eye on compatibility.
The MinervaNeue skin and MobileFrontend are being kept backwards
compatibility to ensure we do not break anything in Wikimedia's
cluster, which is detailed in the Phabricator
of the migration I will be porting over translations to the new
skin from MobileFrontend. There may be some changes to the message keys
during this period of time so please bare this in mind when translating.
The goal is to avoid unnecessary translations!
*Why are you doing this?!!?*
tried to write up this here . Feel free to ask questions on the
talk page there. It's a good conversation to have.
*Can I just use MobileFrontend?*
you just have MobileFrontend it will give you a separate mobile
site and you are free to use whatever skin you want there.
*Can I just use the Minerva skin and throw away my mobile site?*
quite. But that's the next step that this enables... :) More on that
to reply to this thread with any concerns or questions you
or any way I can improve this migration.
*Can I do nothing?*
If you do
not update sure, but if you are updating your instance it's
going to break soon if you do not do anything.
Let me know if any questions!
Mobile-l mailing list
Wikitech-l mailing list