https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-10-19
=2016-10-19=
== Product ==
=== Reading ===
==== Android native app ====
* Current sprint (
https://phabricator.wikimedia.org/tag/mobile-app-android-sprint-93-neptuniu…)
:
* Start on Q2 goals for Wikidata descriptions
* v2.4.160 released to production
* Workaround to handle unexpected JSON service responses gracefully
* CI screenshot regression testing
* Next sprint (https://phabricator.wikimedia.org/project/view/2319/):
* More Q2 goals for Wikidata descriptions
====Web====
* Current sprint: https://phabricator.wikimedia.org/project/view/2270/
- * Mainly tackling the tech debt
- * Also working on moving the first paragraph in the lead section above
the infobox
- * Finished the work on prototype solutions to avoid FOUC (flash of
unstyled content) on section collapsing:
https://phabricator.wikimedia.org/T147338. We've demoed all 4 solutions
to the team members. The next step is to decide on which solution we'll be
using.
* Next sprint: https://phabricator.wikimedia.org/project/view/2314/
- * Tech debt and hovercards instrumentation
-
==== iOS native app ====
Current Board (5.3 is in Beta):
https://phabricator.wikimedia.org/project/view/2220/
Since we last met:
- * Feed based off of MCS (Mobile Content Service) and persisting to
YapDatabase is complete & in beta
- * "In the news" Notifications are complete and awaiting beta
- * "In the news" in the explore feed is complete and awaiting beta
Before we meet again:
- * Adding alternate ToC (Table of Contents) style for UX research
- * Notifications settings
- * Bug fixes, crash fixes, converging to release of 5.3
No blockers
==== Mobile Content Service ====
Backlog: https://phabricator.wikimedia.org/tag/mobile-content-service/
Added more languages to 'In the news' feed portion.
https://gerrit.wikimedia.org/r/#/c/315451/
Going to remove Chinese from it though due to an issue with language
variant syntax and the inability to handle lang variantes in RB.
https://phabricator.wikimedia.org/T147874
==== Reading Infrastructure ====
* no blocking/blocked
* ORES data in action API soon: https://phabricator.wikimedia.org/T143895
* OAuth approval workflow changes soon:
https://phabricator.wikimedia.org/T103587#2621901
=== Community Tech ===
* Sprint board: https://phabricator.wikimedia.org/tag/community-tech-sprint/
* No blockers
* Not blocked
* Since last week:
* Did some more supporting work on Programs Dashboard
* Local (wiki) ID and Global ID now populate in CentralAuth localuser
table on new account attach
* Did some work with NewPagesPatrol on enwiki -
https://phabricator.wikimedia.org/T147225
* Work ongoing on maintenance script to backfill the columns for
existing accounts: https://phabricator.wikimedia.org/T142503
* Work ongoing to modify Copypatrol (the plagiarism detection tool) to
support more wikis https://phabricator.wikimedia.org/T145436
* Work ongoing on sending cookie with each block ticket -
https://phabricator.wikimedia.org/T5233
* Upcoming:
* Investigation for adding IP range support to Special:Contributions
https://phabricator.wikimedia.org/T147664
* Preliminary work/investigation on throttling number of accounts
created per browser: https://phabricator.wikimedia.org/T106930
=== Discovery ===
* No blockers
* Working on multiwiki indexes
* Deploying BM25 for top 10 languages soon (
https://phabricator.wikimedia.org/T147008#2694395), languages like ja, zh
and th still TODO
* Added accent squashing for Russian/Cyrillic analyzer
* Subphrase completion (completion inside phrase) enabled on mediawiki.org,
wikitech and wikisources
==== Maps ====
* Launched snapshot service Is there any docs, demo, something to show to
people ?
** Basic static service was described at
https://github.com/kartotherian/kartotherian#static-map-images
** The new "overlay addition" to the static service added three params to
specify which page and which map to draw over the image:
domain=www.mediawiki.org
title=Help:Extension:Kartographer
groups=_925bf4f20f98fdda374476b902f702d080492748
* Discussing tabular data on Commons
* If somebody has hive to Graphite setup, please talk to Yuri
=== Wikidata ===
* No blockers.
* Working on a new parser function in addition to {{#property:…}}, as well
as Lua support: https://phabricator.wikimedia.org/T142941
* Separate "Cognate" extension for automatic Wiktionary sitelinks pretty
much done, in security review: https://phabricator.wikimedia.org/T145412
* We are going to celebrate Wikidata's fourth birthday on October 29:
https://www.wikidata.org/wiki/Wikidata:Fourth_Birthday
=== Analytics ===
* Not blocking nor blocked
* Update:
* Recruiting fullstack dev: several tasks submitted and reviewed, some
candidates passed to next steps.
* Working on a KafkaSSE prototype (Kafka consumer to SSE) Kasocki's
analog for SSE.
* More work on removing Limn dashboards, only reportcard and
ee-dashboards remaining.
* Edit history reconstruction: good progress on productionization of
the jobs for all wikis.
* Troubleshooting varnish-kafka, causing false alarms in hadoop
webrequest loading jobs.
* Improved EventLogging monitoring and alarms.
=== Security ===
* Brian was out last week, but is back now
* Security Reviews:
* FileAnnotations (this week - done)
* Google MT for Content Translation (this week)
* Electron PDF-rendering service (next week)
=== Services ===
* Not blocking or blocked
* Updates
** SCB is expanded to 4 machines per DC
** Node.js security update to 4.6.0 is live on SCB and RESTBase
*** Please test and update your services that were not updated!
** Parsoid config deployment move to Scap3 ongoing
=== Technical Operations ===
* '''Blocked'''
** None
* '''Blocking'''
** Noone
* Updates
** SCB cluster capacity doubled today
** work ongoing on varnish 4 on text
** Jessie appserver reimaging ongoing, almost done
** API outage on Monday, root cause still unknown.
https://phabricator.wikimedia.org/T148652
=== ArchCom ===
* (RobLa can't be here; please follow links and comment)
* https://phabricator.wikimedia.org/E323 - today's ArchCom meeting
** *T145472: Survey Cookies/Local Storage usage on Wikimedia sites*
** https://phabricator.wikimedia.org/T145472
== Fundraising Tech ==
* Got some help from Aaron Schultz on CN bug, would welcome more review
from others familiar with MessageCache
** https://phabricator.wikimedia.org/T144952
* Brainstorming ways to monitor for recurrance of the issue
* General stabilization and log-quieting tasks
* Improving donor error messages
How to grow our technical community? This is a main topic at the upcoming
Wikimedia Developer Summit (San Francisco, January 11-13, 2017).
There is a call for participation open until the end of this month (October
31). Your proposals for discussions related to this main topic are welcome!
There are some ideas about possible topics at
https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/How_to_grow_…
If you are interested in contributing to the discussions about How to grow
our technical community, please join us at the Summit (the deadline to
request travel sponsorship is next Monday, October 24).
PLEASE ENCOURAGE OTHER PEOPLE to submit a proposal and/or join the Summit.
This email will likely arrive to the core of the Wikimedia technical
community, but the chances to arrive to the periphery and beyond are a lot
smaller. We need your help! We want to discuss how to grow our technical
community including the perspectives of those who haven't joined us yet.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hi,
I installed MW 1.23.15 on my laptop (running on a XAMPP).
I have
# InstantCommons allows wiki to use images from http://commons.wikimedia.org
$wgUseInstantCommons = true;
in LocalSettings.php.
Content of my template is:
[[Kép:Tick-green.png|20px]]<noinclude>[[Kategória:Sablonok]]</noinclude>
where Kép is a legitimate alias for File in Hungarian
I get a red 20px text and a tracking category for bad file instead of the
image from Commons.
The redlink goes to:
http://localhost/w/index.php?title=Speci%C3%A1lis:Felt%C3%B6lt%C3%A9s&wpDes…
(Special:Upload for those who can't fluently read urlencoded Hungarian)
Thanks sfor the help.
--
Bináris
Your help is welcome to provide feedback (CR±1/2) and guidance:
No *new* & unreviewed patches this week but:
== mediawiki/extensions/LdapAuthentication: ==
since 2016-09-27 (3rd time listed here; it's 2 lines):
Allow local user creation even if LDAP user creation is disabled
https://gerrit.wikimedia.org/r/#/c/313019/
== pywikibot/core: ==
since 2016-09-25 (3rd time listed here):
Checks the type of isbn and modifies accordingly
https://gerrit.wikimedia.org/r/#/c/312726/
Thanks in advance for your reviews.
Of last time's 3 listed patches, 1 got merged.
Thanks to Hashar, Jonas and Thiemo!
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
Google Code-in 2016 has been announced: A contest for 13-17 year old
students. While we wait for Wikimedia to get accepted:
Take those 10 minutes to find (or update) some Phabricator tasks in
your project(s) that would take an experienced contributor 2-3 hours.
* Do you have small, self-contained bugs you'd love to get fixed?
* Does your documentation need improvements?
* Does your user interface have small design issues?
* Does your Outreachy/Summer of Code project welcome small tweaks?
* Would you enjoy helping someone port your template to Lua?
* Does your gadget use some deprecated API calls?
* Do you have tasks in mind that welcome some research?
We have nearly 600 open "easy" tasks listed:
https://phabricator.wikimedia.org/maniphest/query/609oZQR8EpOH/#R
Are the tasks in your area clear enough and still valid?
And can you imagine helping a young person fix some of these tasks?
* Add the project "Google-Code-in-2016" and a comment in Phabricator
tasks that you would mentor those tasks.
* Tasks are welcome in five areas: Code; Outreach/Research;
Documentation/Training; Quality Assurance; User Interface.
* Add yourself to the table of mentors on the wikipage.
* Make sure the task description provides pointers to help the student.
* "Beginner tasks" (e.g. "Set up Vagrant"?) also very very welcome!
* "Generic" tasks also welcome (e.g. "Choose and fix 2 UI messages
from the task list in https://phabricator.wikimedia.org/T40638 ").
For complete info about Google Code-in, check
https://www.mediawiki.org/wiki/Google_Code-in_2016#Mentors.27_corner
Unsure about quality of contributions in GCI and effort? Please read
https://lists.wikimedia.org/pipermail/multimedia/2015-January/001009.html
Please ask if you have questions. Happy to help!
See you in Google Code-in!
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
Friends,
I'm helping review a tool <https://www.mediawiki.org/wiki/Extension:Ids>
that I understand Wikimedia Taiwan is eager to use, which uses a parser
hook to render ideographic description characters
<https://en.wikipedia.org/wiki/Ideographic_Description_Characters_(Unicode_b…>
into PNG glyphs in order to display historic or rare characters which
aren't covered by Unicode. It's very cool.
The challenges are first that it's based on a Tomcat backend
<https://github.com/Wikimedia-TW/han3_ji7_tsoo1_kian3_WM/blob/master/src/ids…>,
which I'm not sure is precedented in our current ecosystem, and second that
the code uses Chinese variable and function names, which should
unfortunately be Anglicized by convention, AIUI. Finally, there might be
security issues around the rendered text itself, if it were misused to mask
content.
I'm mostly asking this list for help with the question of using Tomcat in
production.
Thanks,
Adam
Hello everybody,
The Technical Collaboration team is very happy to introduce you to Srishti
Sethi <https://meta.wikimedia.org/wiki/User:SSethi_(WMF)>, our new
Developer Advocate. Srishti will lead our efforts to engage volunteer
developers in Wikimedia software projects and to grow the Wikimedia
technical community. In her first assignments, she will help promote
Community Wishlist projects, the Wikimedia Developer Summit, and
Wikimedia’s participation in Google Code-in. Srishti just relocated from
Boston to San Francisco, and she will work at the Wikimedia Foundation
office.
Srishti originally hails from Rajasthan, India. She recently finished her
Masters in Media Arts and Sciences from the MIT Media Lab, where she was
exploring how online platforms for learning could be made more peer-led,
engaging, participatory and accessible to diverse populations. At the Media
Lab, Srishti contributed to the design, development, and research of
Unhangout (http://unhangout.media.mit.edu), a platform for running
large-scale un-conference style events online.
Before joining MIT, she was working as a software developer with a startup
organization in India. As an undergrad, she was involved with the open
source community GNOME and its educational project GCompris.
In her spare time, Srishti likes to play ping-pong, do long bike trips,
take photographs and make masala chai for friends. :)
Please join us in welcoming Srishti!
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hi Shoichi,
On Mon, Oct 17, 2016 at 5:25 AM, 魔法設計師 <shoichi.chou(a)gmail.com> wrote:
> 1. Acutally speaking it can be launched as a self-server by lightweight
> Jetty (the server is Jetty embedded) it will be launched as a nomal java
> application. Why I use Tomcat now but not launched by "java -jar XXXX.jar"
> ,is because on tools.wmflabs.org , as I remembered,
>
> I had took the way :
> "webservice generic start /data/project/toolname/code/myserver.bash "
>
> Then, the port binding always faiedl,because the command "port" seemed
> always take away parameters belongs to
> the java ap owns.
>
> I couldn't resolve it,so I changed to Tomcat.
>
Great point--we can serve this using whatever Java web container is most
practical! Question for wikitech-l: Which would that be? It looks like
we're already running Jetty for Gerrit, is that the best choice for a new
service?
> 2.About Chinese variable and function names in the server code, after
> forking from the upstream , I think it can be translated to English (
> Actually speaking,I have get some works done.)
>
I'd be happy to help with some of that, maybe we can coordinate the work at
some point. Forking just for the sake of translation sounds problematic,
though. Maybe I'm wrong about this being a review requirement--or maybe
the upstream author would be open to switching to English variable names?
Sorry again about the anglocentrism...
3. There are another way : deploying it to an independent server. For
> example
>
> a. use the upstream server like this
> <http://%E6%BC%A2%E5%AD%97.%E6%84%8F%E5%82%B3.%E5%8F%B0%E7%81%A3/%E2%BF%B1%E2%BF%B0%E7%81%AB%E7%81%AB%E2%BF%B0%E7%81%AB%E7%81%AB.png?%E5%AD%97%E9%AB%94=%E5%AE%8B%E9%AB%94>
> b.use a server maintained by we, Taiwan Chapter, providing service for
> C.J.K.V wiki_____ and etc.
>
I don't think we have the option of using a 3rd-party server, nor relying
on a WMF Labs service for production use. We want to have the same uptime
and security guarantees as for the wiki itself. The production
configuration will probably need to look like a dedicated node or cluster
for serving the IDS requests, and we would cache its PNG or SVG responses.
Someone here might be able to correct me, though?
Thanks again for integrating this tool for us!
-Adam
Hi all,
At this week's ArchCom Office hour, we'd like to help the WMF Legal
team ensure our software development practices don't accidentally
cause us to enable all sorts of creepy surveillance because a naive
developer adds it. The challenge, of course, is when the royal "we"
accidentally add something, and then we deploy it (because that's a
pretty routine thing these days). Sometimes, no amount of begging "NO
WAIT, WE DIDN'T *MEAN* TO DO THAT" (no matter how sincere) can undo
the damage done. Wikimedia seems to have a pretty good reputation in
the grand scheme of things, but maintaining that reputation is going
to take a lot of vigilance.
Zhou Zhou filed an RFC about this:
<https://phabricator.wikimedia.org/T145472>
<https://www.mediawiki.org/wiki/Requests_for_comment/Survey_Cookies/Local_St…>
...which seems like a good topic for our Wednesday meeting[1]. Zhou
is hoping to figure out how to build the alerts necessary to
understand when some new form of tracking is created. I'm guessing
there's lots of automated and semi-automated monitoring that we could
create to make keeping track of new cookie uses easier; let's talk
about what's realistic, what WMF needs to invest in directly, and how
our wider community of developers can chip in.
Our meeting is at its usual time (Wednesday 21 UTC, 14 PDT, 23 CEST)
and place (#wikimedia-office).
Rob
p.s. Obligatory reminder about ArchComStatus page[2]
[1]: <https://phabricator.wikimedia.org/E316>
[2]: <https://www.mediawiki.org/wiki/ArchComStatus>
