Hi,
It's been a while since we had one of these, and 2015 has been a very
busy year! :-)
I'll quote Sumana from last time:
> How about a little email thread for us to say nice things about each
> other? Rules: be kind, thank someone, and say why you're thanking
> them.
> [If you don't get thanked and you feel mopey, email me and I'll
> comfort you. :-)]
I'll start off with thank yous to:
* Addshore, for his awesome work on CatWatch and help with recent
ExtensionDistributor improvements
* YuviPanda, for coming up with unique and useful tools for Wikimedians,
and then following through and building them
* S Page, for consistently nagging me and other developers to improve
documentation
-- Legoktm
So I enabled a beta feature today that is part of reading web's
quarterly goals (read more about read more here if interested [1])
When enabled it showed up in desktop beta features (yey) but the
JavaScript module wasn't loading...
Investigating I discovered that BetaFeatures::isEnabled consults a
config variable called wgBetaFeaturesWhitelist
This makes the feature return false if the feature is not in
wgBetaFeaturesWhitelist
Apparently however you make the feature show up in the
GetBetaFeaturePreferences hook - so the whitelist doesn't actually
apply to things we show to users (which I would say would be more
important...) [2]
The whitelist also asks when enabling to check with James Forrester and Greg
and to note a date 6 months after the last major change. According to
these comments all the listed beta features have passed their expiry
dates.
Will they live here forever - or is it time to talk about beta features?
[1] https://www.mediawiki.org/wiki/Reading/Web/Projects/Read_more
[1] https://phabricator.wikimedia.org/T121182
---------- Forwarded message ----------
From: Kevin Leduc <kevin(a)wikimedia.org>
Date: Fri, Dec 11, 2015 at 11:56 AM
Subject: December Lightning Talks
To: "Staff (All)" <wmfall(a)lists.wikimedia.org>, Engineering list <
engineering(a)lists.wikimedia.org>
Hi All,
December Lightning Talks are in less than 2 weeks (the same week as
Christmas) and there are still a couple of spaces left to present. The
talks are recorded and streamed for people not able to attend in person.
Lightning Talks are an opportunity for teams @ WMF & in the Community to
showcase something they have achieved: a quarterly goal, milestone,
release, or anything of significance to the rest of the foundation and the
movement as a whole.
Each presentation will be 10 minutes or less including time for questions.
Sign up here: https://www.mediawiki.org/wiki/Lightning_Talks#December_2015
Next round of Lightning Talks:
When: Tuesday December 22, 1900 UTC
<http://www.timeanddate.com/worldclock/fixedtime.html?msg=Lightning+Talks&is…>,
11am PST (We have added this Lightning Talk to the WMF Engineering, Fun &
Learning, and Staff calendars)
Where: 5th Floor
Remotees: On-Air google hangout will be provided just before the meeting
IRC: #wikimedia-tech
YouTube stream: http://www.youtube.com/watch?v=cIqhGxtXFbg
Thanks!
Kevin Leduc, Rachel Farrand, Megan Neisler
On Sun, Dec 6, 2015 at 7:30 PM, Bartosz Dziewoński <matma.rex(a)gmail.com>
wrote:
> On 2015-12-04 18:59, Adam Baso wrote:
>
>> I do wonder though if we've spent much time studying the ease of getting
>> at
>> least some part of oojs-ui split out or making it so that new stuff going
>> forward is part of the oojs-ui family but it's not as monolithich?
>>
>
> Not any more than what is written at <
> https://phabricator.wikimedia.org/T113681#1673158>, as far as I know.
>
> OOjs UI doesn't have a dedicated team (or even a dedicated person)
> supporting it. The changes are mostly driven by whatever the VisualEditor
> or Design teams need, and what they are willing to implement themselves
> (and to a lesser extent, Multimedia team and random people like Brad or
> Florian). This makes it difficult to make any big changes happen.
>
If OOjs UI is the thing that we're supposed to be using in the future for
our UI stuff, it's very concerning that further development is blocked on
T113681 but no one is planning on working on that task or feels ownership
for the thing.
Is someone going to step up to actually own and maintain the thing? Or
should we consider declaring it a failure and figure out a plan to move
away from it, if no one wants to maintain our home-grown JS UI library
anymore?
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
On Sat, Dec 5, 2015 at 1:55 PM, Legoktm <legoktm.wikipedia(a)gmail.com> wrote:
> It's been a while since we had one of these, and 2015 has been a very
> busy year! :-)
ie Appreciation thread of 2015!
* Santhosh, Niklas and Amir: For all (hard) work on ContentTranslation!
* Runa: For being awesome manager.
* Pau: For amazing design and being 'voice' of the team.
* Alex (akosiaris) + Ops: For all help in Puppet and config.
* Bryan Davis and Reedy and Chad: For helping in emergency
deployment(s) when needed.
Thanks!
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
Hi there,
The WMF has scheduled an office hour with Wes Moran, VP of Product, for
Thursday 10 December, at 20:00 UTC. We can use the time as an informal meet
and greet, or ask questions about product process, strategy, and planning.
You can participate in #wikimedia-office on Freenode, and logs will be
posted afterwards.
You can find the relevant information, including your timezone, here:
https://meta.wikimedia.org/wiki/IRC_office_hours#Upcoming_office_hours
Hope to see you there :)
rachel
--
Rachel diCerbo
Director of Community Engagement (Product)
Wikimedia Foundation
Rdicerb (WMF) <https://meta.wikimedia.org/wiki/User_talk:Rdicerb_%28WMF%29>
@a_rachel <https://twitter.com/a_rachel>
https://www.mediawiki.org/wiki/Scrum_of_scrums/2015-12-09
= 2015-12-09 =
== Reading ==
=== Android ===
* 2.1.135-beta-2015-12-03 published to beta only.
* 2.1.136-* release candidate to be published as beta soon.
** Only bug fixes and polish since v2.1.135.
** New Wikipedia Maps promotion from beta to prod to appear in this release.
** Final planned release of 2015.
=== iOS ===
* Doing regression testing before wider, public beta distribution of
Wikipedia 5.0.0
* Considering Mobile Content Service integration (perhaps as a beta
experiment) as Q3 "reach" goal
** (
https://www.mediawiki.org/wiki/Reading/Quarterly_Planning/Q3#iOS_Goals_.28n…)
=== Mobile Content Service ===
* 10% of Android Beta App users use the RB based service for link previews
(page summary) + page content
=== Reading Infrastructure ===
* We're concerned that oojs-ui is what we're supposedly wanting to move UI
stuff to, but oojs-ui is apparently unowned and development is blocked on
T113681 with no one planning to work on it (and people are being encouraged
to shove stuff into mw.widgets to hack around that block).
** ApiSandbox is now theoretically blocked on Brad finding time to apply
said hack, since we've determined oojs-ui isn't getting new functionality
any time soon..
== Technology ==
=== Security ===
* Reviews: ArticlePlacement (waiting for wikidata), Thumbor in progress,
RevisionJumper this week
* Secure Code training today, 3:30pm PST -
https://lists.wikimedia.org/pipermail/wikitech-l/2015-December/084213.html
* Need help: T118769 (Ops, someone who can help with vcl)
* Goals: 2FA for wiki accounts, and possibly changes to Javascript
permisions (T120889, T120886) . Input welcome.
**
https://www.mediawiki.org/wiki/Wikimedia_Security_Team/Goals_201516#Q3_.28J…
=== Technical Operations ===
* Blocking: none
* Blocked by: none
* Updates:
* Migration from OpenDJ to OpenLDAP successful. Some minor wake from
the migration, solved today
* ops get their yuvikeys one by one
* moving on with scaling alerting monitoring
* drafting Q3 goals
=== Services ===
* Actively working with RelEng on Scap3
:* Current goal: set up AQS in beta
* RESTBase v0.9.0 released
:* many config style changes
:* Analytics - need to coordinate next deploy (config changes)
:* move RESTBase to service::node -
https://gerrit.wikimedia.org/r/#/c/257898/
* EventBus
:* extension emitting events now in Beta, after tests moving to prod (next
week)
:* need security review
:* HTTP proxy service work continues (Analytics)
:* working on change propagation
* CXServer move to service-runner
:* let's schedule the actual merge/deploy, Kartik, Alex
* Goals for next Q: https://phabricator.wikimedia.org/T118868
:* finalisation tomorrow
:* if you have JobRunner jobs, we'd like to talk to you about moving them
to the EventBus
== Release Engineering ==
* *Blocking*: (none)
* *Blocked by*: (none)
* *Updates*:
** Scap3 refactoring and tech debt cleanup
*** https://phabricator.wikimedia.org/project/view/1449/
*** Deployed AQS in Beta Cluster
*** Moving on to support Mathoid
*** One Q3 goal is to support MediaWiki deployments
** Rolling responsibility of cutting MediaWiki branches
*** Bear with noobs
== Discovery ==
* Portal A/B test launched
* Completion suggesters beta feature deployed soon
* Working on Q3 goals
* No blocking/blockers
=== Maps/Graphs ===
* interactive graphs are on the train -
https://test.wikipedia.org/wiki/DynamicGraph
* Do not perform image quality reduction for any zero partners, or it may
corrupt image URLs
* Will push kartographer extension to beta cluster
== Fundraising Tech ==
* Tiny, conservative fixes to Central Notice and payments-wiki
* Bunch of new visualizations for the internal fundraising dashboard
* Dealing with interesting behaviors of the new CiviCRM verison
** Actually upstreaming a bunch of fixes!
* Watching donation streams and error logs
* More testing of backup credit card processor
* Gathering stats on donatewiki clicks
** Will replace 3rd-party email performance tracking, which has been
redirecting users through weird-looking domains
==Community Tech==
* Wrapping up Wishlist Survey
* Working on Gadgets 2.0
* PageAssessments extension - need some help figuring out job/database
scalability
== Editing ==
=== Parsing ===
* Discovered use of "wikitext as a database" page (
https://ur.wikipedia.org/wiki/%D9%86%D8%A7%D9%85_%D9%85%D9%82%D8%A7%D9%85%D…
)
that was being updated multiple times a minute by bots
** Let to a 80% and higher load on the Parsoid cluster over the last 4-6
hours because the DOM is larger than what Parsoid can reliably handle.
** Filed https://phabricator.wikimedia.org/T120972: Introduce configurable
wt2html/html2wt to deal with this; On the RESTBase end, there is
https://phabricator.wikimedia.org/T120971 (Blacklist automatic updates for
especially expensive pages)