Mobile-l March 2014

mobile-l@lists.wikimedia.org

44 participants
79 discussions

by Ori Livneh

The newest release of Mobile Safari adds support for a new meta tag property, 'minimal-ui', which allows you to hide the browser chrome. It looks really great. I thought it might pair well with MultimediaViewer. http://darkblue.sdf.org/weblog/ios-7-dot-1-mobile-safari-minimal-ui.html --- Ori Livneh ori(a)wikimedia.org

10 years

Fwd: [Wikitech-l] Wednesday the 26th - styling in templates discussion

by Tomasz Finc

Wikimedia mobile teams - do make sure to attend and provide perspective about why this is so important mobile-l - come join to learn about some of the challenges we are facing and proposed solutions --tomasz ---------- Forwarded message ---------- From: Sumana Harihareswara <sumanah(a)wikimedia.org> Date: Mon, Mar 24, 2014 at 11:05 PM Subject: [Wikitech-l] Wednesday the 26th - styling in templates discussion To: Jon Robson <jdlrobson(a)gmail.com>, Jon Robson <jrobson(a)wikimedia.org>, Wikimedia developers <wikitech-l(a)lists.wikimedia.org>, Jared Zimmerman <jzimmerman(a)wikimedia.org> https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-03-26 This Wednesday the 26th, at 2100 UTC, in #wikimedia-office , we will be talking about Jon Robson's "Allow styling in templates" proposal: https://www.mediawiki.org/wiki/Requests_for_comment/Allow_styling_in_templa… Berlin: 10pm New York City: 5pm San Francisco: 2pm Sydney: 8am Thursday Please do come with comments and suggestions. We also have room to discuss an additional RfC on Wednesday, in case you have a favorite. -- Sumana Harihareswara Senior Technical Writer Wikimedia Foundation _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

10 years, 1 month

Fwd: [Wikitech-l] Three GSoC proposals about skins

by Arthur Richards

Any mobilistas interested in mentoring a project around Skins (nudge nudge, Jon). This also seems like a good opportunity to flex some mobile muscle on another one of our favourite (yes, that's right, British spelling to butter up Jon) topics. ---------- Forwarded message ---------- From: Quim Gil <qgil(a)wikimedia.org> Date: Sat, Mar 22, 2014 at 10:38 AM Subject: [Wikitech-l] Three GSoC proposals about skins To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> Let me draw your attention to three GSoC proposals trying to improve the current situation with MediaWiki skins. They didn't come from our list of featured projects,but they point to problems the community has acknowledged, and so far they are responding well to feedback. Your attention and help is welcome. Sorted by date: A modern, scalable and attractive skin for MediaWiki, by Jack Phoenix https://www.mediawiki.org/wiki/User:Jack_Phoenix/A_modern,_scalable_and_att… Isarra and Emufarmers are volunteering as mentors. All the basics seem to be in place, more scrutiny is welcomed. Separating skins from core MediaWiki, by Bartosz Dziewoński https://www.mediawiki.org/wiki/User:Matma_Rex/Separating_skins_from_core_Me… No mentors assigned yet, Jon Robson is volunteering. More than classical mentors, this proposal needs explicit community consensus, and a clear backing from MatmaRex's fellow Vector maintaners: Trevor Parscal, Roan Kattouw, Timo Tijhof. In fact, one of these (or someone else with +2 amb familiarity with skins) should be a co-mentor to offer a third pair of eyes to the plans and the code reviews. Frontend for Vector skin CSS customizations, by Ioannis Protonotarios https://www.mediawiki.org/wiki/User:Protnet/Frontend_for_Vector_skin_CSS_cu… No mentors assigned, and nobody is volunteering so far. The proposal is receiving good feedback from known experts in that area. While the previous two candidates are already maintainers in the areas they are proposing to work, and while Ioannis provides details about his experience, he needs mentors happy to evaluate him with microtasks and tough questions. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Arthur Richards Software Engineer, Mobile [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687

10 years, 1 month

VisualEditor is broken (again)

by Jon Robson

Tests for VE hidden in our browser tests show this is broken again. This prompts 2 things: 1) We are still not doing a good enough job of ensuring that VE keeps compatibility with mobile. James - is there anyway we can alert you better about these issues, maybe running our browser tests for VE alongside yours? 2) We ___really___ need to get our browser tests into better shape. This could have been catched sooner had Chris not managed to wade through the tests to actually assess the false positives. Let's try and get this fixed asap so broken code does not get on the deployment train... On the plus side, our tests are working (sometimes :-))

10 years, 1 month

Fwd: [Wikitech-l] Three GSoC projects about CAPTCHA improvements

by Arthur Richards

Any mobileistas interested in mentoring a project like this? This feels like a good opportunity to exert some mobile perspective/experience on a subject that everyone loves to hate: captchas. ---------- Forwarded message ---------- From: Quim Gil <qgil(a)wikimedia.org> Date: Sat, Mar 22, 2014 at 11:51 AM Subject: [Wikitech-l] Three GSoC projects about CAPTCHA improvements To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> We have discussed extensively the topic of CAPTCHA techniques for combating spam. The last round of discussions came after the fact that we featured a project related to captchas in our GSoC and OPW project ideas pages. See Bug 62960 - Prototype CAPTCHA optimized for multilingual and mobile https://bugzilla.wikimedia.org/show_bug.cgi?id=62960 I think we can make this a good GSoC project idea, basically by * acknowledging that we have a problem with our deployed captchas, and the investigation of alternatives is welcomed * limiting the scope to mobile + multilingual, two key areas where our current implementation is clearly lacking. * limiting the expectation on efficiency to anything better than the current implementation, not to a perfect system * limiting the expectation on deliveries to a prototype, not to a full solution to be deployed in five months from now Pau Giner and Emufarmers are willing to co-mentor, but they lack the experience required in programming. If the Language and Mobile teams are interested in this prototype, could they pull/pool the mentoring time required for this project? Is there anybody else willing to help? In my non-expert opinion, the fact that we are aiming to have a prototype reduces a bit the demand for code perfection. Still, programming experience is needed to evaluate properly our current candidates, and also to assess whether the plans drafted during the project are technically appropriate. The current proposals, sorted by date: https://www.mediawiki.org/wiki/User:AalekhN/GSoC_proposal_2014 by Aalekh Nigam https://www.mediawiki.org/wiki/CAPTCHA/Image_completion_captchas by Thanuditha Ruchiranga Wickramasinghe https://en.wikipedia.org/wiki/User:Shashank2016/Multilingual,_usable_and_ef… by Shashank Jaiswal Even if it is tempting to evaluate their CAPTCHA methods proposed first, in fact that doesn't matter as much as evaluating the skills, experience and collaboration style of the candidates themselves. This is why we need now your help, even as no-mentors, proposing technical tasks to the candidates, and helping evaluating them. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Arthur Richards Software Engineer, Mobile [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687

10 years, 1 month

Wikipedia Zero Automation Test Stuff Back Up

by Adam Baso

Okay, it's back up and running. -Adam On Tue, Mar 11, 2014 at 11:27 AM, Adam Baso <abaso(a)wikimedia.org> wrote: > Oops, copy-paste issue with Subject: line! Anyway, there you have it. > > > On Tue, Mar 11, 2014 at 11:21 AM, Adam Baso <abaso(a)wikimedia.org> wrote: > >> Heads up: the automation tests that take banner screenshots and examine >> links for proper interstitial format for Wikipedia Zero access are >> temporarily disabled in order to migrate servers from one data center to >> another. >> >> The core banner and interstitial warning functionality for W0 has been >> relatively stable, but wanted to give a heads up just in case. >> >> -Adam >> > >

10 years, 1 month

The last extension for ICCTIM2014 deadline!

by The International Conference on Computing Technology and Information Management (ICCTIM2014)

*************************************************************************** We apologize for multiples copies. Please circulate this CFP among your colleagues and students. *************************************************************************** [ICCTIM 2014] The International Conference on Computing Technology and Information Management April 9-11, 2014 Dubai, UAE http://sdiwc.net/conferences/2014/icctim2014/ **************************************************************************** Paper due: March 25, 2014 **************************************************************************** The proposed conference on the above theme will be held at Academic City Campus, Dubai, UAE, From April 9-11, 2014 which aims to enable researchers build connections between different digital applications. The conference welcomes papers on the following (but not limited to) research topics: * Computational Intelligence * Forensics, Recognition Technologies and Applications * Theories and methodologies of enterprise management * Computer Graphics and Simulations * Information and Data Management * Internet Modeling * Mobile Networking * E-Technologies, E-Business and E-Government * Multimedia Computing * Network Security * Peer-to-Peer Social Networks * Information Management * Project Management * Wireless Communications * Real-Time Systems * Engineering management and applications * Fuzzy and Neural Network Systems * Signal Processing, Pattern Recognition and Applications * Self-Organizing Networks and Networked Systems * Semantic Web, Ontologies * Sensor Networks and Social Sensing * Remote Sensing * Web Services Security * Business Intelligence and Web Services * Ethics in Technology Management * Web Services Architecture, Modeling and Design * Software Engineering **************************************************************************** All registered papers will be published in one of the following special issues provided that the author do major improvements and extension within the time frame that will be set by the conference and his/her paper is approved by the chief editor: * International Journal of New Computer Architectures and their Applications (IJNCAA) * International Journal of Digital Information and Wireless Communications (IJDIWC) * International Journal of Cyber-Security and Digital Forensics (IJCSDF) * International Journal of E-Entrepreneurship and Innovation (IJEEI) * International Journal of E-Services and Mobile Applications (IJESMA) * International Journal of Information Technology Project Management (IJITPM) * International Journal of Multimedia Data Engineering and Management (IJMDEM) * International Journal of Service Science, Management, Engineering, and Technology (IJSSMET) ****************************************************************************

10 years, 1 month

PHP CodeSniffer now Jenkins voting and auto message generation

by Jon Robson

Thanks to Siebrand, MobileFrontend code passes in PHP codesniffer. Jenkins will now refuse to accept code which doesn't meet PHP codesniffer coding standards. To test locally in the MobileFrontend repository you can run `make phplint` which will help you setup CodeSniffer with the correct configuration options and report errors. If you are using our pre-commit and pre-review hooks then any commit you make will also check for errors thus no excuses for bad PHP code from now on! Thanks again to Siebrand for cleaning up our code so it passes and make this possible. What a guy! :-) In other news we have some other cool Makefile magic. `make message` will provide a choose your own adventure type interface that means you never need to edit i18n files again! $ review/jdlrobson/bug/62553 x ~/Sites/w/extensions/MobileFrontend $ make message $ Choose a message key e.g. `mobile-frontend-xxx`: $ mobile-frontend-hello $ Creating new message with key `mobile-frontend-hello` $ What is the message in English?: $ Hello is it MobileFrontend you are looking for? $ What is the description for this message (qqq)? $ Message that appears when MobileFrontend feels like saying hello. $ Saving English message... $ Saving qqq message... $ Done! $ review/jdlrobson/bug/62553 x ~/Sites/w/extensions/MobileFrontend $ git diff diff --git a/i18n/en.json b/i18n/en.json index 28ff2d7..337a8c3 100644 --- a/i18n/en.json +++ b/i18n/en.json @@ -99,6 +99,7 @@ "mobile-frontend-generic-login-action": "Log in to contribute.", "mobile-frontend-generic-signup-action": "Sign up to contribute.", "mobile-frontend-geonotahack": "Near this page", + "mobile-frontend-hello": "Hello is it MobileFrontend you are looking for?", "mobile-frontend-history": "View edit history of this page.", "mobile-frontend-history-404-desc": "Cannot look at history for a page that doesn't exist. It may have been deleted or you may have followed a bad link.", "mobile-frontend-history-404-title": "No such page", diff --git a/i18n/qqq.json b/i18n/qqq.json index 0ff47c0..8d3dd9c 100644 --- a/i18n/qqq.json +++ b/i18n/qqq.json @@ -123,6 +123,7 @@ "mobile-frontend-generic-login-action": "Call to action that follows {{msg-mw|mobile-frontend-generic-login}} asking them to login.", "mobile-frontend-generic-signup-action": "Call to action that follows {{msg-mw|mobile-frontend-generic-login}} asking them to signup.", "mobile-frontend-geonotahack": "Label for button that shows pages near a given page.\n{{Identical|Near this page}}", + "mobile-frontend-hello": "Message that appears when MobileFrontend feels like saying hello.", "mobile-frontend-history": "Used as label for the link which points to the \"Edit history\" page.\n\nThis is shown on the Main Page in place of a last modified labe "mobile-frontend-history-404-desc": "Explain the reasons why the user may have arrived on {{msg-mw|mobile-frontend-history-404-title}}", "mobile-frontend-history-404-title": "Title of the 404 error page shown when navigate to [[Special:History/Title of page that does not exist]]", (END)

10 years, 1 month

Re: [WikimediaMobile] MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox - Build # 429 - Still Failing!

by Jon Robson

Moving to qa mailing list and mobile-l. These tests shouldn't be running on beta labs since the @custom-browser tag doesn't seem to work. It seems they got re-enabled (accidentally?) by Zeljko [2]. Zeljko are you looking into fixing the @custom-browser tag or was this a mistake? [1] https://gerrit.wikimedia.org/r/#/c/118559/3 On Tue, Mar 18, 2014 at 10:10 AM, Arthur Richards <arichards(a)wikimedia.org>wrote: > Anybody know what's going on here? These two tests have been failing for a > while now. > > > On Mon, Mar 17, 2014 at 9:13 PM, <jenkins-no-reply(a)cloudbees.com> wrote: > >> * FAILURE: >> MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox Build #429 >> <https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs…> >> (Tue, 18 Mar 2014 03:39:46 +0000)* >> *Test Result*<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs…> >> 2 failed, 1 skipped >> Failed Tests *Test Name**Duration**Age* Basic site for legacy >> devices.Able to access left navigation in basic non-JavaScript site<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs…> 8 >> sec9<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs…> Basic >> site for legacy devices.Able to search in basic non-JavaScript site<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs…> 6.4 >> sec9<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs…> All >> Tests *Package**Duration**Fail**Skip**Total* (root)<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs…>25 >> min2161 Wikitext Editor (TEST RUN ON WIKIPEDIA<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs…> 1 >> min 2 sec003 >> > > > > -- > Arthur Richards > Software Engineer, Mobile > [[User:Awjrichards]] > IRC: awjr > +1-415-839-6885 x6687 >

10 years, 1 month

Per-browser tags now in the build

by Chris McMahon

We wanted the no_javascript_site.feature test to run only for Firefox and not for Chrome. Zeljko and I today changed the builds and the tests such that a tag of @firefox will cause the test to run for FF and @chrome will run for Chrome, and both tags will run for both browsers. This is becoming a shared standard across all the builds for all the repos. -Chris

10 years, 1 month

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Mobile-l March 2014