sweet.

From my perspective, I want T114072 to happen because it helps with
presentation issues but I don't have the context to part of a discussion.
Real time editing seems more suited for the summit.

Hi Quim -- we'll take a look next week. It's very connected to the work on the mobile presentation that we're doing right now.

If people turn it on, then off, will we be able to count them?

Thanks Florian!

Hi Adam -- we should review this "soon" as it potentially impacts users who are trying to increase page performance by not downloading images but have the additional undesirable effect of disabling the cache.

T114542: Next Generation Content Loading and Routing, in Practice (+ T111588: RFC: API-driven web front-end, T106099: RFC: Page composition using service workers and server-side JS fall-back)
T114072: <section> tags for MediaWiki sections
T113210: How should Wikimedia software support non-Wikimedia deployments of its software?
T113540: What can the Search API do for you?

I have experienced this bug multiple times over the last few weeks. It
causes the article to be unreadable on my iphone. From my perspective this
is a high priority issue.

I think we can find a balance between a power user's IDE view of editing
with lots of tools versus and relatively simple editing experience for
newbies/anons. I'd like to think of the two experiences as 80/20 rather
than 100% either way.

Hi Moushira -- would love your feedback on this. Thanks!

I think so -- this is primarily is response to some discussions with
community folks who say that they actually will pull pages up in a mobile
to see how they render. It would be nice to have this be part of the tool.

We're pulling this into this sprint; there are a few minor UX issues to explore but we'd like to get this done now.

I agree with the SWAT deployment. Thanks for the quick response all.

Argh -- wrong parent.

Argh -- I'd like to move forward with the suggestions Adam captured in the
previous comment. I'll create a sub-ticket for the IRC channel and for
communicating this out.

I'm disappointed that it took this long, but it is done.

I wonder if we redacted the W0 numbers in 2.0. I seem to remember some
concerns about sharing those publicly.

[continued] so I would support keeping the status quo for now.

Thanks Krenair - qchris has my complete trust and support for any access he
feels is appropriate.

Congrats Dan and team -- nice to see this so close.

Anne's doing this as part of her work for the readership team and I approve.

I agree with bd808 -- we need to decide what data we need to support our
use cases and record just that, subject to normal privacy/ethical concerns
of course. We should take this approach across the board.

I talked to Bob West -- there are some other options we can investigate for
populating the lists.

We're going to post publicly -- ticket should not be closed until this
happens. Anne/Jon are point since they both worked on the analysis.

Thanks for the bump -- the task status (stalled) is definitely accurate.

approved

I support keeping things simple for this project and simply replacing the
source and definition of the page view logs as Dan proposes. Our
definitions will improve over time as will our ability to identify and
correct errors.

I spoke with Kevin on this -- he'll follow up with you, but yes, this is a
high priority task. If we can't finish by the requested date, we (you) need
to say when it will be done. We do have workarounds in the short term.

Hi all -- Terry has asked that this be finished by the next scorecard (10/19). We need to let him know the schedule -- do we have an ETA?

@JKatzWMF and I were talking about this today and I wanted to capture it. What if we acknowledged that there were actually two applications here -- an editor stack that needed to support 100,000 users and an consumption app that needed to support millions.

Thanks Erik -- that worked. I'll be taking the phab training next month :)

Hi Erik -- I can't seem to bring up the image in the attached task. It says
the image isn't viewable.

Nice work Baha! Let's run this by research as well, I'm sure there will be
feedback on seasonality, etc.

Thanks Gergo!

Hi Quim -- I'd like to second @Spage's proposal that we form a working group around Gabriel's proposals. The audience teams have been working to create some product requirements to accompany these proposals and it would be very constructive to report on these discussions at the summit.

Folks -- I'm going to respond to the wikitech thread; let's continue the discussion about the why's behind this project there. It's more accessible and it would be better to have a single discussion thread.

What do we do with mobile-l?

Approved (Volker's manager)

Hi Research -- it looks like this test will take place in late August/September. We'll reach out to meet on strategies.

Hi folks -- Tilman has a time sensitive request that he needs the pentaho data for. If we can't restart the interface, can we give him access to the underlying database?

Hi Daniel -- we'll use the Hadoop workflow system (Oozie) to run these
numbers regularly when we have the queries where we want them. Agree that
random cron jobs are undesirable.

This has been an enlightening thread in many ways! Thanks everybody.

Hi Adam -- can you please look at the UAs for the queries that come to
these domains? The question was asked on mobile-l and I think it would be
interesting (and hopefully straightforward) -- I think pulling the UA and
limiting to the top 10 would be enough.

If you insist...

Check out this document:

cool -- I'll defer to the expertise of Adam and Joaquin on this.

@Jhernandez, @dr0ptp4kt -- what's the level of effort for Reading here?

Hi folks -- please add any thoughts on the devices your team needs for the next fiscal. We're planning on reserving some portion of the budget for purchases later in the fiscal.

Thanks Dan -- it's R based which is unlikely to be our implementation
language. We'll check it out though.

Created https://phabricator.wikimedia.org/T105561 to make sure we sync up with Research on methodology.

Hi Adam -- Tilman will be reaching out for some help with this. We're primarily basing this on the numbers from the QR.

And here is a link to the MPL

Hi Rachel -- Katie's title is Director of Engineering, Fundraising. Can you please make sure it gets updated in the right places?

Adam/Jon/Wes -- I feel like this lines up with the SEO work that we've been doing. Should we try to connect these and make a larger project out them?