Re: [Wikitech-l] 2018-11-28 Scrum of Scrums meeting notes
Hi, I would like to request that, even if a team doesn't have a representative at a scrum of scrums meeting, the team submit a written status report that can be included in the SOS notes. I read these SOS notes to try to keep up to date with the many technical and product developments in the enormous Wikiverse, and it is helpful to me to read high level summaries from each team in the SOS notes. Thanks, -- Pine ( https://meta.wikimedia.org/wiki/User:Pine ) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] 2018-11-28 Scrum of Scrums meeting notes
https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-11-28 *=2018-11-28=* == Callouts == * Fundraising campaigns https://meta.wikimedia.org/wiki/CentralNotice/Calendar * Please avoid significant updates to any systems used by Fundraising (Geolocation, core facilities used by CentralNotice). Pls. ping on #wikimedia-fundraising by saying 'fr-tech' if you have quesitons. Thanks!!! * Release Engineering ** Train Health: *** Last week: No train due to the Thanksgiving Holiday *** This week: 1.33.0-wmf.6 deployment blockers https://phabricator.wikimedia.org/T206660 Wikidata rolled back to 1.33.0-wmf.4, all other group1 and all group0 on 1.33.0-wmf.6 see https://tools.wmflabs.org/versions/ T210608 (EventBus, Analytics) EventBus::createEvent Call to a member function format() on a non-object (boolean) T210610 (ORES - Ladsgroup) PHP Fatal Error: Argument 2 passed to ORES\Hooks\ApiHooksHandler::addScoresForAPI() must be an instance of array, null given T210617 (Wikidata, Maps - hoo)BadMethodCallException on Wikidata item pages containing coordinates with non-Earth globes T210618 (Wikidata, CirrusSearch) Wikidata entity search sometimes case-sensitive, uses wb_terms instead of CirrusSearch *** Next week: No train due to the Release Engineering team offsite == Audiences == === Contributors === Community Tech * Blocked by: * Blocking: * Updates: ** Anti-Harassment Tools * Blocked by: * Blocking: * Updates: ** Editing * Blocked by: **Working with Reading/Web to discuss loading overlay improvements * Blocking: **Language - working with them to prioritize adding inspector functionality to VE read mode ** Updates: ** Improved unit testing of ve.ce T206138 Growth * Blocked by: * Blocking: * Updates: ** Language * Blocked by: * Blocking: * Updates: ** === Readers === iOS native app * Blocked by: * Blocking: * Updates: **6.1.2 released last week (crash fixes) **Working on 6.2 ( https://phabricator.wikimedia.org/tag/ios-app-v6.2-beluga-on-a-pogo-stick/) - large release that contains editing (syntax highlighting, editing tools). Planning to release to beta before holiday break Android native app * Blocked by: * Blocking: * Updates: ** Readers Web * Blocked by: * Blocking: * Updates: ** Summary: SEO A/B test staged rollout is complete, we're continuing the MobileFrontend architecture project, and planning for advanced mobile contributions. ** Mobile website (MinervaNeue / MobileFrontend): *** Invest in the MobileFrontend & MinervaNeue frontend architecture https://www.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFrontend_%26_MinervaNeue_frontend_architecture Reduce View inheritance and improve composition support T209007 T209647 Replace mobile.startup/user with mw.user T204866 Webpackify references T207805 Webpackify watchstar T208921 *** Page issues https://www.mediawiki.org/wiki/Reading/Web/Projects/Mobile_Page_Issues Standardize parsing T206177 Distinct issues should not be grouped T202349 *** Advanced mobile contributions https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions Design added a few more pages to the prototype and some mocks for enable / disabling https://mobile-contributions.firebaseapp.com/nav4.html https://wikimedia.invisionapp.com/share/RNO2HHBPK7M#/screens/331909359_Enabling-Disabling Started team planning *** Maintenance and bug fixes T86210 T205008 T208808 T210191 T193505 ** Desktop website (Popups) https://www.mediawiki.org/wiki/Page_Previews *** Reproduce Popups memory leak T208634 ** PDF rendering (Proton) https://www.mediawiki.org/wiki/Reading/Web/PDF_Functionality *** Remaining work tracked in deploy Proton T181084 Readers Infrastructure * Blocked by: * Blocking: * Updates: ** English Wiki fundraising on apps starting Nov 29 (T209801). Multimedia * Updates ** SDoC - still working on beta release, have made progress but not there yet ** Also work continues on the next release (statements/depicts) Parsing * Blocked by: * Blocking: * Updates: UI Standardization * Blocked by: * Blocking: * Updates: ** Preparing v0.29.6 release of OOUI ** a11y measurments on portals finished == Technology == === Analytics === * Blocked by: * Blocking: * Updates: ** === Cloud Services === * Blocked by: * Blocking: * Updates: ** === Fundraising Tech === * Blocked by: - * Blocking: Please avoid significant updates to any systems used by Fundraising (Geolocation, core facilities used by CentralNotice). Thanks!!! * Updates: ** Year-end fundraising campaigns in English-speaking countries started yesterday (2018-11-27). E-mail campaign ongoing. ** Currently facing payment processor issues and sophisticated credit-card fraud attempts. Donations are pouring in, nonetheless. ** Various minor improvements to CiviCRM (donor database), payment processors. ** Follow-ups from CentralNotice
[Wikitech-l] Wikimedia production excellence (October 2018)
Read this post on Phabricator at https://phabricator.wikimedia.org/phame/live/1/post/125/ --- How’d we do in our strive for operational excellence last month? Read on to find out! - Month in numbers. - Highlighted stories. - Current problems. ## Month in numbers * 7 documented incident since from 24 September to 31 October. [1] * 79 Wikimedia-prod-error tasks closed from 24 September to 31 October. [2] * 69 Wikimedia-prod-error tasks created from 24 September to 31 October. [3] * 175 currently open Wikimedia-prod-error tasks (as of 25 November 2018). October had a relatively high number of incidents – compared to prior months and compared to the same month last year. Details at [1]. Terminology: * An Exception (or fatal) causes user actions to be prevented. For example, a page would display "Exception: Unable to render page", instead the article content. * A Warning (or non-fatal, or error) can produce page views that are technically unaware of a problem, but may show corrupt, incorrect, or incomplete information. Examples – an article would display the code word “null” instead of the actual content, a user looking for Vegetables may be taken to an article about Vegetarians, a user may receive a notification that says “You have (null) new messages.” I’ve highlighted a few of last moth’s resolved tasks below. ## *️⃣ Send your thanks for talk contributions Fixed by volunteer @Mh-3110 (Mahuton). The Thanks functionality for MediaWiki (created in 2013) wasn’t working in some cases. This problem was first reported in April, with four more reports since then. Mahuton investigated together with @SBisson. They found that the issue was specific to talk pages with structured discussions. It turned out to be caused by an outdated array access key in SpecialThanks.php. Once adjusted, the functionality was restored to its former glory. The error existed for about eight months, since internal refactoring in March for T186920 changed the internal array. This was Mahuton’s first Gerrit contribution. Thank you @Mh-3110, and welcome! – https://phabricator.wikimedia.org/T191442 ## *️⃣ One space led to Fatal exception Fixed by volunteer @D3r1ck01 (Derick Alangi). Administrators use the Special:DeletedContributions page to search for edits that are hidden from public view. When an admin typed a space at the end of their search, the MediaWiki application would throw a fatal exception. The user would see a generic error page, suggesting that the website may be unavailable. Derick went in and updated the input handler to automatically correct these inputs for the user. – https://phabricator.wikimedia.org/T187619 ## *️⃣ Fatal exception from translation draft access Accessing the private link for ContentTranslation when logged-out isn’t meant to work. But, the code didn’t account for this fact. When users attempted to open such url when not logged in, the ContentTranslation code performed an invalid operation. This caused a fatal error from the MediaWiki application. The user would see a system error page without further details. This could happen when opening the link from your bookmarks before logging in, or after restarting the browser, or after clearing one’s cookies. Fixed by @santhosh (Santhosh Thottingal, WMF Language Engineering team). – https://phabricator.wikimedia.org/T205433 ## Thanks! Thank you to everyone who helped by reporting or investigating problems in Wikimedia production; and for devising, coding or reviewing the corrective measures. Including: Addshore, Aklapper, Anomie, ArielGlenn, Catrope, D3r1ck01, Daimona, Fomafix, Ladsgroup, Legoktm, MSantos, Mainframe98, Melos, Mh-3110, SBisson, Tgr, Umherirrender, Vort, aaron, aezell, cscott, dcausse, jcrespo, kostajh, matmarex, mmodell, mobrovac, santhosh, thcipriani, and thiemowmde. ## Current problems Take a look at the workboard and look for tasks that might need your help. The workboard lists known issues, grouped by the week in which they were first observed. → https://phabricator.wikimedia.org/tag/wikimedia-production-error/ ProTip: Cross-reference one workboard with another via “Open Tasks” > “Advanced Filter” and enter Tag(s) to apply as a filter. Thanks! Until next time, – Timo Tijhof --- Further reading: * September 2018 edition. https://phabricator.wikimedia.org/phame/live/1/post/119/ Footnotes: [1] Incidents. – https://wikitech.wikimedia.org/wiki/Special:AllPages?from=Incident+documentation%2F20180924=Incident+documentation%2F20181101=0 [2] Tasks closed. – https://phabricator.wikimedia.org/maniphest/query/2FueDFF3G9zU/#R [3] Tasks opened. – https://phabricator.wikimedia.org/maniphest/query/Ifhw.G3VvBMJ/#R ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Commons app PG proposal, and v2.9 beta release
Hi folks, Hope you've all been well! :) We (the Commons app team) are applying for a Project Grant[1] to fund the development of v3.0 of the Commons Android app[2]. At the moment, we're approaching completion of our 2nd Individual Engagement Grant, having implemented several major new features, e.g. a revamped map of "nearby places that need photos" with direct uploads and Wikidata integration, user talk notifications, browsing of other Commons pictures with focus on featured images, and 2FA logins. We currently have 4000+ active installs, and 15,000+ distinct images uploaded via our app have been used in Wikimedia articles. In the last 6 months alone, 21,241 files were uploaded via our app, and only 1738 (8.2%) of those files required deletion. We are also proud to report that we have a vibrant, diverse community of volunteers on our GitHub repository[3], and that we have increased our global user coverage since our first grant. It has been a rocky road this year, however. One of the major issues we faced was that a large portion of our codebase is based on sparsely-documented legacy code from the very first incarnation of the app 5 years ago (a long time in the Android development world), leading to unpredictable behavior and bugs. We eventually found ourselves in a position where new features built on top of legacy code were causing other features to not work correctly, and even fixes to those problems sometimes had side effects that caused other problems. (My sincerest apologies to users for the inconveniences that they were caused!) In view of that, our Project Grant proposal focuses on these areas: - Increasing app stability and code quality: We plan to overhaul our legacy backend to adhere to modern best practices, reduce complexity and dependencies in our codebase, and introduce test-driven development for the first time. - Targeted acquisition of photos for places that need them: The "Nearby places that need photos" feature has come a long way, but there is still plenty of room for improvement. We plan to introduce new quality-of-life features (e.g. by implementing filters and bookmarks) and fix a few outstanding bugs to make it more user-friendly and convenient to use. We will also complete the final link in the chain of collecting photos for Wikipedia articles that lack them by prompting users to add their recently-uploaded photo to the relevant Wikipedia article. - Increasing user acquisition in the Global South: We plan to implement a "limited connectivity" mode, allow pausing and resuming of uploads, and put more time and effort into outreach and socializing the app, especially to underrepresented communities. - We also wish to continue to assist the Commons community to reduce vandalism and improve usability of images uploaded. This will be done by implementing selfie detection, and a "to-do" system that reminds users if an image lacks a description/categories. Your feedback is important to us! Please do take a look at our proposal[1], and feel free to let us know what you think on the Discussion page, and/or endorse the proposal if you see fit. If you would like to be part of the project, new volunteers and additions to our diverse team are always welcome - please visit our GitHub repository[3] and say "Hi". :) Also, we have just released v2.9 for beta testing on the Play Store! \o/ v2.9 features a new main screen UI, a new upload UI with multiple uploads enabled, and major bugfixes for image dates and the Nearby map default zoom level. More information and screenshots can be found on our blog[4]. If you would like to help test the new release, you can sign up for beta testing here[5]. Finally, we want to thank everyone who has cheered us on and supported us throughout the years. As a community-maintained app, we wouldn't be here without you. Best regards, Josephine (User:Misaochan), Commons app project maintainer [1] https://meta.wikimedia.org/wiki/Grants:Project/Commons_app/Commons_Android_app_v3 [2] https://play.google.com/store/apps/details?id=fr.free.nrw.commons [3] https://github.com/commons-app/apps-android-commons [4] https://cookiesandcodeblog.wordpress.com/2018/11/28/version-2-9-beta/ [5] https://play.google.com/apps/testing/fr.free.nrw.commons ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Advanced Search is now a default feature on all wikis
// Sorry for cross-posting Hi everyone, the Advanced Search interface is now available as a default feature on all wikis. That means you, logged-in or not, can carry out advanced searches even if you don’t know any search syntax. The new feature provides some existing advanced search options in a visual interface. This can help you find pages that contain a particular template, search in page titles, for a specific sequence of characters, and much more. Plus, the way namespaces can be selected has been redesigned. Among other things, you can now select several namespaces with one click, e.g. to search in all talk namespaces. More detailed information is on the project page. [1] The feature was developed by Wikimedia Deutschland’s Technical Wishes Team. [2] The idea for it was born in 2016 in workshops with editors, followed by prototypes, several feedback rounds on dewiki and Meta, and finally the beta function, which 43,000 people across all wikis used. During the beta phase, bugs were fixed, the namespace selection was revised, and more search options were added. Many thanks to everyone who took the time to give feedback (onwiki, in discussions, at the dev summit and more), to test or to translate. A big thank you also goes to the Discovery team at the WMF for their support, by making backend adjustments and implementing a new search parameter for deep category searches. The development team hopes that the new feature will help you find what you’re looking for more easily. People who prefer to keep the previous search interface can deactivate the new feature in their user preferences. [3] As always, feedback is welcome on the central talk page. [4] Johanna for the Technical Wishes team -- Johanna Strodt Project Manager Community Communications Technical Wishlist, Wikimedia Deutschland [1] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/AdvancedSearch [2] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes [3] https://meta.wikimedia.org/wiki/Special:Preferences#mw-prefsection-searchoptions [4] https://www.mediawiki.org/wiki/Help_talk:Extension:AdvancedSearch ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
