<tl;dr>: Read https://www.mediawiki.org/wiki/Google_Code-in/Mentors and
add your name to the mentors table and start tagging #GCI-2018 tasks.
We'll need MANY mentors and MANY tasks, otherwise we cannot make it.
Google Code-in is an annual contest for 13-17 year old students. It
will take place from Oct23 to Dec13. It's not only about coding:
we also need tasks about design, docs, outreach/research, QA.
Last year, 300 students worked on 760 tasks supported by 51 mentors.
For some achievements from last round, see
https://blog.wikimedia.org/2018/03/20/wikimedia-google-code-in-2017/
While we wait whether Wikimedia will get accepted:
* You have small, self-contained bugs you'd like to see fixed?
* Your documentation needs specific improvements?
* Your user interface has some smaller design issues?
* Your Outreachy/Summer of Code project welcomes small tweaks?
* You'd enjoy helping someone port your template to Lua?
* Your gadget code uses some deprecated API calls?
* You have tasks in mind that welcome some research?
Note that "beginner tasks" (e.g. "Set up Vagrant") and generic
tasks are very welcome (like "Choose and fix 2 PHP7 issues from
the list in https://phabricator.wikimedia.org/T120336" style).
We also have more than 400 unassigned open #easy tasks listed:
https://phabricator.wikimedia.org/maniphest/query/HCyOonSbFn.z/#R
Can you mentor some of those tasks in your area?
Please take a moment to find / update [Phabricator etc.] tasks in your
project(s) which would take an experienced contributor 2-3 hours. Read
https://www.mediawiki.org/wiki/Google_Code-in/Mentors
, ask if you have any questions, and add your name to
https://www.mediawiki.org/wiki/Google_Code-in/2018#List_of_Wikimedia_mentors
(If you have mentored before and have a good overview of our
infrastructure: We also need more organization admins! See
https://www.mediawiki.org/wiki/Google_Code-in/Admins )
Thanks (as we cannot run this without your help),
andre
--
Andre Klapper | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/
https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-09-05
*=2018-09-05=*
== Callouts ==
* SRE:
Switchover/Switchback dates reminder. *I**t's next week!*
Services: Tuesday, September 11th 2018 14:30 UTC
Media storage/Swift: Tuesday, September 11th 2018 15:00 UTC
Traffic: Tuesday, September 11th 2018 19:00 UTC
MediaWiki: Wednesday, September 12th 2018: 14:00 UTC
Switchback:
Traffic: Wednesday, October 10th 2018 09:00 UTC
MediaWiki: Wednesday, October 10th 2018: 14:00 UTC
Services: Thursday, October 11th 2018 14:30 UTC
Media storage/Swift: Thursday, October 11th 2018 15:00 UTC
IMPORTANT: For the duration of the switchover (1 month), please refrain
from large db schema changes and please avoid deploying any kind of new
feature that requires creation of tables.
IMPORTANT: There will be a train freeze in the week of Sept 10th and Oct
8th.
* Fundraising campaigns
https://meta.wikimedia.org/wiki/CentralNotice/Calendar
* RelEng -> Language:
https://gerrit.wikimedia.org/r/#/c/integration/config/+/450508/
Release Engineering: No train next week, DC switchover
== Audiences ==
=== Contributors ===
==== Community Tech ====
* Blocked by:
* Blocking:
* Updates:
** No update.
==== Anti-Harassment Tools ====
* Blocked by:
* Blocking:
* Updates: Partial blocks RFC's last call ends today at 2pm PST. We could
use help on reviewing the new blocking code. Stack of commits here (and
dependents): https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/440871/
**
==== Editing ====
* Blocked by:
* Blocking:
** Updates:
** No update
==== Growth ====
* Blocked by:
* Blocking:
* Updates:
** No update.
==== Language ====
* Blocked by:
** RelEng: https://gerrit.wikimedia.org/r/#/c/integration/config/+/450508/
* Blocking:
* Updates:
** ContentTranslation version 2 work continues.
=== Readers ===
==== iOS native app ====
* Blocked by:
* Blocking:
* Updates:
** Working on 6.1 (
https://phabricator.wikimedia.org/tag/ios-app-v6.1-narwhal-on-a-bumper-car/)
** Wikidata editing + some bug fixes. Investigating our bigger editing goals
==== Android native app ====
* Blocked by:
* Blocking:
* Updates:
** Completed user testing of navigation updates.
** Completed notifications, to be released within ~1 week
==== Readers Web ====
* Blocked by:
* Blocking:
* Updates:
** Mobile website (MinervaNeue / MobileFrontend):
*** Page issues
https://www.mediawiki.org/wiki/Reading/Web/Projects/Mobile_Page_Issues
**** Bug fixing: T203386 T203050 T202568 T203449 T202349 T202940
**** New / old treatment A/B test can be seen here
https://readers-web-master.wmflabs.org/wiki/Pharmacovigilance?mobileaction=…
*** Invest in the MobileFrontend & MinervaNeue frontend architecture
https://www.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFro…
**** Introduce Webpack and QUnit to MobileFrontend T199452 T202742
**** Client side error reporting for Minerva+MobileFrontend T202026
*** Avoid abrupt and jarring white flash in media viewer: T197110
*** Other fixes: T202374 T202701
** Desktop website (Popups):
*** Maintenance: T203013 T202748
** PDF rendering (Proton)
https://www.mediawiki.org/wiki/Reading/Web/PDF_Functionality
*** Improve Chromium halt behavior T181623
** Product and design are continuing advanced mobile contributions
https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions
==== Readers Infrastructure ====
* Blocked by:
** Language Team – Reverting https://phabricator.wikimedia.org/T199941 via
https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Babel/+/446766 resolution
so we can un-revert MW core
* Blocking:
** None known.
* Updates:
** Maps, MCS, PCS: Nothing particularly exciting.
** ReadingLists: Finishing tests case and incresing coverage, both service
(RESTbase) and extension (T184545 and T184544).
==== Multimedia ====
* Updates
** design review on SDoC search prototype
** structured data on File page - multi-lingual captions
** next - MCR integration
==== Parsing ====
* Blocked by: None
* Blocking: None
* Updates: Team offsite coming up week of Sept 10th through 15th
==== UI Standardization ====
* Blocked by:
* Blocking:
* Updates:
** No update.
== Technology ==
=== Analytics ===
* Blocked by:
* Blocking:
* Updates:
** Testing out presto (facebook OS project, extremely fast SQL query
engine for hadoop). This will be the datastore we deploy to cloud
environment once we make public the edit data lake data. We will be
creating a debian install
** IRC meeting about modern event data platform, RFC to decide the use
cases the initial mvp for schema registry will support.
** We will be deploying new code to API to be able to serve edit
metrics “per project family” such us: “Edited pages for all wikipedias or
all wikibooks”, later these metrics will be surfaced on wikistats UI
** As of today we will be computing pageviews for
usability.wikimedia.org and strategy.wikimedia.org
** Doing some experiments with systemd timers versus cron.
=== Cloud Services ===
* Blocked by:
* Blocking:
* Updates:
** No update.
=== Fundraising Tech ===
* Blocked by:
* Blocking:
* Updates:
** CiviCRM
*** Trying to speed up donation import
*** Fixing UI bugs
** Various things to let people opt-in to email lists
** Bug fixes for recurring donations
** Using stretch/PHP7 for payment notification listener, testing it for
payments-wiki
** Final touches on CentralNotice / Landing page stats pipeline
=== MediaWiki Core Platform ===
* Blocked by:
* Blocking:
* Updates:
** Continuing to review stakeholder inputs for Tech Conf
** Lots of work towards phan-taint-check-plugin being voting for all
deployed extensions + skins
** "Don't throw an exception when waiting for replication times out" merged
** Research storage for recommendation API (
https://phabricator.wikimedia.org/T203039)
** Officially deploying the stable summary endpoint
** Parsoid content negotiation
** Work on job queue for deleting pages with many revisions,
GuzzleHttpRequest, PoolCounter, and PHPUnit test improvements
** fixcopyright.wikimedia.org
=== Performance ===
* Blocked by:
**
* Blocking:
**
* Updates:
** No update.
=== Release Engineering ===
* Blocked by:
** None.
* Blocking:
** None.
* Updates:
** Train:
*** 1.32.0-wmf.20 at group 1, no problems
*** on European time this week
*** No train next week, DC switchover
** Log Health:
*** Exception thrown for failure to save settings appears ~ 1000 times/day:
https://phabricator.wikimedia.org/T202149[Contribution?]
*** labtestweb2001 is sending updates to a read-only db host: db2037:
https://phabricator.wikimedia.org/T201082 [Cloud Services?]
*** ErrorException from line EducationProgram PHP Notice: Undefined
variable: retValue: https://phabricator.wikimedia.org/T203577 [?]
=== Research ===
* Blocked by: None
* Blocking: None
* Updates:
** Sent out reminder emails to collect more data (2nd stage of the
experiment) for the Elicit new editor interests research:
https://meta.wikimedia.org/wiki/Research:Voice_and_exit_in_a_voluntary_work…
** Starting data collection for the CitationUsage schema today (had to
delay last week):
https://gerrit.wikimedia.org/r/#/c/operations/mediawiki-config/+/454854/
** Continuing discussion about storage for the Recommendation API:
https://phabricator.wikimedia.org/T203039
=== Scoring Platform ===
* Blocked by: None
* Blocking: None
* Updates:
** Working on PoolCounter support continues, tested on labs, ready for
poduction
=== Search Platform ===
* Blocked by:
* Blocking:
* Updates:
** Removed indexing of empty tokens:
https://phabricator.wikimedia.org/T192502
** Enabled loading categories from daily diffs on internal cluster:
https://phabricator.wikimedia.org/T201217
** Working on improving Korean analyzers:
https://phabricator.wikimedia.org/T178925
** Working on running multiple Elastic instances on the same hardware:
https://phabricator.wikimedia.org/T193654
** Working on searching for Wikidata statement values without additional
keywords: https://phabricator.wikimedia.org/T163642
** Working on ES 6.3 upgrade: https://phabricator.wikimedia.org/T197960
** Working on query parsing refactoring:
https://phabricator.wikimedia.org/T185108
=== Security ===
* Blocked by:
* Blocking:T177765: New service request: chromium-render/deploy
* Updates:
**Should be resolved by end of week per engineer
=== Site Reliability Engineering ===
* Blocked by:
** None
* Blocking:
** None
* Updates:
Switchover/Switchback dates reminder
Services: Tuesday, September 11th 2018 14:30 UTC
Media storage/Swift: Tuesday, September 11th 2018 15:00 UTC
Traffic: Tuesday, September 11th 2018 19:00 UTC
MediaWiki: Wednesday, September 12th 2018: 14:00 UTC
Switchback:
Traffic: Wednesday, October 10th 2018 09:00 UTC
MediaWiki: Wednesday, October 10th 2018: 14:00 UTC
Services: Thursday, October 11th 2018 14:30 UTC
Media storage/Swift: Thursday, October 11th 2018 15:00 UTC
IMPORTANT: For the duration of the switchover (1 month), please refrain
from large db schema changes and please avoid deploying any kind of new
feature that requires creation of tables.
IMPORTANT: There will be a train freeze in the week of Sept 10th and Oct
8th.
== Wikidata ==
* Blocked by:
* Blocking:
* Updates:
** No update.
== German Technical Wishlist ==
* Blocked by:
* Blocking:
* Updates:
** No update.
== Multi-Content Revisions ==
* Blocked by:
* Blocking:
* Updates:
** Last task for phase 2 (file caption support) nearing completion
** Phase 3 (statement support) tasks in progress
** CI issues with deployment fixed and deployment moving forward
== SoS Meeting Bookkeeping ==
* Updates:
**
Hello,
As part of normalizing change tag schema [1] I just switched on reading
from the new column (ct_tag_id in change_tag table, a foreign key to ctd_id
from change_tag_def table) in beta cluster [2] which means new rows will
have empty string as their value of ct_tag. [3]
We are not rushing to flip the switch in production but I just wanted to
send this email asking people who test in beta cluster to file a
phabricator ticket if they see anything unexpected in there that might be
related change tags. This table is being read if someone checks history,
recent changes, watchlist, user contributions, or whole lot of other
special pages plus lots of API queries. I checked anything I could think of
but I might have missed something. Any extra pair of eyes would be
extremely appreciated.
[1]: https://phabricator.wikimedia.org/T185355
[2]: https://phabricator.wikimedia.org/T196671
[3]: For example:
MariaDB [enwiki]> select ct_id, ct_rc_id, ct_rev_id, ct_tag, ct_tag_id from
change_tag order by ct_id desc limit 10;
+--------+----------+-----------+-----------------------+-----------+
| ct_id | ct_rc_id | ct_rev_id | ct_tag | ct_tag_id |
+--------+----------+-----------+-----------------------+-----------+
| 217824 | 633991 | 384018 | | 3 |
| 217823 | 633990 | 384017 | | 3 |
| 217822 | 633989 | 384016 | | 3 |
| 217821 | 633988 | 384015 | | 3 |
| 217820 | 633987 | 384014 | | 3 |
| 217819 | 633986 | 384013 | mw-undo | 2 |
| 217818 | 633985 | 384012 | mw-undo | 2 |
| 217817 | 633984 | 384011 | visualeditor-wikitext | 29 |
| 217816 | 633983 | 384010 | mobile web edit | 16 |
| 217815 | 633983 | 384010 | mobile edit | 15 |
+--------+----------+-----------+-----------------------+-----------+
10 rows in set (0.00 sec)
Thank you!
Best
--
Amir Sarabadani
Software Engineer
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
Is it possible to override messages part of MediaWiki core via an
extension. I tried adding to an extension's en.json file and that didn't
seem to work, but am wondering if there's another way.
Is it possible for an extension to add a language? If so, then the
extension's mylang.json file could only define those that need overriding
and fallback on another language for everything else.
Thanks,
James
Hi. I am not sure if it is important enough so I could add "High" or
"Unbreak more", so please pay attention. The page moving does not work
properly any more. Thank you.
Igal (User:IKhitron)
https://phabricator.wikimedia.org/T203661
Following the recent outage, we've had a new series of complaints
about the lack of improvements in CX, especially related to
server-side activities like saving/publishing pages.
Now, I know the team is involved in a long-term effort to merge the
editor with the VE, but is there an end in sight for that effort? Can
I tell people who ask "look, 6 more months then we'll have a much
better translation tool"?
Is there a publicly available roadmap for this project and more
generally, for CX?
Thanks,
Strainu