// sorry for cross-posting
Hello everyone! I’d like to draw your attention to a software change coming
to wikis this week:
When you click on a footnote which is referenced multiple times in an
article, it can be hard to find your way back to your reading position in
the text.
This will soon become easier: If you have jumped to a multi-referenced
footnote and want to go back to your previous reading position,
1) you can now click on the *jump mark* at the beginning of the footnote
(in most wikis it's an arrow, in some, like enwiki, it's a caret ^). The
tooltip says "Jump back up".
2) or you can click on the *superscript jump mark* in the footnote. The one
leading you back to your original position is now highlighted *bold*.
This second part of the change doesn’t work for wikis where these
superscript jump marks are bold by default, e.g. enwiki. If those wikis
want this highlighting as well, they would need to change their default
style for these superscript jump marks to regular.
Deployment of this change is scheduled for this week’s train [1].
Originating from the German community’s Technical Wishlist, it was made by
Wikimedia Germany’s Technical Wishes team [2].
Feedback is always appreciated. The best place for it is the project talk
page [3]. More information is available on the project page [4] and on
Phabricator [5].
Best,
Johanna for the Technical Wishes team
Hi everyone,
It has been a month since the Wikimedia Technical Conference[1] and the
year is winding down, so it seemed like a good time to send an update on
the Platform Evolution Program[2]. Specifically, I wanted to let you all
know how the Core Platform Team will be following up on the great work
coming out the conference.
For those who didn’t attend, the primary goal of the conference was to
produce the building blocks to develop a 3-5 year platform roadmap, which
in turn will enable us to achieve our program goal: Evolve our technology
platform and development processes to empower the Wikimedia Movement.
Each session was designed to generate action items, decisions, and goals
that will become the building blocks of the roadmap. Session leaders,
scribes, facilitators and attendees worked hard to capture these outcomes
in notes on wiki[3] and in Phabricator[4] (thanks again to all who helped
with this process! 🙏)
Following TechConf, the Core Platform Team along with members of the
Conference Committee has been reviewing all of the session notes and
aggregating major outcomes into a single document. We are working to
publish this document on MediaWiki.org by the new year and will send out
another email when we do so that you will know where to find them. We will
also be asking attendees to review this wiki to ensure we didn’t miss
anything important.
There are also teams and attendees are independently following up on
TechConf outcomes alongside this formal process - this includes authoring
RFCs and planning projects. Once the initial review of the materials is
complete, we will be reaching out to individuals and teams to see how the
Platform Evolution Program and Core Platform Team can support their work.
In addition to guiding the 3-5 year platform roadmap, the outcomes from
TechConf will be used as input into annual planning and the Q3/Q4 work for
the Platform Evolution Program. The WMF officially begins the 3-5 year
strategy and annual planning in January, so we will have more updates as
that process kicks off.
On behalf of the the Conference Committee, Core Platform Team and the
Platform Evolution Program, I would again like to thank everyone who
attended and contributed to the conference. Your time, work and input were
essential to the success of the event and will be invaluable to the
development of the Platform Evolution Program.
Corey
[1] https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2018
[2]
https://www.mediawiki.org/wiki/Platform_Evolution
[3]
https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2018/Session_…
[4]
https://phabricator.wikimedia.org/tag/wikimedia-technical-conference-2018/
--
Corey Floyd
Director of Engineering, Core Platform
Wikimedia Foundation
cfloyd(a)wikimedia.org
Hello!
WMCZ and the WMF Community Relations team are please to confirm the dates
of 17 - 19 May, 2019 for the Wikimedia Hackathon 2019
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2019> which will be
taking place at the National Library of Technology
<https://www.techlib.cz/en/> in Prague, Czech Republic.
We will be opening registration and announcing the event’s main focus areas
in the next week. For now please save the date and send us an email (at
hackathon(a)wikimedia.cz) if you would like to discuss collaboration on focus
areas (highlighted themes and projects), organizing pre-hackathons (smaller
focused events for Wikimedia developers generally organized around a topic
or region, in advance of the main hackathon), or if you have any questions.
We will continue to update the event’s mediawiki page
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2019> as we have more
information!
Thanks!
--
Rachel Farrand
Events Program Manager
Technical Collaboration Team
Wikimedia Foundation
Hello everyone,
One of the main problems of under-resourced Wikipedias is the lack of
content in their languages. We want to tackle this problem by supporting
editors in creating more content in their languages easily.
We are working on a tool to support editors in creating new articles. The
editing tool (Scribe) will display a structure of the new article and
references (with their most important points) for each section, supported
by the information on Wikidata. The project is based on recent research in
document planning, reference discovery and collection, and document
summarization. One of the emphasizes of our project is to keep the
community involved in every step of the development to ensure that we are
serving their needs.
We are currently applying for a Wikimedia project grant and would like to
hear your feedback:
https://meta.wikimedia.org/wiki/Grants:Project/Scribe:_Supporting_Under-res…
Looking forward to hearing from you!
Best,
Lucie
--
Lucie-Aimée Kaffee
I'd like to nominate D3r1ck01 for +2 rights in mediawiki/*. See
https://phabricator.wikimedia.org/T209775 for details.
Copying the contents of the ticket below:
I'd like to nominate Alangi Derick (@D3r1ck01) for +2 on mediawiki/*.
He's been around for a while now (First merged commit was to Echo in
sept 2015), and has contributed to a large number of mediawiki related
repositories. He has also been very active mentoring people as part of
GCI. In particular, I think him having code review rights will be very
helpful with his mentoring students in mentorship programs. I think
this contributor has shown good judgment, and I trust him to know
which things he is capable of reviewing and giving good reviews for
those things.
List of merged commits in gerrit:
https://gerrit.wikimedia.org/r/#/q/owner:%22D3r1ck01+%253Calangiderick%2540…
List of reviews:
https://gerrit.wikimedia.org/r/#/q/reviewedby:%22D3r1ck01+%253Calangiderick…
---
Brian
This year's edition of Google Code-In is already half over:
https://www.mediawiki.org/wiki/Google_Code-in/2018
GCI is still running for another 2½ weeks.
We will need more tasks. If you have a task in mind to mentor, add
it! You can still become a mentor at any time - see the link above!
Thanks to our students and mentors, many tasks are resolved already!
Here is an incomplete list of some achievements:
* VisualEditor now allows editing a table cell by pressing F2; Several
fixes for the "Page Options" dialog; Leading spaces from the
"format" field in TemplateData GUI are now stripped
* Documentation was written how to use our Gerrit test instance
* More unit tests in MW's Thanks and StructuredDiscussions extensions
* Code coverage: Several MW extensions got missing @covers tags added
* MW web upgrade process now handles errors in purgeCache correctly
* Improved the workflow in MW web installer if an error occurs
* MW action API now returns HTTP 405 error code when unsupported http
method used; Included namespace information on the action=info page
* The Wikimedia Hashtags tool on Toolforge now has a JSON endpoint
* The Wikinity tool on Toolforge now has a coordinate format converter
* Pywikibot removes disambiguation brackets in labels to create new
items for articles in Wikidata; unused code removed in some places
* Several fixes and improvements for the JSDoc WMF theme
* Several MW extensions now display their licenses on Special:Version
* Several students took incremental tasks to learn Lua and templates
* Sticker designs!, such as raccoonicorns or "Personal Space Needed"
* Constructed SQL queries in Quarry to get statistics about Wikipedia
* Many fixes & new features for WMCZ's expense tracking app "Tracker"
* In the Wikidata Query GUI, the placeholder now updates the language
dynamically
* Added support for the Eastern Pwo language (kjp) to MW's Names.php
* Mobile frontend/Minerva skin: The "Edit" button is now disabled for
anonymous editors; Control-clicking on an image now opens the image
in a new tab; Moved client side code inside initEditLink to server
* Some Wikimedia site configuration changes were prepared by students
* WikiEduDashboard: Now shows file urls and author in 'Recent Uploads'
on user profile pages; `no-undef` eslint rule enabled; users now get
informed when a course is not listed in any campaigns
* FormWizard extension: Extension group on special page modified and
further small fixes
* Modified the newsletter 'issue announce' summary textbox
...and many many more.
Congratulations & thanks to all our hard-working students and mentors!
andre
--
Andre Klapper | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/
Due to a lucky arrangement of schedules, we are going to move the
deployment-prep project to the new Cloud region this week, starting in a
few minutes. *This includes all of the infrastructure behind the
beta.wmflabs.org site.*
Various people will be standing by to troubleshoot the outages that
result, but for the most part if you see bad behaviors you should
disregard or work around them for the time being.
Once everything is moved and semi-stable I will send a followup email,
at which point the deployment-prep team will once again become
interested in bug reports :)
Sorry for the short notice! With a little luck this should be mostly
painless.
-Andrew
Hey everyone,
The Community Wishlist Survey is now open, and you can post proposals
for projects that you would like the Wikimedia Foundation's Community
Tech team to work on:
https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019
The Community Tech team builds features and makes changes that active
Wikimedia contributors want, and the Wishlist Survey sets the team's
agenda for the next year.
The Wishlist Survey starts with a two-week proposal period, when
contributors from all Wikimedia projects are invited to post, discuss
and improve proposals. After that, there's a two-week voting period,
when everyone can post support-votes on the proposals.
You can post technical proposals until 11 November.
You can vote on proposals from 16 November to 30 November.
The Community Tech team is responsible for addressing the top ten
wishes on the list. If they, after investigating it, find that
something isn't feasible, they need to explain why to the community.
The Wishlist can also be used by volunteer developers and other teams,
who want to find projects to work on that the community really wants.
//Johan Jönsson
--
https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-11-21
*2018-11-21=*
== Callouts ==
* Release Engineering: No train this week due to the Thanksgiving Holiday
* UI Standardization: Feedback welcome on non-proportional, aka monospace
font choice for code https://phabricator.wikimedia.org/T209915
== Audiences ==
=== Contributors ===
==== Community Tech ====
* Blocked by:
* Blocking:
* Updates:
**
==== Anti-Harassment Tools ====
* Blocked by:
* Blocking:
* Updates:
**
==== Editing ====
* Blocked by:
* Blocking:
** Updates:
** Responded to Language's request for feedback
==== Growth ====
* Blocked by:
* Blocking:
* Updates:
** Recording EventLogging events in MySQL in beta broke multiple times this
past week. Perhaps caused by Neutron migration?
**EditorJourney schema logging went live on Thursday for Czech and Korean
wikis.
**WelcomeSurvey is live on cswiki and kowiki despite 2 OOUI bugs: T209716,
T209717. (help from anyone that manages OOUI would be great)
==== Language ====
* Blocked by: None
* Blocking: None
* Updates:
** Apertium and depenencies are updated in Production.
** New shiny graphs for cxserver (service-cxserver) at Graphana available.
Helped to identify issues already!
** ContentTranslation v2 bug fixes continue.
=== Readers ===
==== iOS native app ====
* Blocked by:
* Blocking:
* Updates:
**
==== Android native app ====
* Blocked by:
* Blocking:
* Updates:
**
==== Readers Web ====
* Blocked by:
* Blocking:
* Updates:
**
==== Readers Infrastructure ====
* Blocked by:
* Blocking:
* Updates:
** Announcements changes for English app fundraising are deployed. App
devs: please test asap. https://phabricator.wikimedia.org/T204821
==== Multimedia ====
* Updates
** Mostly bugfixing on beta commons - hoping to invite community comment on
it real soon (honest!)
** Also working on depicts and other statements
==== Parsing ====
* Blocked by: None
* Blocking: None
* Updates: None
==== UI Standardization ====
* Blocked by:
* Blocking:
* Updates:
** Design Style Guide
*** New “Resources” section
https://design.wikimedia.org/style-guide/resources.html
*** Updates on “Typography” and imagery across pages
** Accessibility:
*** Wikipedia Portals freed of technical a11y hurdles
== Technology ==
=== Analytics ===
* Blocked by: performance of cloud replicas for sqooping all rows monthly,
ongoing work and discussion at T209031
* Blocking:
* Updates:
** testing Kerberos with our infrastructure on cloud VMs, progressing well
** work on Modern Event Platform's Event Intake service code going well.
If you want to follow from the very early stages, see
https://github.com/ottomata/eventbus
** XML dumps available in HDFS, see T202489
** ongoing work on sanitizing Hive event database (all EventLogging data)
=== Cloud Services ===
* Blocked by:
* Blocking:
* Updates:
**
=== Fundraising Tech ===
* Blocked by:
* Blocking:
* Updates:
**
=== MediaWiki Core Platform ===
* Blocked by:
* Blocking:
* Updates:
** RFC meeting regarding session storage interface (multi-DC dependency)
continuing tomorrow (https://phabricator.wikimedia.org/T206010 )
** PHP 7.2 tests are now voting for MediaWiki (gerrit:473312)
** Continuing to extract decisions and action items from Tech Conf session
notes
** Actor table rolled out to test wikis and mediawiki.org last week, and to
group 0 this week. No problems reported
** Comment table image_comment_temp merging is done, except for the WMF
schema change (https://phabricator.wikimedia.org/T209591 ).
** Externallinks indexing: DONE! (https://phabricator.wikimedia.org/T209373
)
=== Performance ===
* Blocked by:
**
* Blocking:
**
* Updates:
**
=== Release Engineering ===
* Blocked by:
* Blocking:
* Updates:
** Hired Jeena Huneidi. She will be working on local development and other
developer satisfaction improvements.
https://groups.google.com/a/wikimedia.org/d/topic/foundation-optional/5GXGf…
** Blog post by Dan Duvall: Bring in 'da noise, bring in defunct. It's a
zombie party! Peering into the CI cauldron – October 2018
https://phabricator.wikimedia.org/phame/post/view/127
** Thanks to Krenair, Andrew Boggott, and Bryan Davis for helping make the
Beta Cluster region migration go as smoothly as possible -
https://phabricator.wikimedia.org/T208101
** CI Nodepool stopped yeah! #technical-debt
** Gerrit is alright. Got JavaMelody for monitoring now.
InitialiseSettings.php is too big.
** Blubber build with Blubber
** Code Health:
*** Experimenting with SonarQube https://phabricator.wikimedia.org/T207046
** Train Health:
*** Last week: 1.33.0-wmf.4 deployment blockers
https://phabricator.wikimedia.org/T206658
*** This week: No train due to the Thanksgiving Holiday
*** Next week: 1.33.0-wmf.6 deployment blockers
https://phabricator.wikimedia.org/T206660
=== Research ===
* Blocked by: None
* Blocking: None
* Updates:
** Working on collecting more synonyms for section titles:
https://phabricator.wikimedia.org/T210085
** Preparing to run QuickSurveys for Reader Trust:
https://phabricator.wikimedia.org/T209882
=== Scoring Platform ===
* Blocked by: None
* Blocking: None
* Updates:
** Work on upgrading to celery 4 is officially done
** Jade TechCom RFC discussion coming up regarding JADE storage (22nd @
0600 UTC)
** Investigating on using redis-sentinel for ores
** Fixed scap restart check for ores-celery
=== Search Platform ===
* Blocked by:
* Blocking:
* Updates:
** Worked with DWIM Gadget authors to improve “wrong keyboard” detection:
https://phabricator.wikimedia.org/T138958
** Fixed prefix search with multiple namespaces:
https://phabricator.wikimedia.org/T208255
** Improved Blazegraph reliability:
https://phabricator.wikimedia.org/T206189
** Setting up A/B test for new wikidata completion models:
https://phabricator.wikimedia.org/T209402
** Working on transforming Elasticsearch explains into tensorflow code:
https://phabricator.wikimedia.org/T208917
** Working on ES 6 upgrade: https://phabricator.wikimedia.org/T183282
** Working on running multiple Elastic instances on the same hardware:
https://phabricator.wikimedia.org/T193654
** Working on query parsing refactoring:
https://phabricator.wikimedia.org/T185108
=== Security ===
* Blocked by:
* Blocking:
* Updates: Security Engineers are Reviewing Tasks and are expected to
complete Reviews on time
**
=== Services ===
* Blocked by:
* Blocking:
* Updates:
**
=== Site Reliability Engineering ===
* Blocked by:
** None
* Blocking:
** None
* Updates:
** ATS work (replacing varnish) ongoing. Still a long way from complete,
just FYI
** zoterov2 successfully deployed in staging, production finally next
** php 7.2 installed on appservers
** A lot of reboots happening, should be transparent
== Wikidata ==
* Blocked by:
* Blocking:
* Updates:
**
== German Technical Wishlist ==
* Blocked by:
* Blocking:
* Updates:
**
== Multi-Content Revisions ==
* Blocked by:
* Blocking:
* Updates:
** working on making AbuseFilter work with MCR: (
https://phabricator.wikimedia.org/T208769)
** discussing MCR support for File page layout: (
https://phabricator.wikimedia.org/T209878)
== SoS Meeting Bookkeeping ==
* Updates:
**