Mobile-l

mobile-l@lists.wikimedia.org

4 participants
6884 discussions

Re: [WikimediaMobile] [reading-wmf] Is Schema:MobileWebClickTracking dead?
by S Page 31 Jul '15

31 Jul '15

> Adam Baso <abaso(a)wikimedia.org> asked: > > Hi there - is Schema:MobileWebClickTracking dead? > Jon Robson <jrobson(a)wikimedia.org> replied: > Yes. > Then someone should have updated its talk page. https://meta.wikimedia.org/wiki/Schema_talk:MobileWebClickTracking See e.g. https://meta.wikimedia.org/wiki/Schema_talk:EchoPrefUpdate Back in 2013 the talk pages for schemas was where we kept track of their use. (Dario, is this still the case?) It's not ideal but the alternative is looking at the git logs of operations/mediawiki-config and the extension to figure out when things were disabled or decommissioned. I did it this time, but I think engineers should update the talk page when they stop using a schema, unless there's a better approach. > It got split into main-menu-daily, page-ui-daily and various other schemas. > I think you mean MobileWebMainMenuClickTracking and MobileWebUIClickTracking. I pasted baho's "break up MobileWebClickTracking" commit message into the talk page. FWIW https://meta.wikimedia.org/wiki/Special:PrefixIndex/Schema:MobileWeb lists 18 schemas, the EventLoggingRegisterSchemas hook[1] registers 9 schemas, and the active schemas category [2] only has four MobileWeb schemas. [1] https://phabricator.wikimedia.org/diffusion/EMFR/browse/master/includes/Mob… [2] https://meta.wikimedia.org/wiki/Category:Schemas_(active) -- =S Page WMF Tech writer

2 2

Re: [WikimediaMobile] [reading-wmf] Is Schema:MobileWebClickTracking dead?
by Adam Baso 30 Jul '15

30 Jul '15

Oops, should have sent this on mobile-l to start with. Thanks. Do you think we should remove that chart from the dashboard, or just prune stuff after 2015 and disable the job that keeps adding records to it? Kevin and Marcel from Analytics on the CC. -Adam On Thu, Jul 30, 2015 at 11:57 AM, Jon Robson <jrobson(a)wikimedia.org> wrote: > Yes. It got split into main-menu-daily, page-ui-daily and various other > schemas. > > On Thu, Jul 30, 2015 at 11:54 AM, Adam Baso <abaso(a)wikimedia.org> wrote: > > Hi there - is Schema:MobileWebClickTracking dead? > > > > On the ui-daily-historic chart in > > https://mobile-reportcard.wmflabs.org/#other-graphs-tab it looks like > stuff > > pretty much stops at the beginning of 2015. > > > > I'm going to ask Analytics to prune the long tail of events in 2015 to > make > > the graph prettier without the big drop off if no one objects. > > > > -Adam > > > > _______________________________________________ > > reading-wmf mailing list > > reading-wmf(a)lists.wikimedia.org > > https://lists.wikimedia.org/mailman/listinfo/reading-wmf > > > > _______________________________________________ > reading-wmf mailing list > reading-wmf(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/reading-wmf >

1 0

Wikipedia iOS 4.1.7 beta
by Brian Gerstle 30 Jul '15

30 Jul '15

Hi everyone! We're gearing up release another minor update the app. You can download it by opening the TestFlight app on your device and downloading the *Wikipedia Beta 4.1.7 (171)*. You'll see "What To Test" notes in TestFlight, but I've also copied them below for convenience. Please reply to me directly if you're not already a member of the beta testing group or have issues installing the app on your device. Thanks! Brian, Corey, & Monte - Make sure your favorite faces are nicely centered on the page's lead > image. Someone besides President Obama, we've checked him already ;-) > - Try to break the language picker! Both when changing languages of a > specific page (language "A" button on bottom toolbar) and changing the > search site (tap "W" > "More" > "Search ____ Wikipedia"). > - Try to break read more! Tap on the "Read More" suggestions at the bottom > of a page. > - Try to break saved pages! We had some issues where saving pages was > crashing the app. We're not sure which pages (or series of events before > the save) were causing the crash, so do your worst! -- EN Wikipedia user page: https://en.wikipedia.org/wiki/User:Brian.gerstle IRC: bgerstle

1 0

Measuring performance
by Jon Robson 30 Jul '15

30 Jul '15

The reading team are currently focusing energy on speeding up the site for all our users (https://phabricator.wikimedia.org/T98986 is the tracking bug where this work can be followed) Off the back of https://phabricator.wikimedia.org/T105361 I had a quick chat with Ori to document how the performance team is currently identifying problems with MediaWiki's code. I'm sharing here, so anyone who is interested in helping us improve the time our users can load our content can analyse our data, raise tasks, and submit patches. I'm hoping this will be useful for anyone who wants to get involved in an effort to make our site faster for our users (this is not desktop specific). If you have anything useful to add please do, after some discussion or nods I'd love to share some best practices on mediawiki.org Tool 1) Use http://webpagetest.org (no credentials necessary) * Use https://en.wikipedia.org/wiki/Facebook as an example wiki page * Choose a region of the world and browser * Select first view only since this is what we are currently interested in (repeat view is when they load again - and it should be quicker as it is from cache). * Capture video can be turned off - I personally find the screenshots more useful To shout out some of the advanced settings, the more interesting/useful features include: *Chrome > capture dev tools timeline * Setting speed 3G or 2G * Script can be used to conditionally turn on things which are not yet available to everyone e.g. VisualEditor You can do a lot of this in your Chrome browser locally, but different browsers may have different behaviours and are in a fixed location so this does not get captured in this tool. The visual screenshots also make it easier to see where things get blocked. With the timeline from advanced tools you can match up white screens with blocking scripts/styles Tool 2) Add http://performance.wikimedia.org to your browser bookmarks. Navigation timing section is probably the most interesting right now. It points to https://grafana.wikimedia.org (no credentials needed) which is powered by http://graphite.wikimedia.org (Access graphite with your wikitech credentials). This data is sourced from our users, so is a good representation of how we are doing. If a graph is missing you can create a new one from data in graphite by clicking "add row" or editing an existing graph. Clicking edit on https://grafana.wikimedia.org/#/dashboard/db/navigation-timing?panelId=12&f… you'll be able to understand where the data comes from on graphite e.g. metrics/frontend/navtiming/totalPageLoadTime Note for graphs median data is less sensitive to edge cases so best to use this as a more realistic indicator. Folders in graphite, are populated by scripts that live in: https://github.com/wikimedia/operations-puppet/tree/production/modules/webp… To create a graph, simply go to an existing workboard, save it under a different name (this clones it) - don't worry you can't mess up and delete existing workboards. Tool 3) Speedcurve requires you to setup an account but it gives you an opiniated view about things you care about and is nicely presented so could be a good source of inspiration for your own grafana dashboard. To oversimplify what it does: each day it will access a page, store result, allow you to see historic data. Note the performance team has plans to setup infrastructure to automate this. Tool 4) is one we are not using - http://sitespeed.io. We might want to use it for performance regressions test. In the grand scheme of things it would be great to get to a place where Jenkins complains if you cause a regression in firstPaint time but we are a long way from that but let's work in that direction :-) Let's live up to the Hawaiian word after which we are named! Apologies if this is oversimplified, please take this as an opportunity to share how you/your team/your company test page performance. I see this mailing list as a good place to share these sort of things!

2 1

[Apps] Android Wikipedia beta app release (2.0.104-beta-2015-06-25)
by Stephen Niedzielski 29 Jul '15

29 Jul '15

The Android team[0] is proud to announce a new Wikipedia Android app beta release, v2.0.104-beta-2015-06-25[1]. In summary, this revision contains the following enhancements: * New: Tabbed browsing! Press-and-hold links to open in a new tab. * New: Big images in articles! * New: Enable experimental read more enhancements for some users * Improve list design throughout the app * Add responsive UI to edit pencil * Fix certain ISBN number links * Reduce app memory requirements * Add image licensing to Share A Fact & link to app privacy policy * Remove initial login onboarding pop up * Dozens of fixes & improvements as listed[2]: https://phabricator.wikimedia.org/T103788 Make it better! Read our getting started guide[3]. We can't wait for your contributions! [0] https://www.mediawiki.org/wiki/Wikimedia_Apps/Team#Android_App [1] Rolling out at https://play.google.com/store/apps/details?id=org.wikipedia.beta [2] A complete list of changes is available at http://git.wikimedia.org/compare/apps%2Fandroid%2Fwikipedia/beta%2F2.0.103-… [3] https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_ha…

4 3

Wikipedia iOS app moving to GH
by Brian Gerstle 28 Jul '15

28 Jul '15

Hey everyone, I'm writing with plans for the Wikimedia iOS engineering team to move its workflow to GitHub with Travis CI, much like RESTbase. The Wikimedia iOS engineers have been maintaining their own CI and build server and using Gerrit for code review. The more time efficient and commonplace approach for open source iOS software development leans heavily on GitHub with Travis CI instead (e.g., WordPress[0][1] and Firefox[2][3]). By using GitHub with Travis CI, the team believes it will work faster, improve testing, grow developer confidence in making code changes, and, most importantly, deploy fewer bugs to production. For builds requiring sensitive information (e.g., prod certs), will continue to run on WMF's Mac Mini. As is done for Android, when betas are pushed, the team will notify mobile-l. Feel free to reply or email me directly with any questions or comments. Regards, Brian 0: https://github.com/wordpress-mobile/WordPress-iOS 1: https://travis-ci.org/wordpress-mobile/WordPress-iOS 2: https://github.com/mozilla/firefox-ios 3: https://travis-ci.org/mozilla/firefox-ios -- EN Wikipedia user page: https://en.wikipedia.org/wiki/User:Brian.gerstle IRC: bgerstle

2 4

Event Logging Field Aggregation versus Time-based Deletion
by Adam Baso 28 Jul '15

28 Jul '15

Hi there - we're reviewing with Analytics the Event Logging tables that have historically been part of the mobile presence. To reduce longer than necessary storage of information in some fields yet retaining information where it will be useful for future analyses, Marcel has noted a couple approaches. Would you please weigh in over the next couple days on which approach you prefer? Read: https://wikitech.wikimedia.org/wiki/Analytics/EventLogging_Sanitization_vs_… Then comment: https://wikitech.wikimedia.org/wiki/Talk:Analytics/EventLogging_Sanitizatio… Thanks! -Adam

1 0

Fwd: Wikimedia Foundation quarterly reviews for April-June 2015
by Tilman Bayer 27 Jul '15

27 Jul '15

Forwarding the link to the Reading team's quarterly review documentation, as it just occurred to me that not everyone might have caught it on the other lists. ---------- Forwarded message ---------- From: Tilman Bayer <tbayer(a)wikimedia.org> Date: Thu, Jul 16, 2015 at 7:50 AM Subject: Wikimedia Foundation quarterly reviews for April-June 2015 To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org> Cc: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> Hi all, the Wikimedia Foundation's quarterly reviews of teams' work in the past quarter (April-June 2015) took place last week. Minutes and slides for those meetings are now available: ... Reading (formerly mobile web and apps): https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter… ... As usual, much of this information will also be available in consolidated form as part of the general WMF quarterly report for Q4, which is planned to be published on July 30. -- Tilman Bayer Senior Analyst Wikimedia Foundation IRC (Freenode): HaeB -- Tilman Bayer Senior Analyst Wikimedia Foundation IRC (Freenode): HaeB

1 0

Cross-Post: Editing + Reading Meeting Notes
by Adam Baso 27 Jul '15

27 Jul '15

Cross posting to mobile-l. ---------- Forwarded message ---------- From: Adam Baso <abaso(a)wikimedia.org> Date: Mon, Jul 27, 2015 at 10:11 AM Subject: Editing + Reading Meeting Notes To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> Hi all, James Forrester, Florian, and I met Wednesday, 22-July-2015 to discuss the Editing roadmap, with the backdrop of editing modes available in mobile web and apps but both the mobile web and apps teams now being in the Reading department. Notes: * FY 2015-2016: active Editing development for apps not planned * General plan is to replace the current mobile web editing experiences with new (replacement) VE and wikitext editor maintained by the VE team for mobile web * Q1: VE mobile prototyping (doesn't require Reading involvement) * Q2: Editing for mobile web replacement *coding* starting, but rollout on mobile web would begin in some future quarter _after_ Q2 * Feature submission practices for volunteers submitting editing related stuff for the mobile web for the time being (feature submissions discouraged for now as it will end up being replaced; mainline VisualEditor / next gen wikitext editing in collaboration with VE team would probably make more sense) - ** Create task in reading-web Phabricator board and indicate the details of what you were thinking to work on and roughly when. Add James Forrester and Joaquin Hernandez to card. ** Reach out to James_F (Senior Product Manager, VisualEditor) and joakino (Reading Web engineering product owner and tech lead) on #wikimedia-mobile on Freenode to discuss the idea and to determine who would need to code review and test * Code review for bugfixes for the existing mobile editing code should be done by Reading Web, and code review plus testing should be done by Editing as well. Ping joakino and James_F on IRC to figure out who to add to bugfixes. * As the Editing team gets into the practice of submitting patches for MobileFrontend to swap out the editor, as usual, tasks should be filed well ahead of time in the reading-web Phabricator board so there's a heads up about potential code review. Also, Editing and Reading should be tracking Q2 and subsequent quarter planning together to ensure dependencies are clearly defined and agreed upon. I also spoke to Roan from Collaboration after the Scrum of Scrums the same day. Roan indicated that there isn't an emphasis on rolling out Flow to mobile Wikipedias en masse for FY 2015-2016. And generally, when Flow does become slated for rollout on the mobile Wikipedias and sister projects in a broader sense it shouldn't require work - or anything substantial, anyway - from the Reading team. -Adam

2 1

Re: [WikimediaMobile] In-app editing / talk pages support
by Adam Baso 26 Jul '15

26 Jul '15

Moving discussion to mobile-l. On Wednesday, July 22, 2015, Michael Holloway <mholloway(a)wikimedia.org> wrote: > OK by me. > > On Wed, Jul 22, 2015 at 10:53 AM, Adam Baso <abaso(a)wikimedia.org > <javascript:_e(%7B%7D,'cvml','abaso(a)wikimedia.org');>> wrote: > >> Okay to move this discussion to mobile-l? >> >> I'm talking with Editing (includes VE and Flow) this morning about >> engagement model and their short to medium term roadmap, which should be >> helpful in your guys' examination of bridge/stopgap solutions for this >> pretty fundamental stuff. >> >> >> On Wednesday, July 22, 2015, Michael Holloway <mholloway(a)wikimedia.org >> <javascript:_e(%7B%7D,'cvml','mholloway(a)wikimedia.org');>> wrote: >> >>> Hey all, >>> >>> Last week at Wikimania I had some interesting conversations about the >>> Android app. On the whole, people really like the new and improved app, >>> but there are definitely frustrations with the editing experience -- from >>> people thinking it's not possible to edit in the app, to uninstalling it so >>> that Google links direct them to the mobile website, where they vastly >>> prefer the editing experience. Editors are a small but important group and >>> I don't think we're doing them justice at the moment. Although reading is >>> our focus, I would suggest we devote some resources to improving the >>> editing experience as well. (It turns out that Abbey Ripstra and the >>> design research team are running a survey research study on mobile >>> contribution experiences as I write, so I'll be interested to hear what >>> insights they have to offer.) >>> >>> I also had a conversation with Asaf Bartov, who mentioned that it would >>> be nice to be able to access talk pages in the mobile app. I'm sympathetic >>> to this; most users may not care about talk pages, but they're very >>> important to the editing experience, and even for savvy readers they offer >>> useful commentary about what's on (or off) the page and why. So yesterday >>> afternoon I hacked up a POC patch to add a toolbar button to flip back and >>> forth between main articles and talk pages. Have a look and let me know >>> what you think! >>> >>> https://gerrit.wikimedia.org/r/#/c/226297/ >>> >>> Cheers, >>> Michael >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "android" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to android+unsubscribe(a)wikimedia.org. >>> To post to this group, send email to android(a)wikimedia.org. >>> To view this discussion on the web visit >>> https://groups.google.com/a/wikimedia.org/d/msgid/android/CAMEEL1-AxGuy%2BG… >>> <https://groups.google.com/a/wikimedia.org/d/msgid/android/CAMEEL1-AxGuy%2BG…> >>> . >>> >> >

13 19

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Mobile-l