Hi all - just wanted to let you know about
https://phabricator.wikimedia.org/tag/reading-admin/ if you didn't know
about it already. This is a place the Reading management team adds and
tracks more manager oriented tasks.
As items get moved to Done, we will in the future probably actually want to
check into whether they should be moved farther left in the board to be
repeated / re-reviewed or figure out some appropriate lightweight workflow
for such things.
-Adam
Hi all -
I've been reviewing a list of extensions with Reading Engineering and
Reading Infrastructure leads - props to James Forrester for promoting this
discussion. Here's a list of extensions we believe currently falls under
Reading for triage (n.b., not all extensions will get active development
support).
https://www.mediawiki.org/wiki/User:ABaso_(WMF)/Extension_Responsibility
Presuming no major issues with this, I think we should move the page to
mw:Reading/Extension_Responsibility.
One important outstanding question:
Is MultimediaViewer appropriate for Reading given its consumption-oriented
nature? Or is this actually better suited to Editing (where there exists a
team named Multimedia)?
Some other notes:
* For skins with low utilization, we in time probably should coordinate
handover to interested community members (or discuss with community members
practical approaches for EOL).
* Regarding the Nostalgia skin, we believe it's only used on
https://nostalgia.wikipedia.org/wiki/HomePage, so maintenance would be
updating for breaking skin changes or security issues only.
* JsonConfig, ZeroBanner, ZeroPortal - we'll need to examine this more
closely. Yuri (who has deepest PHP knowledge on extensions) is now over in
Discovery, Jeff (JS & Lua) is in Reading, and now I'm managing instead of
writing lots of code.
* Collection probably belongs in Services
Just an FYI, a recent change in the selenium gem is causing the bot
Barry to report false positives for MobileFrontend patches. If you see
a -1 from him on your MobileFrontend patch, please read the log in the
mean time - if only 2 tests are failing it's highly likely your patch
is fine.
+2ers please consult the log prior to merging and overriding Barry's
-1 whilst the upstream bug [1] remains unfixed.
QAers the problem seems to be related to a recent change to the
selenium gem that requires a new user for new page creations. Would be
great to fix this...
[1] https://phabricator.wikimedia.org/T106343#1465574
The Reading Web team kicked off Sprint 52 today [1].
Work undertaken in this sprint will include rounding out the efforts that
were started in the previous sprint to increase test coverage and a create
a staging environment for testing and review, and diving in to performance
goals with an audit of the mobile site [2], which will inform
highest-priority performance improvements going forward.
Also, we have reached the end of the alphabet for our movie sprint naming
scheme! New sprint naming ideas are welcome :-)
[1] https://phabricator.wikimedia.org/tag/reading-web-sprint-52-zoolander/
[2] https://phabricator.wikimedia.org/T105365
There's a ticket for removing mobile.wikipedia.org and wap.wikipedia.org
domains/subdomains, which are legacy domain names superseded by
m.wikipedia.org and its subdomains.
https://phabricator.wikimedia.org/T104942
The rationale for the removal of these legacy domain names is to help
support HSTS preloading in browsers with the existing TLS SAN cert.
After review of the ticket, can anyone think of a compelling reason to keep
those old domain names?
I opened a separate thread about this on wikitech-l under a different
subject about this as well.
-Adam
Hi everyone,
We've released a new version of the production Wikipedia Android app
[1][2], which is currently rolling out to all Play Store users today. This
is mostly a maintenance release, with a few welcome visual enhancements.
Here's an abridged list of the updates in this release:
* Enlarged images when browsing articles
* Improved "read more" suggestions at the bottom of articles
* Enabled "Search Wikipedia" when sharing text from other apps
* Added system language support & Chinese dialects to Wikipedia language
picker
* Improved appearance and consistency of article lists (History, Saved
Pages, etc.)
* Improved text alignment for mixed left-to-right and right-to-left
languages
* Improved page caching
* Added link to app FAQ in the "More" menu
* Various miscellaneous fixes and enhancements [3]
Stay tuned for future updates! We have some big things in store for our
next release. You won't want to miss it!
Best,
Dmitry Brant
Mobile apps team (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_Apps/Team
[1] https://play.google.com/store/apps/details?id=org.wikipedia&hl=en
[2]
https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.…
[3] https://phabricator.wikimedia.org/T103788
This might be interesting to some folks:
https://github.com/cscott/npm-travis
It works, I've tested it locally, I just got sidetracked when I was trying
to install a local jenkins slave or something so I could test it in labs.
If someone wants to adopt this, I'd love to see it find a loving home.
--scott
--
(http://cscott.net)