Hey,
This is the 30th and 31st weekly update from the revision scoring team that
we have sent to this mailing list. We accidentally skipped a week again.
*New development:*
- We added a new "lowest" sensitivity level to ORES review tool. This
new sensistivity level will only flag edits that ORES is very confident are
actually damaging[1].
- We applied the MediaWiki standard color palette to Wikilabels[2]
- We generated a manually censored public dataset of
spam/vandalism/attack pages[3]. This will help others to develop spam,
vandalism and attack page detection models. See the publication of the
dataset[4].
- We've implement color-based confidence reporting for ORES damage
detection[5]
*Maintenance and robustness:*
- We updated the version of OOjs-UI that gets bundled with Wiki
labels[6] and moved the static assets to a new repositiory[7]
- We fixed an issue in the recscoring library[8] that caused ORES to
return invalid JSON and rendered the UI useless[9].
*Communications:*
- We gave a 3 minute presentation on the state of ORES to Victoria
Coleman, the WMF's new CTO[10].
- We performed a basic analysis of Wikipedia article quality trends
using the dataset we released a few weeks ago[11]. We'll have a more
substantial analysis soon.
- We made a post on the ORES review tool talk page[12,13] detailing how
we plan to incorporate a new filtering strategy into the ORES review tool.
Please join the discussion there.
1. https://phabricator.wikimedia.org/T150224 -- Add "Lowest" ORES
sensitivity for fpr=0.1
2. https://phabricator.wikimedia.org/T151119 -- Apply ui standardization
color palette to Wikilabels
3. https://phabricator.wikimedia.org/T150307 -- Create manually vetted
dataset of spam/vandalism/attack pages
4. https://dx.doi.org/10.6084/m9.figshare.4245035
5. https://phabricator.wikimedia.org/T144922 -- Visually report damaging
confidence
6. https://phabricator.wikimedia.org/T151222 -- Update bundled OOJS-ui with
Wikilabels
7. https://github.com/wiki-ai/flask-oojsui
8. https://phabricator.wikimedia.org/T150961 -- ORES ui is broken (text
field disabled)
9. https://github.com/wiki-ai/ores/issues/177
10. https://phabricator.wikimedia.org/T150544 -- ORES (a 2-3 minute
presentation)
11. https://phabricator.wikimedia.org/T151214 -- Basic analysis of
Wikipedia quality using monthly predictions
12. https://phabricator.wikimedia.org/T150858 -- Post about ORES review
tool including ERI filters
13. https://www.mediawiki.org/wiki/Topic:Tflhjj5x1numzg67
Sincerely,
Aaron from the Revision Scoring team
Hi all,
A new version of Scap has been released and with it comes a few changes.
tl;dr highlights:
* Old scap bin stubs (e.g., /usr/bin/sync-file, /usr/bin/sync-dir,
/usr/bin/mwversionsinuse, etc) will now exit 1.
Subcommands are now the only way to interact with scap, i.e., `sync-file` is
now `scap sync-file`.
* Scap3 (non-mediawiki) deploys will now announce deploys in IRC -- you
can specify a message for IRC via:
scap deploy 'A message for the SAL'
* Scap lockfile errors now show you (a) who has the lockfile and (b) their
deploy message. The output you'll see if another person is deploying
looks like:
sync-file failed: <LockFailedError> Failed to acquire lock "/var/lock/scap"; owner is "thcipriani"; reason is "scap 3.4 sync file"
You can see a full changelog for both the 3.4.0-1 and the 3.3.1-1 release on
phabricator[0]. If you spot any issues, file a phabricator task tagged with the
`Scap3` project[1].
-- Your Humble Scap Toilers
[0]. <https://phabricator.wikimedia.org/P4523>
[1]. <https://phabricator.wikimedia.org/tag/scap3/>
Hello everyone!
In preparation for getting hovercards ready for release, the reading-web
team has been working on some changes to the PageImages extension
<https://www.mediawiki.org/wiki/Extension:PageImages> to account for a
number of bug reports on incorrect images or images that may appear out of
context. We are working on the following changes:
1. Allowing Non-free images to appear (when allowed)
2. Allowing PageImages to select images only from the lead section or
infobox of an article
3. Allowing editors to set the PageImage for a page
>From these, we will be applying 1 and 2 within this quarter (and most
likely by the end of this sprint). More details on the changes, including
corresponding tasks can be found here -
https://www.mediawiki.org/wiki/Reading/Web/Projects/PageImagesChanges
Thanks and let us know if there’s any questions!
Cheers,
- Olga
--
Olga Vasileva // Product Manager // Reading Web Team
https://wikimediafoundation.org/
Hi,
I saw this project and I thought it was very interesting:
https://www.wikipediap2p.org/
Basically, it makes the clients connect to each other to share pages
between each other using webrtc before going to the centralized server.
It would probably be a bad idea to convert mobile devices into network
peers given the data restrictions and quality of connections but it seems
like something very interesting for the desktop clients.
Cheers
Hi,
With the release of MediaWiki 1.28, the lifetime of MediaWiki version
1.26.x has come to an end.
Users still using MediaWiki 1.26.x are advised to upgrade to version
1.28.0, the latest stable version.
-Chad
_______________________________________________
MediaWiki announcements mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
Hi all!
For this week's RFC discussion [1], let's talk about per-language URLs for
multilingual wiki pages[2]. The basic idea is to encode the uselang parameter
the the url path so it doesn't break caching. This raises some questions about
purging, and about rendering links.
The meeting will be the usual time (Wednesday 21 UTC, 14 PDT, 23 CEST)
and place (#wikimedia-office).
A brief synopsis of the RFC:
* Need: we want anon visitors to browse multilingual wikis in their language
* Problem: Serving different renderings for the same URL messes with web caches.
* Solution: Encode uselang in the URL path, generate links to the same URL path.
Discussion points:
* Is the proposed solution viable and useful?
* Can we use varnish's xkey feature to purge all language versions of a page?
* What should the path scheme look like? /wiki-fr/Foo or /fr/Foo or...
* On which wiki shall we try this first?
* How do we make a wiki-link to a specific language version of a page?
If you are interested, please comment on the ticket[2] and join the meeting[1].
[1] https://phabricator.wikimedia.org/E384
[2] https://phabricator.wikimedia.org/T114662
--
Daniel Kinzler
Senior Software Developer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.
Hi everyone,
The voting has started on the 2016 Community Wishlist Survey, and all
Wikimedia contributors are invited to come and vote on the projects that
WMF's Community Tech team will work on next year:
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey
There are 267 proposals this year, on a wide range of subjects that I'm
pretty sure you have an opinion about.
You've got two weeks to vote, from now through December 12th. You can vote
for as many proposals as you like, by adding a {{support}} tag under the
proposals that you think are worthwhile.
Once the voting's over, we'll have a ranked list of projects for the
Community Tech team to work on, as well as other developers and volunteers
who want to build features and make changes that the core contributors
really want.
This is an opportunity for you to help set the agenda for a WMF product
team, so I hope everybody comes and participates!
Danny Horn
WMF Product Manager
Community Tech
Hello,
Hovercards, currently a beta feature, is nearing release. [0] We'd like to
encourage communities to adopt Hovercards as a default option for
logged-out readers. [1] Hovercards provide a preview of any linked article,
giving readers a quick understanding of a related article without leaving
the current page. The Reading web team recently completed a series of A/B
tests to gather information on how Hovercards are used.
* April 2015 - Catalan and Greek A/B test results [2]
* Summer/Fall 2016 Hungarian, Italian, and Russian Wikipedia A/B test
results [3]
* 2016 Reading team UX research [4]
As you can see the results of the tests were generally positive. A few key
highlights:
* During the Catalan and Greek A/B test, 79% of respondents either Agreed
or Strongly Agreed that Hovercards were easy to use, 76% of respondents
either Agreed or Strongly Agreed that Hovercards were useful for their
needs.
* Users are viewing approximately 0.99 hovercards per session, and
interacting with approximately 31% more pages each session. [5]
* The disable rate was very low: the rate of clicking the settings cog for
Hovercards was 0.02% for Hungarian, 0.034% for Italian, and 0.016% for
Russian Wikipedia. The rates for disabling the feature were even lower.
* In our qualitative tests, 13 out of 15 questionnaire participants
reported positive experiences with Hovercards.
== Rollout plan ==
The next step for Hovercards is to develop a plan for rolling the feature
out to all projects. We have created a draft proposal for which projects to
discuss Hovercards with and approximate timeline for deployments. [6]
The Reading Web team will be reaching out to the communities in the order
listed above to discuss how to implement the feature. We want to enable the
feature by default for logged-out users and we will respect the current
beta feature preferences for logged-in users.
Questions and feedback welcome at Beta Features/Hovercards. [7]
Thank you for your time.
[0] https://www.mediawiki.org/wiki/Beta_Features/Hovercards
[1] Logged-out users would see Hovercards by default on wikis that opt-in.
Logged-out users may turn Hovercards off via the cog-icon displayed at the
bottom of each Hovercard. Logged-in users see Hovercards if they have
enabled the feature. New accounts created after the launch of Hovercards
would have it on by default (mimicking the default for logged-out users)
with the option to disable in Special:Preferences.
[2] https://www.mediawiki.org/wiki/Beta_Features/Hovercards/GreekCatalanTest
[3] https://www.mediawiki.org/wiki/Beta_Features/Hovercards/2016_A/B_Tests
[4]
https://www.mediawiki.org/wiki/Wikimedia_Research/Design_Research/Reading_T…
[5] With page interactions defined as the sum of average hovercards viewed
per session and average pages viewed per session
[6] https://www.mediawiki.org/wiki/Beta_Features/Hovercards#Rollout_Plan
[7] https://www.mediawiki.org/wiki/Talk:Beta_Features/Hovercards
Yours,
Chris Koerner
Community Liaison - Discovery
Wikimedia Foundation
Hey,
With merge of 320328 [1] and 320341, two major changes will come to ORES
review tool:
1- You will see one more option in ORES sensitivity called "Lowest". It
means if you choose it, it only flags edit that are very likely to be
vandalism.
2- Coloring of rows will be completely different. You will see several
colors instead of one and as confidence of ORES grows, the colors will tend
to be more noticeable. It goes without saying that you can change these
colors in your own css. I put a screenshot in [3] and you can test it in
https://en.wikipedia.beta.wmflabs.org or https://mw-revscoring.wmflabs.org
Feedback is always welcome
[1]: https://gerrit.wikimedia.org/r/#/c/320328/
[2]: https://gerrit.wikimedia.org/r/#/c/320341/
[3]: https://phabricator.wikimedia.org/T144922#2824696
Best
--
Amir Sarabadani Tafreshi
Software Engineer (contractor)
-------------------------------------
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
http://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.