Hello all!
Here are the minutes from this week's meeting:
* Last Call for Comments: Introduce page creation log
<https://phabricator.wikimedia.org/T12331>. If no pertinent issues remain
unaddressed by January 17, this RFC will be approved for implementation. Patch:
<https://gerrit.wikimedia.org/r/#/c/399897/>
* Last Call for Comments: Introduce PlatformSettings.php
<https://phabricator.wikimedia.org/T182020>. If no pertinent issues remain
unaddressed by January 17, this RFC will be approved for implementation.
* First major MCR patches going live next week. The Revision class is now
deprecated, use RevisionStore or RevisionRecord instead.
<https://gerrit.wikimedia.org/r/#/c/399174>
* Patch for MCR database schema is also merged, new tables are not used yet.
<https://gerrit.wikimedia.org/r/#/c/378724/>
* There was an issue with increased response times for several days over the
holidays, the cause is still unknown. Ops is investigating.
* The #architecture project on phabricator has been archived, since nobody was
using the associated workboard. Could be revived as a plain “yellow” tag if needed.
* TechCom to use next week’s meeting for going over old/stale RFCs
You can also find our meeting minutes at
<https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes>
See also the TechCom RFC board
<https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>.
--
Daniel Kinzler
Principal Platform Engineer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.
Hello all!
Addshore last night merged the patch[1] that is the first major step towards
Multi-Content-Revisions[2]: it completely guts the Revision class and turns it
into a thin proxy for the new RevisionStore service. The new code is now live
on beta.
This is our second attempt: The first one, on December 18th, thoroughly
corrupted the beta database. It took us some time and a lot of help from Aaron
and especially Roan to figure out what was happening. A detailed post-mortem by
Roan can be found at [3].
Anyway - this stage of MCR development introduces the new multi-revision capable
interface for revision storage (and blob storage) [4]. It does not yet introduce
the new database schema, that will be the next step [5][6]. While doing the
refactoring, I tried to keep the structure of the existing code mostly intact,
just moving functionality out of Revision into the new classes, most importantly
RevisionRecord, RevisionStore, and BlobStore.
Beware that with the next deployment (due January 2nd) the live sites will start
using the new code. Please keep an eye out for any strangeness regarding
revision handling. Adam greatly improved test coverage of the relevant code
(thanks Adam!), but it's always possible that we missed some edge case, maybe
something about archived revisions that were partially migrated from on old
schema or something similarly fun.
Exiting times!
Cheers
Daniel
[1] https://gerrit.wikimedia.org/r/#/c/399174/
[2] https://www.mediawiki.org/wiki/Requests_for_comment/Multi-Content_Revisions
[3] https://phabricator.wikimedia.org/T183252#3853749
[4] https://phabricator.wikimedia.org/T174025
[5] https://phabricator.wikimedia.org/T174024
[6] https://phabricator.wikimedia.org/T174030
--
Daniel Kinzler
Principal Platform Engineer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.
https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-01-03
= *2018-01-03* =
== Callouts ==
* Ops/DBAs. Reminder that s5 will have readonly time on 9th January as s8
will become the online wikidata shard.
https://phabricator.wikimedia.org/T181645,
https://phabricator.wikimedia.org/T177208
* Search PF would like somebody from performance/MediaWiki team to look at:
https://phabricator.wikimedia.org/T183101 we’ve got some fails on
LinksUpdate which blocked search index update which makes Wikidata items
invisible in search (~50 items)
== Audiences ==
=== Readers ===
==== iOS native app ====
* Blocked by: none
* Blocking: none
* Updates:
**Releasing 5.7.4 this week - minor bug fixes related to article loading,
new navigation bar behavior
**Continuing work on 5.8 - synced reading lists
==== Reading Infrastructure ====
* Blocked by: Ops on puppet code review:
** https://gerrit.wikimedia.org/r/#/c/397623/
** https://gerrit.wikimedia.org/r/#/c/395694/
* Blocking: none
* Updates:
** vacation
** working on T167400 (WP0 piracy) + T174993 (vandalism)
==== Maps ====
* Blocked by: None
* Blocking: none
* Updates:
- Everyone has been on vacation
=== Global Collaboration ===
* Blocked by: Security on response to
https://phabricator.wikimedia.org/T144467
* Blocking: Ops on Flow dumps; Matt is working on it
* Updates:
** A bunch of bug fixes for Special:Recentchangeslinked
** Roan working on refactoring the change_tag schema (inspired by
Cenarium and Ladsgroup), will write a small RFC later this week
=== Community Tech ===
* GlobalPreferences is almost ready.
* Analyzing new proposals.
== Technology ==
=== Analytics ===
* Wikistats UI launch, working on bugs filed by community members.
* Working on TLS and kafka with brandon for the ciphers we will use
* Working on new APIs to report pageview data by country
* Blogpost about wikistats launch
* Some troubles on dbstore (the analytics box that holds the
wiki-replicas). We might need to order new hardware
* We order 8 new boxes for cluster which brings total to 50 nodes
* Started work on geowiki project (editors per country, internal data only)
users of this project are mostly internal (Asaf’s team)
=== Technical Operations ===
* Blocked by:
** None
* Blocking
** None
* Updates:
** Very quiet week, most everyone on vacation.
=== Services ===
* Blockers: none
* Updates:
** Very quite because of vacations and holidays
** Mathoid storage in Cassandra 3 cluster populated, transition blocked
by renderer bugs
** Preparing next round of Cassandra reshapes
=== Fundraising Tech ===
* Deploying (and debugging) stuff we held back for the fundraiser
* CiviCRM enhancements
* Writing some python code to help with banner impression stats collection
* More thoughts on how to replace our kafkatee -> payments cluster log
parser system: https://phabricator.wikimedia.org/T179841
=== Release Engineering ===
* Blocked by
** None
* Blocking
** None?
* Updates
** wmf.15 going out this week
=== Performance ===
* Blocked by: none
* Blocking: none
* Updates
** HHVM hangs resulted in increased save times over the holiday weekend:
https://phabricator.wikimedia.org/T183889
** Addressing a couple of edge cases in Thumbor, little general impact
** Mostly quiet (holidays)
=== Search Platform ===
* Blocked by:
* Blocking:
* Updates:
* Would like somebody from performance team to look at:
https://phabricator.wikimedia.org/T183101 we’ve got some fails on
LinksUpdate which blocked search index update which makes Wikidata items
invisible in search (~50 items)
* Working on fixes for completion suggester & redirects namespaces
* Investigating ElasticSearch phonetic search (
https://phabricator.wikimedia.org/T182708)
* Wikidata search fixes for delay & space handling will be deployed with .15
* Working on refactoring search profiles to make them more config-like
https://phabricator.wikimedia.org/T183279
* Collecting feedback for Wikidata fulltext & prefix search rankings
=== Scoring Platform ===
* Blocked by: No blockers, thanks to great RelEng and Ops work!
* Blocking:
* Updates:
** switching ORES to stretch
** continuing Extension:ORES refactoring (Collab/Roan are looped in)
Dear Wikimedians,
Registration and scholarship applications for the Wikimedia Hackathon
2018 are open!
The hackathon will be taking place in Barcelona between 18 – 20 May 2018.
Scholarship applications are open until January 30, 2018.
- Register here:
https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2018/Register_and_Attend
- Event details here:
https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2018
Depending on your case and situation (e.g., applying for scholarship),
you might need to fill more than one form, please read carefully.
Do not hesitate to forward this announcement along to any relevant
mailing lists!
Looking forward to seeing you in Barcelona!
I[0] am an Outreachy Round 15 intern and I am working on AICaptcha[1]
project. This project is aimed at creating a better captcha system (like
the Google invisible captcha) which can prevent/reduce the incidence of
bots creating user accounts and spamming Wikipedia. My mentors on this
project are Gergő Tisza[2] and Adam Roses Wight[3].
The key aspects of this project are:
1. Data capture for training a machine learning classifier which is
elaborated in Phabricator task[4]. The data can be captured from the
registration page using the WikiMediaEvents extension.
2. Feature selection, dealing with selecting the most appropriate features
which can improve the classification model, explained in Phabricator task[5]
3. Finding appropriate machine learning classifier to create the model [6].
Kindly provide suggestions/ideas on Phabricator, so that any idea missed by
oversight can be discussed. Also if there are any possible issues which I
have not thought about yet, please comment on the tasks so that I can take
care of them sooner rather than later.
Links:
[0]: https://meta.wikimedia.org/wiki/User:Groovier
[1] : https://phabricator.wikimedia.org/project/profile/3137/
[2]: https://www.mediawiki.org/wiki/User:Tgr_(WMF)
[3]: https://www.mediawiki.org/wiki/User:Adamw
[4]: https://phabricator.wikimedia.org/T183991
[5]:https://phabricator.wikimedia.org/T183998
[6]: https://phabricator.wikimedia.org/T184013
Thanks
Vinitha
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2017-12): 315
Active Maniphest users (any activity) in (2017-12): 870
Task authors in (2017-12): 461
Users who have closed tasks in (2017-12): 261
Projects which had at least one task moved from one column to another on
their workboard in (2017-12): 252
Tasks created in (2017-12): 2083
Tasks closed in (2017-12): 1559
Open and stalled tasks in total: 37166
Median age in days of open tasks by priority:
Unbreak now: 19
Needs Triage: 346
High: 614
Normal: 843
Low: 1092
Lowest: 1043
(How long tasks have been open, not how long they have had that priority)
Active Differential users (any activity) in (2017-12): 28
TODO: Numbers which refer to closed tasks might not be correct, as
described in https://phabricator.wikimedia.org/T1003 .
Yours sincerely,
Fab Rick Aytor
(via community_metrics.sh on phab1001 at Mon Jan 1 00:00:27 UTC 2018)
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 4-5 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
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/681/51985.
Hello,
I checked the FAQs and asked one question on french Wikipedia but got no answer.
The subject of the email says all but here is an example.
If you look at the wikipedia article :
https://fr.wikipedia.org/wiki/Pince
it lists many articles for different types of pliers.
I you hover over the links, it will display a preview (hover-preview)
with a small text and most of the time a small image of the
corresponding pliers.
(This is quite useful to learn the name of a particular type of pliers
without opening a lots of tabs :).)
I saw that the link "la pince universelle ;" didn't show any image but
when I looked at the corresponding article, it did have an image
(https://fr.wikipedia.org/wiki/Pince_universelle).
I tried to correct that, comparing the code between
https://fr.wikipedia.org/wiki/Pince_%C3%A0_avoyer that displayed an
image in its hover-preview and
https://fr.wikipedia.org/wiki/Pince_universelle, without success. (I
changed "File:" with "Image:").
I think this is a bug that the image of the article
https://fr.wikipedia.org/wiki/Pince_universelle isn't displayed in its
hover-preview, but I would like to know what you think about it (maybe
the problem stems from the fact that the file has whitespaces in its
name.)
Moreover, I have a feature request : it would be great if the
edit-preview would also display the hover-preview so that you can
validate your modifications also with respect to the hover-preview of
the article.
Happy new year, best regards,
Laurent Lyaudet