Mobile-l

mobile-l@lists.wikimedia.org

4 participants
6884 discussions

[ios] Apple Watch sales in trouble?
by Brian Gerstle 08 Jul '15

08 Jul '15

Down 90% since launch, according to this article citing "Slice" consumer research: http://www.marketwatch.com/story/apple-watch-may-not-be-ticking-with-custom… -- EN Wikipedia user page: https://en.wikipedia.org/wiki/User:Brian.gerstle IRC: bgerstle

1 0

Reading Web Sprint Kickoff: Sprint 51 YOLO
by Kristen Lans 08 Jul '15

08 Jul '15

(sending to mobile-l in addition to Reading internal list) The Reading Web team kicked off their first sprint of Q1 yesterday [1]. Work undertaken in this sprint will address an internal team goal [2] to "improve quality and development by improving development environment", including efforts to increase test coverage and create a robust testing and feature review environment. You can see the team's internal goals plus our one "official" quarterly goal [3] tracked in Phab here: [4]. [1] https://phabricator.wikimedia.org/tag/reading-web-sprint-51-yolo/ [2] https://www.mediawiki.org/wiki/Reading/Strategy_and_Roadmap [3] https://www.mediawiki.org/wiki/Wikimedia_Engineering/2015-16_Q1_Goals#Readi… [4] https://phabricator.wikimedia.org/tag/reading_web_planning/

1 0

Android app bug report template
by Bernd Sitzmann 07 Jul '15

07 Jul '15

https://phabricator.wikimedia.org/T104086 is a bug report template for Android issues. The easiest way to file a new bug is to go there and click on the link to file a pre-populated Phab ticket. Most of the time the "regular" one is what you need. If you fill out bugs coming from OTRS or crash reports then use the second one. You can also find this template in the last column of our Android workboard[1]. Cheers, Bernd [1] https://phabricator.wikimedia.org/tag/wikipedia-android-app/

5 7

Re: [WikimediaMobile] Mobile MediaViewer and the Seattle Japanese Garden
by Florian Schmidt 07 Jul '15

07 Jul '15

Hi, it's already possible in beta mode (open the left "hamburger" menu, click Settings and activate beta mode). We plan to move this very useful function to stable mode. There is a task and a change for it, see https://phabricator.wikimedia.org/T101718 I hope that's what you're looking for :) Best, Florian Sent from my HTC ----- Reply message ----- From: "Pine W" <wiki.pine(a)gmail.com> To: "mobile-l" <mobile-l(a)lists.wikimedia.org>, <Multimedia(a)lists.wikimedia.org> Subject: [WikimediaMobile] Mobile MediaViewer and the Seattle Japanese Garden Date: Mon, Jul 6, 2015 08:51 English Wikipedia's "Seattle Japanese Garden" article looks good in the Android app, and the MediaViewer-like slideshow feature works well for the gallery. However, I'm unable to scroll through the photos in Mobile Web like I csn using the Android app. Are there any plans to add the slideshow functionality to mobile web? Thanks! Pine

2 1

Video for Safari, IE, and Edge: ogv.js 0.9 and TMH patches (please review)
by Brion Vibber 07 Jul '15

07 Jul '15

I've done some more cleanup and fixes on ogv.js JavaScript Ogg media player, with an 0.9 pre-release build and updated patches for TimedMediaHandler. Would love some code review and testing! *Upstream library release:* https://github.com/brion/ogv.js/releases/tag/0.9 *Live demo site:* https://ogvjs-testing.wmflabs.org/ *TMH patches:* Update to bundled ogv.js libs (went ahead and merged): https://gerrit.wikimedia.org/r/#/c/223261/1 Finish the desktop TMH integration of ogv.js player (need testing and review!): https://gerrit.wikimedia.org/r/#/c/165478/36 Work in progress mobile integration for TMH (needs more upstream updates for controls): https://gerrit.wikimedia.org/r/#/c/217485/ -- brion

1 0

Mobile-Apps' "Unbreak now" tasks in Phabricator
by Andre Klapper 07 Jul '15

07 Jul '15

Hi, could the Apps Team please update their open tasks with "Unbreak Now!" priority [1] in Phabricator's "Mobile-App-Sprint-58-iOS" project? https://phabricator.wikimedia.org/maniphest/query/40ps.K.br_Ri/#R That Sprint ended one month ago and all remaining tasks are in the "Done" column. Thanks in advance, andre [1] "Something is broken and needs to be fixed immediately" as per https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_… -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

3 3

ICDIM 2015
by conference＠icdim.org 07 Jul '15

07 Jul '15

Tenth International Conference on Digital Information Management Jeju Island, South Korea October 21-23, 2015 (www.icdim.org) Technically co-sponsored by IEEE Technology Engineering Management Society Proceedings will be indexed in IEEE Xplore Following the successful earlier conferences at Bangalore (2006), Lyon (2007), London (2008), Michigan (2009) , Thunder Bay (2010), Melbourne (2011), Macau (2012), Islamabad (2013) and Thailand (2014) the tenth event is being organized at Jeju Island the Republic of Korea (South Korea) in 2015. The International Conference on Digital Information Management is a multidisciplinary conference on digital information management, science and technology. The principal aim of this conference is to bring people in academia, research laboratories and industry together, and offer a collaborative platform to address the emerging issues and solutions in digital information science and technology. The ICDIM intends to bridge the gap between different areas of digital information management, science and technology. This forum will address a large number of themes and issues. The conference will feature original research and industrial papers on the theory, design and implementation of digital information systems, as well as demonstrations, tutorials, workshops and industrial presentations. The 10th International Conference on Digital Information Management will be held on October 21-23, 2015 at the Jeju Island, Republic of Korea (South Korea). The topics in ICDIM 2015 include but are not confined to the following areas. Information Retrieval Data Grids, Data and Information Quality Big Data Management Temporal and Spatial Databases Data Warehouses and Data Mining Web Mining including Web Intelligence and Web 3.0 E-Learning, eCommerce, e-Business and e-Government Natural Language Processing XML and other extensible languages Web Metrics and its applications Enterprise Computing Semantic Web, Ontologies and Rules Human-Computer Interaction Artificial Intelligence and Decision Support Systems Knowledge Management Ubiquitous Systems Peer to Peer Data Management Interoperability Mobile Data Management Data Models for Production Systems and Services Data Exchange issues and Supply Chain Data Life Cycle in Products and Processes Case Studies on Data Management, Monitoring and Analysis Security and Access Control Information Content Security Mobile, Ad Hoc and Sensor Network Security Distributed information systems Information visualization Web services Quality of Service Issues Multimedia and Interactive Multimedia Image Analysis and Image Processing Video Search and Video Mining Cloud Computing Workshops ICDIM 2015 has the following co-located workshops Fourth Workshop on Emerging Problem- specific Crowdsourcing Technologies Fourth Workshop on Advanced Techniques on Data Analytics and Data Visualization Third IEEE International Workshop on Data Management (IWDM 2015) First Workshop on Internet of Things First Workshop on Big Data Mining First Workshop on Cluster Computing First Workshop on Intelligent Information Systems Proceedings - All the accepted papers will appear in the proceedings published by IEEE. - All papers will be fully indexed by IEEE Xplore. - All the ICDIM papers are indexed by DBLP. Modified version of the selected papers will appear in the special issues of the following peer reviewed journals. 1. Journal of Digital Information Management (SCOPUs/EI) 2. Journal of Electrical Systems 3. Recent Advances in Electrical & Electronic Engineering 4. International Journal of Web Applications (IJWA) 5. International Journal of Information Technology and Web Engineering (IJITWE) 6. International Journal of Emerging Sciences (IJES) 7. International Journal of Grid and High Performance Computing (IJGHPC) (Scopus and EI Indexed) 8. International Journal of Computational Science and Engineering (Scopus and EI Indexed) 9. International Journal of Big Data Intelligence 10. International Journal of Applied Decision Sciences (Scopus/EI) 11. International Journal of Management and Decision Making (Scopus/EI) 12 International Journal of Strategic Decision Sciences 13. International Journal of Enterprise Information Systems (Scopus/EI Important Dates Full Paper Submission August 10, 2015 Notification of Acceptance/Rejection September 10, 2015 Registration Due October 10, 2015 Camera Ready Due October 10, 2015 Workshops/Tutorials/Demos October 22, 2015 Main conference October 21-23, 2015 2015 Main conference October 15-17, 2015 SUBMISSIONS AT http://www.icdim.org/submission.html Committee General Chair Hanmin Jung, Korea Institute of Science and Technology Information, Korea Ezendu Ariwa, University of Bedfordshire, UK Program Chairs Xu Shuo, ISTIC, China Thomas Mandl, Hildesheim University, Germany Satoshi Tojo, JAIST, Japan Program Co-Chairs Michaela Geierhos, Paderborn University, Germany Ing-Xiang Chen, Ericsson, Tiwan Imran Bajwa Sajwa The Islamia University of Bahawlpur, Pakistan Organizing committee Sa-kwang Song, KISTI, Korea Do-Heon Jeong, KISTI, Korea Seungwoo Lee, KISTI, Korea Young-Guk Ha, Konkuk University, Korea In-Su Kang, Kyungsung Univ. Korea Email: conference at icdim.org SUBMISSIONS AT http://www.icdim.org/submission.html ----------------------------------

1 0

Barry the browser bot
by Jon Robson 07 Jul '15

07 Jul '15

Some of you may have noticed a bot [1] providing reviews for the Mobilefrontend and Gather extensions. This is a grass routes experiment [2] to see if we can reduce regressions by running browser tests against every single commit. It's very crude, and we're going to have to maintain it but we see this as a crude stop gap solution until we get gerrit-bot taking care of this for us. Obviously we want to do this for all extensions but we wanted to get something good enough that is not scaleable to start exploring this. So far it has caught various bugs for us and our browser test builds are starting to finally becoming consistently green, a few beta labs flakes aside [3]. Running tests on beta labs is still useful but now we can use it to identify tests caused by other extensions. We were finding too often our tests were failing due to us neglecting them. In case others are interested in how this is working and want to set one up themselves I've documented this here: https://www.mediawiki.org/wiki/Reading/Setting_up_a_browser_test_bot Please let me now if you have any questions and feel free to edit and improve this page. If you want to jump into the code that's doing this and know Python check out: https://github.com/jdlrobson/Barry-the-Browser-Test-Bot (Patches welcomed and apologies in advance for the code) [1] https://gerrit.wikimedia.org/r/#/q/reviewer:jdlrobson%252Bbarry%2540gmail.c… [2] https://phabricator.wikimedia.org/T100293 [3] https://integration.wikimedia.org/ci/view/Mobile/job/browsertests-MobileFro…

2 1

[Web] Outstanding branches
by Sam Smith 07 Jul '15

07 Jul '15

Hey y'all, There are a bunch of (stale?) branches open against MobileFrontend. Do we need to keep any of the following around? - esisupport - photouploads3 - sandbox/jdlrobson/ds - sandbox/jgonera/backbone - sandbox/jgonera/backbone-watchlist - sandbox/jgonera/edit - sandbox/jgonera/framework Ta, –Sam

3 3

[video club] RailsConf 2015 - Implementing a Strong Code Review Culture
by Sam Smith 07 Jul '15

07 Jul '15

Hey y'all, I watch a lot of talks in my downtime. I even post the ones I like to a Tumblr… sometimes [0]. I felt like sharing Derek Prior's "Implementing a Strong Code Review Culture" from RailsConf 2015 in particular because it's relevant to the conversations that the Reading Web team are having around process and quality. You can watch the talk on YouTube [1] and, if you're keen, you can read the paper that's referenced over at Microsoft Research [2]. I particularly like the challenge of providing two paragraphs of context in a commit message – to introduce the problem and your solution – and trying to overcome negativity bias in written communication* by offering compliments whenever possible and asking, not telling, while providing critical feedback. I hope you enjoy the talk as much as I did. –Sam [0] http://sometalks.tumblr.com/ [1] https://www.youtube.com/watch?v=PJjmw9TRB7s [2] http://research.microsoft.com/apps/pubs/default.aspx?id=180283 * The speaker said "research has shown" but I didn't see a citation *Notes (width added emphasis)* - Code review isn't for catching bugs - "Expectations, Outcomes, and Challenges of Modern Code Review" - Chief benefits of code review: - Knowledge transfer - Increased team awareness - Finding alternative solutions - Code review is "the discipline of explaining your code to your peers" - Process is more important than the result - Goes on to define code review as "the discipline of discussing your code with your peers" - If we get better at code review, then we'll get better at communicating technically as a team Rules of Engagement - As an author, provide context - "If content is king, then context is God" - *In a pull request (patch set) the code is the content and the commit message is the context* - Provide sufficient context - bring the reviewer up to speed with what you've been doing in the past X hours - *Challenge: provide at least two paragraphs of context in your commit message* - This additional context lives on in the commit history whereas links to issue trackers might not - As a reviewer, ask questions rather than making demands - Research has shown that there's a negativity bias in written communication. *Offer compliments whenever you can* - *When you need to provide critical feedback, ask, don't tell*, e.g. "extract a service to reduce some of this duplication" could be formulated as "what do you think about extracting a service to reduce some of this duplication?" - "Did you consider?", "can you clarify?" - "Why didn't you just..." is framed negatively and includes the word just - Use the Socratic method: asking and answering questions to stimulate critical thinking and to illuminate ideas Insist on high quality reviews, but agree to disagree - Conflict is good. *Conflict drives a higher standard of coding provided there's healthy debate* - Everyone has a minimum bar to entry for quality. Once that bar is met, then everything else is a trade-off - Reasonable people disagree all the time - Review what's important to you - SRP (Single Responsibility Principle) (the S from SOLID) - Naming - Complexity - Test Coverage - ... (whatever else you're comfortable in giving feedback on) - What about style? - Style is important - "People who received style comments on their code perceived that review negatively" - Adopt a styleguide Benefits of a Strong Code Review Culture - Better code - Better developers through constant knowledge transfer - Team ownership of code, which leads to fewer silos - Healthy debate

4 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Mobile-l