[Wikitech-l] Rob Lanphier appointed to the Architecture Committee

[Tim Starling]

At the previous meeting of the MediaWiki Architecture Committee (April
20), the members present approved the appointment of Rob Lanphier to
the committee.

Rob was the main instigator in the formation of the committee in 2014.
Lately he has been taking an active role, chairing the weekly meetings
and writing the meeting agenda. In recognition of the excellent work
he has been doing, and in the interests of transparency, we decided to
formalise his membership.

-- Tim Starling


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

[Wikitech-l] ArchCom RFC update #6

[Rob Lanphier]

Hi everyone,

Here is the RFC status update from last week's ArchCom meeting (E165).
This is pretty much what is posted on-wiki [1], where everything has
links.

Rob



 Today's IRC session 
** April 20 [[Phab:E66/31]]
*** T91162: RFC: Shadow namespaces

 Queue for future RfC office hours 
** April 27: [[Phab:E66/32]]
*** T122942: RFC: Support language variants in the REST API
** May 4: [[Phab:E66/33]]
*** T130528: RFC: PSR-6 Cache interface in Mediawiki core

 Under discussion 
:Daniel: [[Phab:T124752]]
::Let’s turn the “Changes Tags” refactoring proposed by
[https://gerrit.wikimedia.org/r/#/q/owner:cenarium.sysop%2540gmail.com+status:open,n,z
Cenarium] into an RFC and get it unstuck. Chain of patches starts at
https://gerrit.wikimedia.org/r/#/c/201905/64; The patch refers to
[[Phab:T91535]] but the topic is broader than that, and the ticket
doesn’t fully describe the proposed solution. Needs work.
: Tim: shepherding two for Parser. will pick another
: Roan: [[Phab:T108655]] still need to split it so discussion can take
place on part 2

 Other status 
The "RFC inbox" was empty, nothing "Entering Final Comment Period",
and we didn't discuss the "no activity" list

[1] 
https://www.mediawiki.org/wiki/Architecture_committee/2016-04-20#RFC_status_update

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

Re: [Wikitech-l] Docs, use of, and admin privileges for wikimedia github project?

[Gabriel Wicke]

On Mon, Apr 25, 2016 at 8:19 AM, Brion Vibber  wrote:
> More importantly,
> when folks have repos that they've been running on GitHub already and want
> to move into the wikimedia project (rather than switch to gerrit), what's
> the procedure? I'm an admin/owner so I can manually import people's repos
> but I'm not sure whether I'm supposed to... :)

The method we have been using is via 'transfer ownership' in the
original repo settings. I believe moving the repo to the wikimedia org
requires owner permissions, so for repos owned by non-owners this
might require two transfers: One to an owner, then from owner to the
org.

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

[Wikitech-l] Requiring composer 1.0.0 as minimum version for 1.27?

[Legoktm]

Hi,

Composer recently released their first stable version of 1.0.0, which
among other things mandates usage of secure connections and validates
certificates[1]. I'd like for 1.27 to require 1.0.0 as a minimum version
people must use when fetching installing MediaWiki dependencies (people
can always use mediawiki/vendor instead of composer though).

As a side-effect, this would let us get rid of some old back-compat code
that is currently triggering a deprecation notice on every composer
install command[2].

Thoughts?

[1] https://phabricator.wikimedia.org/T119272#2125086
[2] https://phabricator.wikimedia.org/T119590#2234183

-- Legoktm

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

Re: [Wikitech-l] Docs, use of, and admin privileges for wikimedia github project?

[Antoine Musso]

Le 25/04/2016 17:19, Brion Vibber a écrit :

> More importantly,
> when folks have repos that they've been running on GitHub already and want
> to move into the wikimedia project (rather than switch to gerrit), what's
> the procedure? I'm an admin/owner so I can manually import people's repos
> but I'm not sure whether I'm supposed to... :)

I don't think there is any.  If you are an admin for the 'wikimedia'
github organization, you could fork their repository under 'wikimedia/'
namespace.  That will leave some kind of audit trail and indicate the
original repository.

The Jenkins community does that when they incorporate a third party
plugin in their ecosystem. An example:

 https://github.com/jenkinsci/git-plugin/

Got forked from https://github.com/magnayn/Hudson-GIT-plugin

And can then be community managed.

-- 
Antoine "hashar" Musso


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

Re: [Wikitech-l] Docs, use of, and admin privileges for wikimedia github project?

[Antoine Musso]

Le 25/04/2016 17:34, Bryan Davis a écrit :
>> > We also have a lot of admins, which I wonder is necessary:
>> > https://github.com/orgs/wikimedia/people?utf8=✓&query=role%3Aowner+
>> > 
>> > Do we do any security review / removal of old accounts, or have a procedure
>> > for adding new admins?
> Not that I am aware of. Rights there tend to work a lot like getting
> elevated rights on mediawiki.org: the rights are handed out by
> existing admins when somebody asks for something that will be easily
> solved by giving them rights. I think there was some amount of cleanup
> done a few months ago that got admins to either add 2fa to their
> github account or be removed.

The private task is:
https://phabricator.wikimedia.org/T118946

I havent followed up on it though but it definitely prompted a lot of
admin to enable 2FA.

The up-to-date list is available if you get admin on Github:
https://github.com/orgs/wikimedia/people?query=role%3Aowner


-- 
Antoine "hashar" Musso


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

Re: [Wikitech-l] Docs, use of, and admin privileges for wikimedia github project?

[Antoine Musso]

Le 25/04/2016 19:01, Chad a écrit :
> Honestly, I'm not entirely convinced that "mirror everything" is all that
> useful. It mostly results in a ton of unused repos cluttering up lists.
> 
> Not opposed to mirroring, but I'm wondering if we can be more selective.

Hello,

https://github.com/wikimedia/ is surely a mess. If GitHub had a way to
flag a repo as being a mirror, they could be filtered out easily (maybe
one can fill a feature request to them).

Another approach would be to split mirrors to a different organization
such as 'wikimedia-mirror'.  Admins would solely be people dealing with
mirroriing.  That will nicely cleanup the 'wikimedia' org.

-- 
Antoine "hashar" Musso


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

Re: [Wikitech-l] Fwd: Weekly update

[Aaron Halfaker]

FYI: not the first update on the revscoring project.  See updates going
back years here:
https://meta.wikimedia.org/wiki/Research_talk:Revision_scoring_as_a_service

This is, however, the first email update and the first weekly update in a
while :)

On Mon, Apr 25, 2016 at 2:36 PM, Amir Ladsgroup  wrote:

> Hey, this is the first weekly update on Revision Scoring project. In case
> you are not subscribed to ai-l
>
> -- Forwarded message -
> From: Amir Ladsgroup 
> Date: Mon, Apr 25, 2016 at 7:02 PM
> Subject: Weekly update
> To: a...@lists.wikimedia.org 
>
>
> Hello, This is our first weekly update being posted in this mailing list
>
> New Developments
>
>- Now you can abandon tasks you don't want to review in Wikilabels
>(T105521)
>- We collect user-agents in ORES requests (T113754)
>- Precaching in ORES will be a daemon and more selective (T106638)
>
>
> Progress in supporting new languages
>
>- Russian reverted, damaging, and goodfaith models are built. They look
>good and will be deployed this week.
>- Hungarian reverted model is built, will be deployed this week.
>Campaign for goodfaith and damaging is loaded in Wikilabels.
>- Japanese reverted model are built, but there are still some issues to
>work out. (T133405)
>
>
> Active Labeling campaigns
>
>- Edit quality (damaging and good faith)
>- Wikipedias: Arabic, Azerbaijani, Dutch, German, French, Hebrew,
>   Hungarian, Indonesian, Italian, Japanese, Norwegian, Persian (v2),
>   Polish, Spanish, Ukrainian, Urdu, Vietnamese
>   - Wikidata
>- Edit type
>- English Wikipedia
>
> Sincerely,
> The Revision Scoring team.
> <
> https://meta.wikimedia.org/wiki/Research:Revision_scoring_as_a_service#Team
> >
> ___
> 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] Docs, use of, and admin privileges for wikimedia github project?

[Gergo Tisza]

On Mon, Apr 25, 2016 at 7:33 PM, Bartosz Dziewoński 
wrote:

> I, for one, appreciate it. GitHub's interface is unfortunately a lot more
> convenient than any of the repository viewers we host ourselves. :(
> And fairly often I need to give somebody a link to a code snippet in one
> of our repos.


+1, it's very convenient for linking to code, or even just looking code up
for something that's not locally installed. Gitblit can take several
seconds per page view, and the Phabricator repo browser interface is one of
the sadder components of that software.

If we truly care about repo discoverability on github, using Github Pages
is probably a better option than trying to filter out unused ones (and
still ending up with an unmanageably large list).
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: Weekly update

[Amir Ladsgroup]

Hey, this is the first weekly update on Revision Scoring project. In case
you are not subscribed to ai-l

-- Forwarded message -
From: Amir Ladsgroup 
Date: Mon, Apr 25, 2016 at 7:02 PM
Subject: Weekly update
To: a...@lists.wikimedia.org 


Hello, This is our first weekly update being posted in this mailing list

New Developments

   - Now you can abandon tasks you don't want to review in Wikilabels
   (T105521)
   - We collect user-agents in ORES requests (T113754)
   - Precaching in ORES will be a daemon and more selective (T106638)


Progress in supporting new languages

   - Russian reverted, damaging, and goodfaith models are built. They look
   good and will be deployed this week.
   - Hungarian reverted model is built, will be deployed this week.
   Campaign for goodfaith and damaging is loaded in Wikilabels.
   - Japanese reverted model are built, but there are still some issues to
   work out. (T133405)


Active Labeling campaigns

   - Edit quality (damaging and good faith)
   - Wikipedias: Arabic, Azerbaijani, Dutch, German, French, Hebrew,
  Hungarian, Indonesian, Italian, Japanese, Norwegian, Persian (v2),
  Polish, Spanish, Ukrainian, Urdu, Vietnamese
  - Wikidata
   - Edit type
   - English Wikipedia

Sincerely,
The Revision Scoring team.

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

Re: [Wikitech-l] Docs, use of, and admin privileges for wikimedia github project?

[Bartosz Dziewoński]

On 2016-04-25 19:01, Chad wrote:

Honestly, I'm not entirely convinced that "mirror everything" is all that
useful. It mostly results in a ton of unused repos cluttering up lists.


I, for one, appreciate it. GitHub's interface is unfortunately a lot 
more convenient than any of the repository viewers we host ourselves. :(
And fairly often I need to give somebody a link to a code snippet in one 
of our repos.


--
Bartosz Dziewoński

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

Re: [Wikitech-l] Docs, use of, and admin privileges for wikimedia github project?

[Chad]

On Mon, Apr 25, 2016 at 8:20 AM Brion Vibber  wrote:

> There seems to be extremely little documentation on Wikimedia's GitHub
> project https://github.com/wikimedia ... I can only find
> https://www.mediawiki.org/wiki/Gerrit/GitHub which mostly says we mirror a
> bunch of stuff from gerrit. And I know we have continuous integration of
> some kind set up for some projects, but it doesn't seem to be well
> documented in a place I could find.
>
> There are also some repos that are mirrors of gerrit, and other repos that
> are primary repos, and it's a bit unclear what's what. More importantly,
> when folks have repos that they've been running on GitHub already and want
> to move into the wikimedia project (rather than switch to gerrit), what's
> the procedure? I'm an admin/owner so I can manually import people's repos
> but I'm not sure whether I'm supposed to... :)
>
>
Honestly, I'm not entirely convinced that "mirror everything" is all that
useful. It mostly results in a ton of unused repos cluttering up lists.

Not opposed to mirroring, but I'm wondering if we can be more selective.

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

Re: [Wikitech-l] Docs, use of, and admin privileges for wikimedia github project?

[Chad]

On Mon, Apr 25, 2016 at 9:30 AM Alex Monk  wrote:

> On 25 April 2016 at 17:01, Chris Steipp  wrote:
>
> > Correct, all admins should have two-factor setup. I believe everyone who
> is
> > an admin there has +2 in gerrit, and a reason to have the rights in
> Github.
> > I'd propose those 3 things as a minimal standard, since I don't think we
> > ever defined one
>
>
> I don't think everyone with admin there at the moment meets those criteria.
>
>
What Chris said. And what Alex said.

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

Re: [Wikitech-l] Docs, use of, and admin privileges for wikimedia github project?

[Alex Monk]

On 25 April 2016 at 17:01, Chris Steipp  wrote:

> Correct, all admins should have two-factor setup. I believe everyone who is
> an admin there has +2 in gerrit, and a reason to have the rights in Github.
> I'd propose those 3 things as a minimal standard, since I don't think we
> ever defined one


I don't think everyone with admin there at the moment meets those criteria.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Docs, use of, and admin privileges for wikimedia github project?

[Chris Steipp]

On Mon, Apr 25, 2016 at 8:34 AM, Bryan Davis  wrote:

> Not that I am aware of. Rights there tend to work a lot like getting
> elevated rights on mediawiki.org: the rights are handed out by
> existing admins when somebody asks for something that will be easily
> solved by giving them rights. I think there was some amount of cleanup
> done a few months ago that got admins to either add 2fa to their
> github account or be removed.
>

Correct, all admins should have two-factor setup. I believe everyone who is
an admin there has +2 in gerrit, and a reason to have the rights in Github.
I'd propose those 3 things as a minimal standard, since I don't think we
ever defined one.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Docs, use of, and admin privileges for wikimedia github project?

[Bryan Davis]

On Mon, Apr 25, 2016 at 9:19 AM, Brion Vibber  wrote:
> There seems to be extremely little documentation on Wikimedia's GitHub
> project https://github.com/wikimedia ... I can only find
> https://www.mediawiki.org/wiki/Gerrit/GitHub which mostly says we mirror a
> bunch of stuff from gerrit. And I know we have continuous integration of
> some kind set up for some projects, but it doesn't seem to be well
> documented in a place I could find.
>
> There are also some repos that are mirrors of gerrit, and other repos that
> are primary repos, and it's a bit unclear what's what. More importantly,
> when folks have repos that they've been running on GitHub already and want
> to move into the wikimedia project (rather than switch to gerrit), what's
> the procedure? I'm an admin/owner so I can manually import people's repos
> but I'm not sure whether I'm supposed to... :)

The really brief procedure Timo came up with during the Librarization
project is documented on wiki [0] but probably kind of buried in the
details about developing new libraries.

> We also have a lot of admins, which I wonder is necessary:
> https://github.com/orgs/wikimedia/people?utf8=✓&query=role%3Aowner+
> 
> Do we do any security review / removal of old accounts, or have a procedure
> for adding new admins?

Not that I am aware of. Rights there tend to work a lot like getting
elevated rights on mediawiki.org: the rights are handed out by
existing admins when somebody asks for something that will be easily
solved by giving them rights. I think there was some amount of cleanup
done a few months ago that got admins to either add 2fa to their
github account or be removed.


[0]: 
https://www.mediawiki.org/wiki/Manual:Developing_libraries#Transferring_an_existing_GitHub_repo_to_Wikimedia

Bryan
-- 
Bryan Davis  Wikimedia Foundation
[[m:User:BDavis_(WMF)]]  Sr Software EngineerBoise, ID USA
irc: bd808v:415.839.6885 x6855

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

[Wikitech-l] Docs, use of, and admin privileges for wikimedia github project?

[Brion Vibber]

There seems to be extremely little documentation on Wikimedia's GitHub
project https://github.com/wikimedia ... I can only find
https://www.mediawiki.org/wiki/Gerrit/GitHub which mostly says we mirror a
bunch of stuff from gerrit. And I know we have continuous integration of
some kind set up for some projects, but it doesn't seem to be well
documented in a place I could find.

There are also some repos that are mirrors of gerrit, and other repos that
are primary repos, and it's a bit unclear what's what. More importantly,
when folks have repos that they've been running on GitHub already and want
to move into the wikimedia project (rather than switch to gerrit), what's
the procedure? I'm an admin/owner so I can manually import people's repos
but I'm not sure whether I'm supposed to... :)

We also have a lot of admins, which I wonder is necessary:
https://github.com/orgs/wikimedia/people?utf8=✓&query=role%3Aowner+

Do we do any security review / removal of old accounts, or have a procedure
for adding new admins?

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

[Wikitech-l] Heads-up: "Write The Docs" conference in Sep 2016

[Andre Klapper]

For those interested + working on Wikimedia documentation:

There is a conf in Prague (Czech Rep) on Sep 18-20 "to explore the art
and science of documentation" for "writers, developers, support folks".

See http://www.writethedocs.org/conf/eu/2016 for more information.

There is https://meta.wikimedia.org/wiki/Grants which could be helpful
when it comes to supporting travelling.

I haven't attended the event myself but I've heard good stuff about it. :)

Cheers,
andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/



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

Re: [Wikitech-l] Hey guys how ı can leave this e-mail list?

[Muhammed Tatlısu]

Thanks Peachey.. I hope that would be a good week for all Wikipedia team.

Muhammed Tatlısu
34080/İstanbul-Türkiye
25 Nis 2016 15:07 tarihinde "K. Peachey"  yazdı:

> On 25 April 2016 at 22:01, Muhammed Tatlısu 
> wrote:
>
> > Muhammed Tatlısu
> > 34080/İstanbul-Türkiye
> >
>
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l#manage and follow
> the form details.
> ___
> 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] Hey guys how ı can leave this e-mail list?

[K. Peachey]

On 25 April 2016 at 22:01, Muhammed Tatlısu 
wrote:

> Muhammed Tatlısu
> 34080/İstanbul-Türkiye
>

https://lists.wikimedia.org/mailman/listinfo/wikitech-l#manage and follow
the form details.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Hey guys how ı can leave this e-mail list?

[Muhammed Tatlısu]

Muhammed Tatlısu
34080/İstanbul-Türkiye
25 Nis 2016 14:44 tarihinde "Andre Klapper"  yazdı:

> On Sat, 2016-04-23 at 13:44 +0530, Tony Thomas wrote:
> > The best approach would be to open up a Conpherence with your mentors
> > ( I hope they appreciate it ), and asking the same. If you do not find
> any
> > lucky with that, kindly ping or add in the org-admins too, and we will
> > get this resolved.
>
> For those wondering: "Conpherence" is the name of the discussion tool
> in Wikimedia Phabricator. It allows private conversations.
> See https://www.mediawiki.org/wiki/Phabricator/Help#Using_Conpherence
>
> Cheers,
> andre
> --
> Andre Klapper | Wikimedia Bugwrangler
> http://blogs.gnome.org/aklapper/
>
>
>
> ___
> 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 and Outreachy results out, Congrats interns

[Andre Klapper]

On Sat, 2016-04-23 at 13:44 +0530, Tony Thomas wrote:
> The best approach would be to open up a Conpherence with your mentors
> ( I hope they appreciate it ), and asking the same. If you do not find any
> lucky with that, kindly ping or add in the org-admins too, and we will
> get this resolved.

For those wondering: "Conpherence" is the name of the discussion tool
in Wikimedia Phabricator. It allows private conversations.
See https://www.mediawiki.org/wiki/Phabricator/Help#Using_Conpherence

Cheers,
andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/



___
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 and Outreachy results out, Congrats interns

[Quim Gil]

Congratulations to all the candidates selected -- and their mentors!

Also an encouragement to all the candidates that worked hard but could not
get an internship. Our statistics show that applicants going after a second
round have a very high success rate.

I also want to thank volunteer org admins Tony and Sumit, who (with just a
bit of support from Niharika and me) have run the GSoC and Outreachy
selection processes smoothly and on time. Tony, your announcement almost
reads like a Wikimedia Blog post (hint, hint).  :)

On Sat, Apr 23, 2016 at 9:56 AM, Aashaka Shah  wrote:

> I had also submitted a GSoC proposal for "Improving static analysis tools
> for MediaWiki", but
>

Aashaka, thank your for your understanding. Without knowing the details of
this decision, let me note that Priyanka (prnk28) was in a situation
similar to yours six months ago, when she was an Outreachy candidate but
saw her application declined. Yet she continued being involved, I guess she
learned a lot, and got more experience in our developer community, and now
that perseverance is paying off.

D3r1ck01 has a similar story, and... can it be that he is our first African
GSoC student? He joined this community half year ago, expressed his clear
interest in this GSoC round, and since then he has been involved as a
volunteer, also learning through practice and informal mentorship from
experienced developers.

To all the participants in this round: don't give up! Wikimedia is a
movement offering many possibilities to volunteer developers. I'm sure
there is a project or two where you can learn, meet interesting people, and
prepare for the next round.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] ResourceLoader, latency, & progressive enhancement

[Brion Vibber]

I also didn't really distinguish three separate perf points in my blurb:
* time to first paint
* time to bare page interactivity
* time to enhanced page display / interactivity

Mainly I was concentrating on the third point, but the first two -- which
y'all are already doing a great job on -- are even more important and
should not regress or we will be sad pandas. :)

/me gets on a plane, will comment more later

-- brion

On Monday, April 25, 2016, Brion Vibber  wrote:

> On Monday, April 25, 2016, Ori Livneh  > wrote:
>
>> Not so straight-forward. Khan Academy tried unbundling JavaScript on
>> HTTP/2
>> page views last November and found that performance got worse. They
>> attribute the regression primarily to the fact that bundling improves
>> compression. They concluded that "it is premature to give up on bundling
>> JavaScript files at this time, even for HTTP/2.0 clients."
>>
>> (http://engineering.khanacademy.org/posts/js-packaging-http2.htm)
>
>
> Nice, I'll go read that. :)
>
>
>
>> On most browsers, we take advantage of localStorage pretty heavily in
>> order
>> to have a durable cache of individual modules. Without it, slight
>> variations in the module requirements would occasion re-downloading a lot
>> of JavaScript, as the browser had no way of reusing JavaScript and CSS
>> delivered under a different URL. (Service Workers now provide more
>> sophisticated means of doing that, but global browser support is still
>> only
>> at 53%.
>>
>> We had to disable localStorage caching in Firefox because of the way it
>> manages quotas. Is your primary mobile browser Firefox for Android / iOS?
>
>
> Service workers are sounding more and more attractive here -- we could
> rewrite the requests as necessary to bundle when it makes sense etc, and
> avoid clogging up the synchronous, space-limited localStorage. Needs more
> research...
>
>
>> Lastly, we have good evidence that above-the-fold external CSS is a bigger
>> contributor to page latency than JavaScript. Gabriel documented that
>> pretty
>> well in T124966 . That CSS is
>> a
>> bigger issue than JavaScript is not surprising (top-loaded CSS is
>> render-blocking, whereas all of our JavaScript is loaded asynchronously),
>> but the magnitude of its impact is impressive.
>>
>> Krinkle is working on an arc of tasks that would get us there; T127328
>>  is the master task.
>
>
> Awesome, I'll read up and comment!
>
> -- brion
>
>
>> ___
>> 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] ResourceLoader, latency, & progressive enhancement

[Brion Vibber]

On Monday, April 25, 2016, Ori Livneh  wrote:

> Not so straight-forward. Khan Academy tried unbundling JavaScript on HTTP/2
> page views last November and found that performance got worse. They
> attribute the regression primarily to the fact that bundling improves
> compression. They concluded that "it is premature to give up on bundling
> JavaScript files at this time, even for HTTP/2.0 clients."
>
> (http://engineering.khanacademy.org/posts/js-packaging-http2.htm)


Nice, I'll go read that. :)



> On most browsers, we take advantage of localStorage pretty heavily in order
> to have a durable cache of individual modules. Without it, slight
> variations in the module requirements would occasion re-downloading a lot
> of JavaScript, as the browser had no way of reusing JavaScript and CSS
> delivered under a different URL. (Service Workers now provide more
> sophisticated means of doing that, but global browser support is still only
> at 53%.
>
> We had to disable localStorage caching in Firefox because of the way it
> manages quotas. Is your primary mobile browser Firefox for Android / iOS?


Service workers are sounding more and more attractive here -- we could
rewrite the requests as necessary to bundle when it makes sense etc, and
avoid clogging up the synchronous, space-limited localStorage. Needs more
research...


> Lastly, we have good evidence that above-the-fold external CSS is a bigger
> contributor to page latency than JavaScript. Gabriel documented that pretty
> well in T124966 . That CSS is a
> bigger issue than JavaScript is not surprising (top-loaded CSS is
> render-blocking, whereas all of our JavaScript is loaded asynchronously),
> but the magnitude of its impact is impressive.
>
> Krinkle is working on an arc of tasks that would get us there; T127328
>  is the master task.


Awesome, I'll read up and comment!

-- brion


> ___
> 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