Nice! Thanks for working on this.
On Mon, Jul 3, 2017 at 7:03 PM, Jon Robson <jrobson(a)wikimedia.org> wrote:
> Dear all
> Back in 2014, Legoktm made the sensible suggestion [1] that we should pull
> the skin portion of code from the MobileFrontend extension.
>
> 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 with
> Chad (RainbowSprinkles) [2].
>
> 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 core,
> there was a little bit of pain so I'm keen to help people avoid this.
>
> *Developers:*
> Please make sure you update vagrant. Vagrant will install the new skin as
> 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 [3] and load it
> using wfLoadSkin (after including MobileFrontend extension). When
> MobileFrontend stops working thats a sign you need to pull the latest code
> from Master.
>
> *3rd parties who are using MobileFrontend in deployed wikis*
> Please be aware of this change when updating MobileFrontend. To be safe
> you should install the MinervaNeue skin [3] as part of your deploy process
> 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 production
> cluster, which is detailed in the Phabricator task [4].
>
> *Translators*
> As part 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?!!?*
> I've tried to write up this here [5]. Feel free to ask questions on the
> talk page there. It's a good conversation to have.
>
> *Can I just use MobileFrontend?*
> Sure. If you just have MobileFrontend it will give you a separate mobile
> site and you are free to use whatever skin you want there.
> https://www.mediawiki.org/wiki/Extension:MobileFrontend#Setup_a_skin
>
> *Can I just use the Minerva skin and throw away my mobile site?*
> Not quite. But that's the next step that this enables... :) More on that
> later.
>
> *Any questions?*
> Feel free to reply to this thread with any concerns or questions you have
> 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!
> Jon
>
> [1] https://phabricator.wikimedia.org/T71366
> [2] https://wikitech.wikimedia.org/wiki/Deployments#Week_of_July_10th
> [3] https://github.com/wikimedia/mediawiki-skins-MinervaNeue
> [4] https://phabricator.wikimedia.org/T166748
> [5] https://www.mediawiki.org/wiki/Reading/Web/
> MobileFrontend_and_Minerva#..._but_why_do_we_care_about_
> Minerva_as_a_desktop_skin.3F
>
>
> _______________________________________________
> Mobile-l mailing list
> Mobile-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
Wikimedia Developers,
With the change to a new annual plan and fiscal year, we’ve made some
changes to how the Contributors team, formerly known as the Editing
department, is organized. I believe these changes will help us better serve
our communities and make judicious use of donor funds, by making our teams
more capable of taking on large projects while maintaining production
software. I also believe these changes will better support for our staff by
helping many of them who have been wearing many hats for a long time
achieve greater focus.
The first and most significant change is that the Language and
Collaboration teams have merged to become the Global Collaboration team.
Runa Bhattacharjee, who has managed the Language team since 2014, will
manage the new combined team. Roan Kattouw, who has led and managed the
Collaboration team for the past two years, has now taken off his people
manager hat, and is now focused on being the Lead Engineer of the new team.
By merging, this new team will have the ability to incorporate engineering,
design, QA and community engagement more fluidly, meeting the specific
needs of each project and allowing team members to share their individual
expertise to a greater number of products.
Additionally, as Toby mentioned last month, the Dan Garry has joined the
team responsible for editing tools like VisualEditor, allowing James to
step away from his 5-year stint as the Product Manager for VisualEditor and
focus on leading product for Contributors. With this change comes a new
name for the VisualEditor team, which is now (back to being called) the
Editing team.
It will likely take some time for these changes to fully propagate through
all the wikis and development tools and many staff are currently in
transitional roles. If you have any questions about these changes, please
let me know and I’ll do my best to help you.
Thanks,
Trevor Parscal
--
- Trevor
Forwarding.
Pine
---------- Forwarded message ----------
From: Katherine Maher <kmaher(a)wikimedia.org>
Date: Mon, Jul 3, 2017 at 4:36 PM
Subject: Re: [Wikimedia-l] Wikimedia Foundation Annual Plan FY2017-2018
To: wikimediaannounce-l(a)lists.wikimedia.org, Wikimedia Mailing List <
wikimedia-l(a)lists.wikimedia.org>, "wmfall(a)lists.wikimedia.org" <
wmfall(a)lists.wikimedia.org>
Hi all,
The Wikimedia Foundation is pleased to announce that the final version of
our Annual Plan is now available on Meta. [1] The Annual Plan was approved
by the Board of Trustees on June 16th.
This Annual Plan continues to align the Foundation’s work to the strategic
priorities set out in the interim strategic plan for 2016-18: reach,
communities, and knowledge. We have introduced cross-departmental planning
that will drive several large programs this year. We will be continuing to
invest in our core work while investing in our future through the Movement
Strategy work, the contribution to the endowment, and our work on
Wikimedia’s identity and public awareness.
>From all of us here at the Foundation, we thank the FDC and everyone who
asked questions and provided feedback on the Annual Plan throughout its
development. This feedback continues to challenge us and push us to improve
our planning, our programs, and the way that we share our work. We have
incorporated some of your feedback directly into the plan, and know that
there are other areas where we can continue to evolve and improve.
In our work, in collaboration, and in the spirit of the mission, we look
forward to the year ahead!
Yours,
Katherine
[1]
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_
Annual_Plan/2017-2018/Final
On Fri, Apr 7, 2017 at 7:11 PM, Katherine Maher <kmaher(a)wikimedia.org>
wrote:
> Hi everyone,
>
> I'm pleased to announce that the Wikimedia Foundation's Annual Plan is now
> on Meta.[1]
>
> This year we are continuing to adhere to the three strategic priorities
> laid out in the 2016-2018 interim strategic plan: reach, communities, and
> knowledge.
>
> Across the organization, we've introduced cross-departmental programs and
> planning, with a holistic approach to program support that draws on our
> community, technical, and other capacities. We feel that this new approach
> creates stronger and better outcomes for programs, and is also clearer as
> to what the Foundation is prioritizing. Some examples of these
> cross-departmental programs include New Readers, Structured Data, and
> Community Health, which have been discussed on this list and on wiki
> throughout the past year.
>
> Throughout the rest of the organization and department programs, we're
> continuing to invest in the areas we identified through the 2016-2018
> interim strategic plan, as well as core work such as operational
> improvements, deepening diversity and inclusion, improving privacy and
> security, and funding the Wikimedia endowment.
>
> Thank you all for your support over the past year. Your participation in
> the movement strategy process launched this year is deeply appreciated,
and
> it is remarkable to think that next year's plan will begin to incorporate
> the directions we design together.
>
> In the meanwhile, I'm looking forward to your feedback on this year's
> proposed plan during this open comment period.
>
> Yours,
> Katherine
>
> [1] https://meta.wikimedia.org/wiki/Wikimedia_Foundation_
> Annual_Plan/2017-2018/Draft
>
> --
> Katherine Maher
>
> Wikimedia Foundation
> 149 New Montgomery Street
> San Francisco, CA 94105
>
> +1 (415) 839-6885 ext. 6635 <(415)%20839-6885>
> +1 (415) 712 4873 <(415)%20712-4873>
> kmaher(a)wikimedia.org
>
--
Katherine Maher
Wikimedia Foundation
149 New Montgomery Street
San Francisco, CA 94105
+1 (415) 839-6885 ext. 6635
+1 (415) 712 4873
kmaher(a)wikimedia.org
https://annual.wikimedia.org
_______________________________________________
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
wiki/Wikimedia-l
New messages to: Wikimedia-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
Hello!
MediaWiki-Codesniffer 0.10.0 is now available for use in your MediaWiki
extensions and other projects. This release fixes bugs from 0.9.0 as
well as some new features:
* Add sniff to prevent against using PHP 7's Unicode escape syntax
(Kunal Mehta)
* Add sniff to verify type-casts use the short form (bool, int) (Kunal
Mehta)
* Add sniff for `&$this` that causes warnings in PHP 7.1 (Kunal Mehta)
* Clean up DbrQueryUsageSniff (Umherirrender)
* Ensure all FunctionComment sniff codes are standard (Kunal Mehta)
* Exclude common folders (Umherirrender)
* Fix handling of nested parenthesis in ParenthesesAroundKeywordSniff
(Kunal Mehta)
* IllegalSingleLineCommentSniff: Check return value of strrpos strictly
(Kunal Mehta)
* Improve handling of multi-line class declarations (Kunal Mehta)
* Include sniff warning/error codes in test output (Kunal Mehta)
* Make DisallowEmptyLineFunctionsSniff apply to closures too (Kunal Mehta)
* Use correct notation for UTF-8 (Umherirrender)
I'll be working on submitting patches for extensions again shortly.
Thanks,
-- Legoktm
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2017-06): 425
Active Maniphest users (any activity) in (2017-06): 896
Task authors in (2017-06): 495
Users who have closed tasks in (2017-06): 283
Projects which had at least one task moved from one column to another on
their workboard in (2017-06): 271
Tasks created in (2017-06): 2634
Tasks closed in (2017-06): 2157
Open and stalled tasks in total: 34850
Median age in days of open tasks by priority:
Unbreak now: 14
Needs Triage: 288
High: 507
Normal: 696
Low: 947
Lowest: 926
(How long tasks have been open, not how long they have had that priority)
Active Differential users (any activity) in (2017-06): 28
TODO: Numbers which refer to closed tasks might not be correct, as
described in https://phabricator.wikimedia.org/T1003 .
Yours sincerely,
Fab Rick Aytor
(via community_metrics.sh on iridium at Sat Jul 1 00:00:21 UTC 2017)