[Wikitech-l] [BREAKING CHANGE] Deprecated JavaScript methods to be removed in MediaWiki 1.25

2014-09-20 Thread Krinkle 
TL;DR:
* Several deprecated methods in MediaWiki's JavaScript modules will be removed
in a few weeks' time.
* Ensure your code no longer uses these methods and update it if needed.
* Check and fix any gadgets or scripts you or your wikis rely upon.

As part of the regular update cycle, a number of deprecated methods in our
JavaScript modules will be removed in the MediaWiki 1.25 release. This is an
announcement to give people notice they should update any extensions, gadgets
and scripts they have written, maintain, or rely upon.

Usually we don't give this much attention to removal of deprecated methods,
but due to this being our first proper development cycle for our front-end
code base, I want to make sure this reaches everyone. You're likely not yet in
the habit of updating front-end code between MediaWiki releases.

Deprecated methods to be removed in MediaWiki 1.25:

* Remove mw.user.name() method. [1]
Deprecated since MediaWiki 1.20. Use mw.user.getName() instead.

* Remove mw.user.anon() method. [1]
Deprecated since MediaWiki 1.20: Use mw.user.isAnon() instead.

* Remove mediawiki.api methods' "ok" and "err" callback parameters. [2]
Deprecated since MediaWiki 1.23. Use the returned Promise interface instead.

* Remove mediawiki.api.category "async" parameter. [2]
Deprecated since MediaWiki 1.23. The ability to override $.ajax() to be
synchronous has been removed. The default (asynchronous) behaviour remains.
Use the Promise interface to retreive the fetched data from the API.

* Remove jquery.json module.
Deprecated since MediaWiki 1.24. [3] Use standardised JSON.stringify and
JSON.parse methods. And depend on the "json" module which will automatically
load a polyfill in older browsers.

## Timeline

These removals will land in MediaWiki 1.25alpha in early October 2014, and
deployed to Wikimedia wikis the week after from October 4th onwards (1.25wmf2).

The MediaWiki 1.25.0 stable release is expected to come out around
April 2015.

You should make sure that your code is updated before your wiki upgrades to
MediaWiki 1.25. If you know code you rely upon will be affected but don't know
how to fix it, please check with your wiki's community for local experts. If
none of them can help, you can ask for assistance on the wikitech-ambassadors
mailing list. [5]

## Reminders

In case you've missed the previous announcements:

* The migration period for jQuery core is still on-going and is also scheduled
for MediaWiki 1.25. [4] More about that in the mail from June 2014:

https://www.mail-archive.com/mediawiki-l%40lists.wikimedia.org/msg13651.html

* Learn about deprecation notices and how you can see them in your browser.

https://www.mail-archive.com/wikitech-l%40lists.wikimedia.org/msg72198.html

[1] https://gerrit.wikimedia.org/r/#/c/111422/
[2] https://gerrit.wikimedia.org/r/#/c/118733/
[3] https://gerrit.wikimedia.org/r/#/c/140560/
[4] https://gerrit.wikimedia.org/r/#/c/137168/
[5] https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

-- Krinkle

PS: You can get a sense of the progress on our different migrations, past and
present, via these graphs: http://codepen.io/Krinkle/full/zyodJ/


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wikimedia-l] Invitation to beta-test HHVM

2014-09-20 Thread Guillaume Paumier 
Hello,

On Sat, Sep 20, 2014 at 9:32 PM, Rand McRanderson  wrote:
> Here is one idea. A dashboard of top level Wikimedia projects with
> statuses, estimates, and a key to terms. Or does this exist?

There is https://www.mediawiki.org/wiki/Wikimedia_Engineering/Dashboard

It doesn't have everything you mentioned, but we can build on it and improve it.

-- 
Guillaume Paumier

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Fixing PollNY -- ResourceLoader woes

2014-09-20 Thread Jack Phoenix 
On Wed, Sep 17, 2014 at 10:05 PM, Daniel Friesen  wrote:

> It should, if it's still broken there should be some other issue.
>
> What errors do you get, before and aster.


Same old "TypeError: LightBox is not defined". At first I was thinking of
cache pollution, but that doesn't seem to be the problem here, since I've
purged my caches and the problem just seems to persist.
I've wrapped all three usages (onload handler, Poll.loadingLightBox() and
Poll.goToNewPoll()'s .done() handler) around the mw.loader.using call you
suggested, but to no avail. As you'd guess, it still magically works with
debug=true in the URL.


Thanks and regards,
--
Jack Phoenix
MediaWiki developer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] REL1_24 branched in core

2014-09-20 Thread Antoine Musso 
Le 20/09/2014 00:15, Legoktm a écrit :
> Hi,
> 
> I just merged  and branched
> core to the commit before it. If someone could take care of branching
> extensions that would be wonderful, otherwise I'll figure out how to do
> that over the weekend.
> 
> Bugs tagged for 1.24 release:
> ,
> some have open patches awaiting review!

Hello,

I have adjusted CI to take in account REL1_24

https://gerrit.wikimedia.org/r/#/q/I515b5e21779120ca143a0ed8ec2c99948adec607,n,z



-- 
Antoine "hashar" Musso


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wikimedia-l] Quarterly reviews of high priority WMF initiatives

2014-09-20 Thread Tilman Bayer 
Minutes and slides from Wednesday's quarterly review meeting of the
Foundation's Growth team are now available at
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterly_reviews/Growth/September_2014
.

On Wed, Dec 19, 2012 at 6:49 PM, Erik Moeller  wrote:
> Hi folks,
>
> to increase accountability and create more opportunities for course
> corrections and resourcing adjustments as necessary, Sue's asked me
> and Howie Fung to set up a quarterly project evaluation process,
> starting with our highest priority initiatives. These are, according
> to Sue's narrowing focus recommendations which were approved by the
> Board [1]:
>
> - Visual Editor
> - Mobile (mobile contributions + Wikipedia Zero)
> - Editor Engagement (also known as the E2 and E3 teams)
> - Funds Dissemination Committe and expanded grant-making capacity
>
> I'm proposing the following initial schedule:
>
> January:
> - Editor Engagement Experiments
>
> February:
> - Visual Editor
> - Mobile (Contribs + Zero)
>
> March:
> - Editor Engagement Features (Echo, Flow projects)
> - Funds Dissemination Committee
>
> We’ll try doing this on the same day or adjacent to the monthly
> metrics meetings [2], since the team(s) will give a presentation on
> their recent progress, which will help set some context that would
> otherwise need to be covered in the quarterly review itself. This will
> also create open opportunities for feedback and questions.
>
> My goal is to do this in a manner where even though the quarterly
> review meetings themselves are internal, the outcomes are captured as
> meeting minutes and shared publicly, which is why I'm starting this
> discussion on a public list as well. I've created a wiki page here
> which we can use to discuss the concept further:
>
> https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings/Quarterly_reviews
>
> The internal review will, at minimum, include:
>
> Sue Gardner
> myself
> Howie Fung
> Team members and relevant director(s)
> Designated minute-taker
>
> So for example, for Visual Editor, the review team would be the Visual
> Editor / Parsoid teams, Sue, me, Howie, Terry, and a minute-taker.
>
> I imagine the structure of the review roughly as follows, with a
> duration of about 2 1/2 hours divided into 25-30 minute blocks:
>
> - Brief team intro and recap of team's activities through the quarter,
> compared with goals
> - Drill into goals and targets: Did we achieve what we said we would?
> - Review of challenges, blockers and successes
> - Discussion of proposed changes (e.g. resourcing, targets) and other
> action items
> - Buffer time, debriefing
>
> Once again, the primary purpose of these reviews is to create improved
> structures for internal accountability, escalation points in cases
> where serious changes are necessary, and transparency to the world.
>
> In addition to these priority initiatives, my recommendation would be
> to conduct quarterly reviews for any activity that requires more than
> a set amount of resources (people/dollars). These additional reviews
> may however be conducted in a more lightweight manner and internally
> to the departments. We’re slowly getting into that habit in
> engineering.
>
> As we pilot this process, the format of the high priority reviews can
> help inform and support reviews across the organization.
>
> Feedback and questions are appreciated.
>
> All best,
> Erik
>
> [1] https://wikimediafoundation.org/wiki/Vote:Narrowing_Focus
> [2] https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings
> --
> Erik Möller
> VP of Engineering and Product Development, Wikimedia Foundation
>
> Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
>
> ___
> Wikimedia-l mailing list
> wikimedi...@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l



-- 
Tilman Bayer
Senior Operations Analyst (Movement Communications)
Wikimedia Foundation
IRC (Freenode): HaeB

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wikimedia-l] Invitation to beta-test HHVM

2014-09-20 Thread Pine W 
Do we have a published guideline somewhere about MediaWiki quality
standards for pre-alpha, alpha, beta, and production releases of elements
like MediaViewer, VisualEditor, Flow, Winter, and HHVM?

Pine
On Sep 20, 2014 12:14 AM, "Jon Work"  wrote:

> :}   I am always impressed by those of you for whom English is not your
> native tongue. It can be very complicated to understand some of the
> shortcuts we use.
>
> Sent from my iPad
>
> > On 20 Sep 2014, at 02:22, MZMcBride  wrote:
> >
> > Anders Wennersten wrote:
> >> I also did soma very subjective test on response times and found the new
> >> feature to give 1-3 s quicker response, which is quite much (6s-5s,
> >> 7s-4s) and make a big difference in the user experience.
> >
> > Woo! :D
> >
> >> Also after reflecting on my little harsh reaction on the deployment
> >> process, I wonder if it is not a language/communication issue
> >>
> >> Being a non-native English speaking person I must admit I have no idea
> >> of the meaning "intrepid" means in "for intrepid beta testers".  It
> >> seems for Guillaume it means "hey this is badly tested, but use if you
> >> have patience/courage" which I can accept as a message of a testrelease
> >>
> >> Also in my backgroud working in a company making internal deployment of
> >> software for 4000 internal users, I am used of making a huge difference
> >> in "ready for Alpha test" and "ready for Beta test", but perhaps my
> >> reference frame is inappropriate in this case, where perhaps a beta
> >> functionality means "Software for testing, not ready for release" and
> >> covering both my distinctions
> >>
> >> So I apologize if I used too strong wordings and instead want to
> >> congratulate you on releasing a good function where you so speedily
> >> fixed the bug!
> >
> > No worries. Thank you for taking the time to write up this message
> > explaining. I think there are definitely ways in which we can improve our
> > communication about beta (or alpha!) features, including attempting to
> > label them appropriately and making sure the message is suitably clear.
> > Your constructive feedback will help us do better in the future.
> >
> > MZMcBride
> >
> >
> >
> > ___
> > Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> > wikimedi...@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> wikimedi...@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l