[Wikitech-l] 2016-03-23 Scrum of Scrums notes

[Grace Gellerman]

https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-03-23

= *2016-03-2**3* =

== Product ==
=== Community Tech ===
* '''Blocking''':
** None
* '''Blocked''':
** Waiting for jcrespo to do schema change for category sorting:
https://phabricator.wikimedia.org/T130692
* '''Updates''':
** Pageviews Analytics tool is feature complete (
http://tools.wmflabs.org/pageviews/), talking to communities about adding
links to it
** Deadlink logging API is finished, adding integration to Cyberbot

=== Reading ===
 Reading Infrastructure 
* *AuthManager is still coming!* (see three weeks ago for details)
** Behind schedule though, but we think we're about there on the core
patches.
* It looks like we're getting close on the load.php thing, too.

 Mobile Content Service 
* '''Updates''':
** Fixed issue with lead paragraph transformation
https://phabricator.wikimedia.org/T65874
** Starting rollout of Mobile Content Service to Android production app
this Thursday https://phabricator.wikimedia.org/T126934

 Android 
* 2.1.143 beta published. Expected to be promoted to production soon.

 iOS 
* '''Updates''':
** 5.0.1 was released today - all bug fix updates
** Hockey app is currently much happier - less crashes

* '''Upcoming''':
** Enabling handoff from Mac browser to iOS app and credentials sharing  by
updating a file on the server
** No time frame for next release (but expect it within 3 weeks) -
currently deciding whether to do another bug fix or do 5.1 with features

* '''Blocking''':
** Nothing

Web
=Done=
* Lazy loaded images rolling to beta mobile web
* Structured Language Overlay - trying to push it to 100% stable
* Language Switcher button - beta for now
* Lazy loading references

=Upcoming=
* Bug fixes and tweaks to the Language Overlay
* Ship the language switcher
* Semi-structured sprint

=== Editing ===
 Collaboration 
* '''Blocking''':
** External store work
* '''Blocked''':
* '''Updates''':
** Working on support for Flow notifications being properly hidden on
moderation
** Work on the Echo special page
** Changed MobileFrontend to reuse Echo code
** Working on Flow bug fixes

 Language 
* '''Blocking''':
** None
* '''Blocked''':
** New MT deployments blocked due to
https://gerrit.wikimedia.org/r/#/c/277463/ (WIP)
* '''Updates''':
**  Work on ContentTranslation continue.

 Multimedia ===
* '''Blocking''':
** None
* '''Blocked''':
** None
* '''Updates''':
** UploadWizard fixes and performance stuff on the way, currently in the
works
** ImageTweaks is slow going, currently there's a patch in core that it
depends on, probably won't be moving as quickly as we thought

 Parsing ===
* '''Blocking''':
** None?
* '''Blocked''':
** None
* '''Updates''':
** Somewhat of a lull in activity last couple weeks (with vacation, time
off, 20% work)
** But, heads up for VE, CX, Flow, Reading teams about
https://phabricator.wikimedia.org/T78676 -- been filing dependent tasks for
various teams. Parsoid side of the work should mostly be ready for merge in
2-3 weeks. But, other dependent tasks need to be resolved, performance and
client blockers will be considered before enabling this in production.

 VisualEditor ===
* No update.

== Advancement ==
=== Fundraising Tech ===
* No blocking/blockers
* DonationInterface mw1.27 tests are failing on some i18n core change, but
they're no longer voting
* Raft of CiviCRM enhancements to make logging more robust and enable
reverting contact merges
* Testing new Latin American payment methods in previously unpestered
countries
* Pondering how to make payments use a more recent version of mediawiki
https://phabricator.wikimedia.org/T130658
* More DonationInterface refactoring



== Technology ==
=== Release Engineering ===
* '''Blocking''':
** ???
* '''Blocked''':
** None
* '''Updates''':
** Reminder: Code freeze & Dallas switchover week of April 18
** Trebuchet -> Scap migration! Get in touch if you need it
*** There is a super secret irc channel on freenode, cryptically named
#scap3
*** scap 3.1 should be deployed soon, now with moar git-fat support. This
will unblock some services switching from Trebuchet to scap.

=== Research ===
 Research and Data 
* '''Blocking''':
** none
* '''Blocked''':
** ORES blocked on MW core code review
*** https://etherpad.wikimedia.org/p/ores_extension_blockers
*** What is the normal workflow for getting code reviewed?
 typical turn-around time?
 documentation for engaging +2 people?
* '''Updates''':
** ORES downtime over the weekend
*** https://wikitech.wikimedia.org/wiki/Incident_documentation/20160319-Ores
*** tl;dr pip doesn't remove old versions when installing new wheels

=== Security ===
* '''Blocking''':
** ???
* '''Blocked''':
** ???
* '''Updates''':
** 2FA updates for wikitech today. 2FA available on SUL wikis to Staff next
week.

=== Services ===
* '''Blocking''':
** none
* '''Blocked''':
** Ops: change-prop deploy - 

Re: [Wikitech-l] Internship opening: product management at WMDE

[Keegan Peterzell]

On Thu, Mar 24, 2016 at 4:11 PM, Pine W  wrote:

> Forwarding info about an opportunity to intern in product management with
> Wikidata and the good people at Wikimedia Deutschland.
>
> Pine


Thanks for spreading the word, Pine!

I think it's worth drawing attention to the first bullet point in the role
description:

* [...] enrolled as a Bachelor or Master student at a German university or
college or qualified for working in Germany as an ERASMUS program student.

-- 
Keegan Peterzell
Community Liaison, Product
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Internship opening: product management at WMDE

[Pine W]

Forwarding info about an opportunity to intern in product management with
Wikidata and the good people at Wikimedia Deutschland.

Pine
-- Forwarded message --
From: "Lydia Pintscher" 
Date: Mar 24, 2016 07:24
Subject: [Wikidata] internship opening: product management at WMDE
To: "Discussion list for the Wikidata project." <
wikid...@lists.wikimedia.org>
Cc:

Hey folks :)

I am looking for someone to support me me with my product management work
at WMDE as an intern. If you'd love to work with me and the rest of the
team, love Wikidata and want to learn, this might be the thing for you.
More details are here:
https://wikimedia.de/wiki/Internship_Product_Management


Cheers
Lydia
-- 
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata

Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de

Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.

Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.

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

Re: [Wikitech-l] ArchCom RFC update

[Scott MacLeod]

Thanks for this helpful overview, Gabriel!

Scott

On Wed, Mar 23, 2016 at 3:15 PM, Gabriel Wicke  wrote:

> Hi,
>
> please have a look at this week's summary of new and ongoing RFC
> discussions. There are several new RFCs, and some existing ones are moving
> close to a decision. No RFCs were decided finally this week.
>
> Because of the parallel Hackathon, no IRC discussion is scheduled for next
> week.
>
> Gabriel
>
> New RFCs:
>
> T130663 WIP RFC: Reference API requirements and options
>  (Timo): API access and
> component  markup for references; focus on gathering use cases /
> requirements.
>
> T122942 RFC: Support language variants in the REST API
>  (Gabriel): Different options
> for supporting languange variant selection in the REST API. Needed for
> languages like Chinese.
>
> T122825 Service Ownership and Maintenance
>  (Gabriel): Ownership and
> minimum maintenance requirements for production services. Strongly driven
> by unclear ownership of OCG (PDF renderer).
>
> T39902 RFC: Implement rendering of redlinks (in a post-processor?)
>  (Gabriel): Solutions for
> highlighting links to non-existing pages in Parsoid HTML. Main question is
> preprocessing vs. separate metadata processed on client.
>
> T130528 RFC: PSR-6 Cache interface in Mediawiki core
>  (No shepherd): Exploring use
> of
> standard PHP cache interface.
>
> Today's IRC session:
>
> T124792 Service Locator for MediaWiki core
>  (Daniel): Introduce a service
> locator (aka DI container) to allow code in mediaWiki core to make use of
> the Dependency Injection (DI) and Service Locator (SL) patterns.
>
> The discussion showed general support. Several participants expressed a
> desire to write more code with it before making a final call. Concrete
> suggestions on areas would be welcome. Tentative working group forming,
> aiming to discuss at Jerusalem Hackathon.
>
> Under discussion:
>
> T129435 RFC: drop support for running without mbstring
>  (Gabriel): Very focused RFC by
> Max. Main question in discussion so far is whether polyfilling is worth it.
> Max reaching out to mediawiki-l.
>
> T108655 Standardise on how to access/register JavaScript interfaces
>  (Roan): No update since last
> week, I need to split this task but I haven’t had time to yet. Last week’s
> update:
>
> Considering to split out contentious part (file-based require, or something
> like it; to support embedding libraries), move forward on less
> controversial part (basic module-name-based require infrastructure)
>
> T18691 RFC: Section headings should have a clickable anchor
>  (Timo): Under discussion with
> Volker and  Frontend Standards Group. Volker and team to collect different
> benefits and concerns to determine whether this is generally a desirable
> feature. And to explore other conceptually different solutions to the
> underlying use case of “sharing a link to a section” (e.g. a better table
> of contents, or live address bar).
>
> T124504 Transition WikiDev '16 working areas into working groups
>  (RobLa): No concrete progress;
> MZMcBride advocates for organic growth.
>
> T128351 RfC: Notifications in core
>  (Brion): No movement last
> week.
> Needs clarification of interfaces & scope as follow-up from IRC meeting.
>
> T66214 Use content hash based image / thumb URLs & define an official thumb
> API  (Brion): Clarified
> requirements & priorities in last week's IRC discussion. Needs update to
> reflect discussion.
>
> T118517 [RFC] Use  for media
>  (Brion): Revisit soon.
>
> T88596 Improving extension management
>  (Daniel): Discussion is picking
> up again, patch for review.
>
> T113034 RFC: Overhaul Interwiki map, unify with Sites and WikiMap
>  (Daniel): Has been discussed
> before, needs somebody to actually take this on.
>
> T11 [RFC] Introduce notion of DOM scopes in wikitext
>  (Tim): Active related
> discussion and prototyping at Balanced templates
>  and Hygienic transclusions for
> WYSIWYG, incremental parsing & composition: Options and trade-offs
> .
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 

- Scott MacLeod - Founder & 

Re: [Wikitech-l] Tech Talk: New Readership Data: March 18th

[Tilman Bayer]

The slides are up here BTW:
https://commons.wikimedia.org/wiki/File:New_readership_data_(Wikimedia_Foundation_Tech_Talk).pdf
Thanks to all who attended, or gave input on the presentation beforehand!

On Mon, Mar 14, 2016 at 10:05 PM, Rachel Farrand  wrote:
> Please join for the following tech talk:
>
> *Tech Talk**:* New readership data: Some things we've been learning
> recently about how Wikipedia is read
> *Presenter:* Tilman Bayer
> *Date:* March 18th, 2016
> *Time: *18:00 UTC
> 
> Link to live YouTube stream 
> *IRC channel for questions/discussion:* #wikimedia-office
>
> *Summary: *This talk will highlight various recent insights and new sources
> of data on how readers read Wikipedia, going beyond the familiar pageview
> numbers (that tell us which topics are popular and how overall traffic is
> developing, but not e.g. which parts of articles are being read). While we
> are still only beginning to understand some of these aspects, we now know
> more than a year or two ago. The presentation is centered around data
> analysis done by the Reading team, but will also include findings by other
> WMF teams and by external researchers.
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Tilman Bayer
Senior Analyst
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] Review Service Locator / DI Container proposal (upcoming RFC discussion on March 23)

[Daniel Kinzler]

Thanks everyone for the discussion yesterday!

A quick summary can be found at
. I got the impression that
I'm on the right track with this.

So, please give feedback on , and
suggest code experiments to vet this proposal against.

thanks,
daniel

Am 23.03.2016 um 19:04 schrieb Daniel Kinzler:
> Quick reminder: this is coming up today on #wikimedia-office.
> See  for details.
> 
> 
> Am 18.03.2016 um 20:44 schrieb Daniel Kinzler:
>> Hi all!
>>
>> Over the last couple of months, I have worked on introducing a dependency
>> injection mechanism into MediaWiki core (don't fear, no auto-wiring). My
>> proposal is described in detail at 
>> 
>> (yea, TL;DR - just read the top and search the rest if you have a question).
>>
>> Before we discuss this again on IRC at the RFC meeting on Wednesday (March 
>> 23,
>> 2pm PST / 22:00 CEST due to daylight confusion), I would like to invite you 
>> to
>> review the proposal as well as the patches that are up on gerrit. In 
>> particular,
>> any feedback would be appreciated on:
>>
>> * Introduce top level service locator
>> .
>> * Allow reset of global services 
>> * WIP: Make storage layer services injectable.
>> 
>>
>> Perhaps also have a look at the documentation included in the change, in
>> particular the migration part:
>> 
>>
>> Before commenting on design choices on gerrit, please have a look at T124792 
>> and
>> see whether I have written something about the issue in question there. I 
>> would
>> like to focus conceptual discussion on the RFC ticket on phabricator, rather
>> than on gerrit. On gerrit, we can talk about the implementation.
>>
>>
>> I very much want this to move forward. Perhaps we can even get the first 
>> bits of
>> this merged at the hackathon. So, criticize away!
>>
>>
>> Thanks for your help!
>> -- daniel
>>
>>
>> PS: phabricator event page (still blank, we'll fix that soon):
>> 
>>
>> ___
>> Wikitech-l mailing list
>> Wikitech-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>
> 
> 
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> 


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

Re: [Wikitech-l] Google Summer of Code 2016 portal now accepting applications

[Tony Thomas]

Hello all,

This is a reminder that the *deadline *to apply for Google Summer of Code
2016 with Wikimedia Foundation falls in *< 24 hours* at Friday, *March 25*
at 19:00 UTC. Please make sure that you have your *pdf *copy of proposal in
the application system at g.co/gsoc well before, to avoid last minute
confusions.

Past the deadline, applicants can do *minor* edits to their proposal copy
in Phabricator, which should be limited to wording/style changes. All
proposals submitted in the application system should have its copy in
Phabricator as Life_of_a_successful_project#Submitting_your_proposal
,
and should have minimum *2 mentors *connected with it. Make sure you have a
link to your Phabricator task somewhere in the proposal, to make things
easy. We will be sending a separate notification to all proposals submitted
on the same, and get ready for more emails!

Project mentors and co-mentors are required to get connected with the
application system via *invites*, and you can add your name to the
description at https://phabricator.wikimedia.org/T128441 or comment, for
the same. We will be starting separate Conpherence for that, either-way.

Thanks,
Tony Thomas 
Home  | Blog  |
ThinkFOSS 


On Tue, Mar 15, 2016 at 10:18 AM, Tony Thomas <01tonytho...@gmail.com>
wrote:

> Hello all,
>
> Google announced the start of accepting proposals for GSoC 2016 few hours
> ago. Interested and eligible candidates should submit their proposals at
> http://g.co/gsoc before the deadline of Friday, March 25 at 19:00 UTC.
>
> Wikimedia evaluates your proposal Phabricator task, but it is required
> that you have a copy of the same in the GSoC portal too, to make sure it
> gets a slot ( if eligible ). By March 25th, every possible application
> should have *2 mentors* connected with it, and should have a proposal
> copy in Phabricator, as well as the GSoC portal. Please make sure you
> mention the phab task details in your proposal, for convenience. If you are
> planning to apply, you should be looking at
> Life_of_a_successful_project#Coming_up_with_a_proposal
> 
>
> As of today, we have *8* projects featured for this round ( strong idea +
> 2 mentors connected ), and *13* projects missing one among the two
> mentors. Interested in mentoring ? see
> https://phabricator.wikimedia.org/tag/possible-tech-projects/ and add
> yourself as one.
>
> The Outreachy round May - August 2016 is open, with a deadline of *March
> 22, 2016 *and eligible applicants are advised to apply for *both* GSoC
> and Outreachy, so that the project can still make it, in case we are
> missing a slot with a strong applicant.
>
> Thinking of motivating someone in your locality to take part in ? Find
> flyers and presentations here
> 
>  for
> GSoC 2016 round!
>
> Thanks,
> Tony Thomas 
> Home  | Blog  |
> ThinkFOSS 
>
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l