Hello and welcome to the latest (and late, sorry) edition of the WMF
Engineering Roadmap and Deployment update.
The full log of planned deployments next week can be found at:
<https://wikitech.wikimedia.org/wiki/Deployments#Week_of_July_14th>
A quick list of notable items...
== Monday ==
* The mobile team will be submitting iOS app to AppStore
** There's an unknown review timeline from Apple
* CirrusSearch
** CirrusSearch will be turned on as primary on Dutch Japanese
Wikipedias.
** See the full timeline for the remaining wikis at:
<https://www.mediawiki.org/wiki/Search#Timeline>
== Tuesday ==
* MediaWiki deploy
** group1 to 1.24wmf11: All non-Wikipedia sites (Wiktionary, Wikisource,
Wikinews, Wikibooks, Wikiquote, Wikiversity, and a few other sites)
** <https://www.mediawiki.org/wiki/MediaWiki_1.24/wmf13>
== Wednesday ==
* Weekly fundraising banner test
* CirrusSearch
** CirrusSearch will be turned on as primary on Polish and Russian
Wikipedia
== Thursday ==
* MediaWiki deploy
** group2 to 1.24wmf13 (all Wikipedias)
** group0 to 1.24wmf14 (test/test2/testwikidata/mediawiki)
Thanks and as always, questions and comments welcome,
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
Hi we are upgrading jquery cookie from an early alpha version of 1.1 to 1.2. Please start upgrading your code to be compatible with jquery cookie 1.2. There is just one deprecations to notice and that is $.cookie('foo', null) is now deprecated. And replace it with Adding $.removeCookie('foo') for deleting a cookie. We are slowly upgrading to version 1.4.1 but one step at a time because it is. And please also follow this change log github.com/carhartl/jquery-cookie/blob/master/CHANGELOG.md so that we can upgrade to 1.4.1.
Minutes and slides from Wednesday's quarterly review of the Foundation's
Core features team (focusing on the work on Flow) are now available at
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter…
.
On Wed, Dec 19, 2012 at 6:49 PM, Erik Moeller <erik(a)wikimedia.org> 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_r…
>
> 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
> Wikimedia-l(a)lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>
--
Tilman Bayer
Senior Operations Analyst (Movement Communications)
Wikimedia Foundation
IRC (Freenode): HaeB
Hello all,
We're in negotiations with one of applicants for the MediaWiki release
management RFP and will make the official announcement ASAP, likely
early next week.
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
The 'jquery.json' module has been deprecated, and we plan to remove it
in MW 1.25. You can replace it with the 'json' module.
* In your extension or gadget's ResourceLoader dependencies, change
'jquery.json' to 'json'
* Use JSON.stringify instead of $.toJSON
* Use JSON.parse instead of $.parseJSON (the latter is actually part of
jQuery proper, and not being removed currently, but this allows you to
be consistent and us the standard ECMAScript 5 JSON API for both
directions).
There are some less commonly used JSON APIs in jquery.json. See the
code
(https://git.wikimedia.org/blob/mediawiki%2Fcore.git/5ca4bea3d380911c458659e…),
and feel free to ask.
The benefit is that users with modern browsers (which have JSON
built-in), will not have to download any JSON implementation (currently,
they download jquery.json). Older browsers will still work, but they
will download the JSON implementation.
Thanks,
Matt Flaschen
Hi,
Gerrit change Id819246a9 proposes an implementation for a recent changes
stream broadcast via socket.io, an abstraction layer over WebSockets that
also provides long polling as a fallback for older browsers. Comment on <
https://gerrit.wikimedia.org/r/#/c/131040/> or the mailing list.
Thanks,
Ori
I just stumbled across <https://github.com/wikimedia/mediawiki-core/pull/19>,
a small but useful contribution to core from an HHVM developer. It has gone
unnoticed for two months, which is a bit sad.
Is there a way to accept pull-requests from GitHub? According to <
https://github.com/wikimedia/mediawiki-core/settings/hooks> (may not be
visible to non-Wikimedians, sorry), the WebHook receiver <
http://tools.wmflabs.org/suchaserver/cgi-bin/receiver.py> is defunct.
Anyone know the story there?
It'd be good if some additional people were watching (that is, receiving
notifications for) <https://github.com/wikimedia/mediawiki-core/>.
I haven't responded yet, by the way, so feel free to if you know the
answers to these questions. I don't know what effect accepting the
pull-request will have on the code in master, and telling someone who has
already submitted a patch to go sign up for Gerrit seems impolite.
Ori
Since 2008, we've offered a small feature to download printed books
from Wikipedia article. This is done in partnership with a company
called PediaPress.
They've sold about 15K books over that time period, not enough to
break even, and the support/maintenance burden for the service is no
longer worth it for them.
We'll disable this feature in coming weeks. We'd only continue to
offer it if there's 1) strong community interest in maintaining it,
and 2) a partner who steps up to provide the service.
We'll continue to provide PDF downloads (soon with a new rendering engine).
Thanks,
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Hello,
I've recently had a server disaster and had to recover my wiki from
backup dumps. But after importing all the special characters are mangled
causing many links to be broken and pages that have special characters
in the titles are missing!
Here's an example of a page with many broken characters and red links
showing for pages with special characters in the titles.
http://www.organicdesign.co.nz/2014_Holiday_in_Brazil
I'm sure this must be able to be fixed because when I look at the DB
content from the shell by selecting content from the text table all the
special characters are rendering with no problem...?
I noticed that the mysqdump command was using
--default-character-set=latin1 which may be a legacy setting now?
Help much appreciated
Thanks a lot,
Aran