Mobile-l April 2014

mobile-l@lists.wikimedia.org

52 participants
78 discussions

Re: [WikimediaMobile] [Wikitech-l] jquery.accessKeyLabel broke mobile
by Jon Robson 30 Apr '14

30 Apr '14

1 0

Triaging bugs and moving stories to the backlog or sprint 30
by Tomasz Finc 30 Apr '14

30 Apr '14

Maryana, Can you take a pass through https://trello.com/b/8ADlEuVo/mobile-app-sprint-29-android-to-b (ToDo) and archive, move to sprint 30, or move to backlog as necessary? i'd like like to close sprint 29. thanks --tomasz

2 5

No more Mingle for the mobile web team
by Arthur Richards 29 Apr '14

29 Apr '14

I have completed the final steps for fully migrating from Mingle to Trello for the mobile web team: - I have finished reconciling the immediately important differences between Mingle/Trello for the mobile web team.* - I've enabled bugello to run automatically (it just picked up it's first real bug for the web team: https://trello.com/c/s0KRAIIC/32-bug-64575-ve-link-inspector-after-selectio… ). - I've made our project on Mingle read-only. So, please use Trello for all your project workflow/planning needs. Some useful links: - Current iteration (Vampire Squid) story wall: https://trello.com/b/NjJtUGAz/mobile-web-current-sprint-22-vampire-squid - Q4 Backlog: https://trello.com/b/sFlwoPUn/mobile-web-q4-backlog Trello is new for me and I am liking what I am seeing so far. Please be patient as we all adjust to the new tool. And finally, let me know if you have any issues/concerns/etc. * Bugello doesn't currently support some of the auto-reconciliation features that Bingle does - most notably, Bugello will not move a bug out of the bug backlog and stick it into 'ready for signoff' when the bug has been marked as resolved in BZ - therefore, our bug backlog on Trello is currently a little larger than on Mingle. -- Arthur Richards Software Engineer, Mobile [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687

1 0

Re: [WikimediaMobile] iOS animation library from FB/Paper: Pop
by Tomasz Finc 29 Apr '14

29 Apr '14

Nice, I bet Monte will have fun playing with this. --tomasz On Mon, Apr 28, 2014 at 2:09 PM, Erik Moeller <erik(a)wikimedia.org> wrote: > Just open sourced: > https://github.com/facebook/pop > http://techcrunch.com/2014/04/28/facebook-open-sources-the-animation-engine… > -- > Erik Möller > VP of Engineering and Product Development, Wikimedia Foundation

1 0

Re: [WikimediaMobile] Definition of Pageview for the API
by Adam Baso 29 Apr '14

29 Apr '14

Yuvi, Monte, Toby, ideas? -Adam On Mon, Apr 28, 2014 at 1:11 PM, Tomasz Finc <tfinc(a)wikimedia.org> wrote: > Adam, lets move this to a public list and engage Yuvi, Monte, and Toby > to answer your questions. > > --tomasz > > On Fri, Apr 25, 2014 at 4:55 PM, Adam Baso <abaso(a)wikimedia.org> wrote: > > The article loads for iOS and Android apps will no[w] both be in the web > logs. > > But I can't tell if the pageview counting code is still accurate; also, > > there are two action=mobileview hits per page load in the apps, so it > seems > > like it may be inaccurate from my read of it. > > > > How can Analytics be engaged to straighten out the relevant section of > code? > > I think the app release dates may have been pushed out a bit more, so it > may > > not be an emergency, but I wanted to check on next steps. > > > > Here's the relevant code from my understanding: > > > > > https://github.com/wikimedia/kraken/blob/master/kraken-generic/src/main/jav… > > > > I don't think action=view and action=query qualify as pageviews anymore > (at > > least without even further qualification), if they ever were. It's > possible > > the pageview counting code in the link above is only an intermediate > step in > > the qualification of hits, but until we dig into it, it's an unknown. > > > > I wonder if asking Analytics for action=view and action=query to be > removed, > > and then to disqualify 1 of the 2 URL types for the apps would make > sense. > > Or rather, asking them if it sounds okay and if we should then run it by > the > > engineering mailing list for further refinement. > > > > -Adam >

3 3

[Mobile web] Additional notes RE Bugello updates
by Arthur Richards 29 Apr '14

29 Apr '14

For the mobile web team, I will be migrating bugs that we currently have in our Mingle bug backlog into Trello on Monday before I get Bugello up and running. This will help prevent dupes and make it so backlogged bug cards are still available to us when we're planning, etc. Max, let's sync up sometime on Monday to discuss including PageImages and TextExtracts in the bugs that Bugello pulls in for us. Thanks! -- Arthur Richards Software Engineer, Mobile [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687

2 2

jquery.accessKeyLabel broke mobile
by Jon Robson 28 Apr '14

28 Apr '14

1 0

Bugello updates, rolling out next week
by Arthur Richards 26 Apr '14

26 Apr '14

To accommodate the mobile web team's migration from Mingle to Trello, I've made some enhancements to Bugello [1] to bring it more in line with the features we had added to Bingle. New features include: * Support for prefixing bug cards in Trello with [Bug $bug_num], which helps with... * Improved dupe detection * Adding bug descriptions to Trello card * Adding bug comments from BZ to new Trello cards * Posting a link back to BZ to the Trello card I also did some refactoring and made some minor bug fixes (including one that I know was plaguing the Flow team). I will be rolling this out for the mobile web team on Monday. Any other current users of Bugello should contact me if interested in updating to get these features - there are some config changes that you'll need to make and a couple of gotchas to look out for, and I'd be happy to walk you through it. Thanks and happy Friday! [1] http://github.com/wikimedia/bingle - note that Bugello is included with Bingle -- Arthur Richards Software Engineer, Mobile [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687

1 0

Copyvio test still failing
by Jon Robson 26 Apr '14

26 Apr '14

Juliusz's patch [1] doesn't seem to have fixed the Chrome builds [2]. Chris didn't like Juliusz's patch and submitted a new one [3] which doesn't work for me either. I think we should simplify this by 1) reverting Juliusz's change [4] 2) turning off the test for Chrome with my original patch [5] and then take a look at the bug [6] separately. Thoughts? [1] https://gerrit.wikimedia.org/r/129599 [2] https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs… [3] https://gerrit.wikimedia.org/r/129605 [5] https://gerrit.wikimedia.org/r/129732 [5] https://gerrit.wikimedia.org/r/#/c/129586/ [6] https://bugzilla.wikimedia.org/show_bug.cgi?id=64397

1 0

Gerrit email notifications are useless
by Max Semenik 24 Apr '14

24 Apr '14

Currently, we have ReviewerBot assigning every mobile team member as a reviewer to every MobileFrontend commit resulting in an endless spam in which everything useful is buried. I personally have a dashboard with MobileFrontend commits in it, so adding me to every commit serves nothing, hoever if someone wanted me to pay extra attention to a specific patchset, them adding me to it would have been useful - however it's presently impossible due to ReviewerBot. Also, current stream of useless emails makes noticing useful notifications about reviews much harder. I would rather preferred that ReviewerBot left me alone - does anyone else share this feeling? -- Best regards, Max Semenik ([[User:MaxSem]])

4 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Mobile-l April 2014