Original version: https://www.mediawiki.org/wiki/Topic:Td5wfd70vptn8eu4
The Wikimedia Developer Summit 2017 is 13 weeks away!
PARTICIPANTS
* 68 people have requested an invitation.
* 19 of them have requested travel sponsorship as well.
Join us: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit.
The deadline to request travel sponsorship is Monday, October 24th.
PROPOSALS
* 8 proposals submitted - https://phabricator.wikimedia.
org/project/view/2205/
** 1 in backlog
** 2 in Unconference
** 2 missing basic information
** 3 to be pre-scheduled
https://www.mediawiki.org/wiki/Wikimedia_Developer_
Summit/Call_for_participation
The deadline for submitting new proposals is Monday, October 31.
MAIN TOPICS
https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Program
On track:
* A plan for the Community Wishlist 2016 top results
* Building on Wikimedia services: APIs and Developer Resources
* How to manage our technical debt
Missing basic information
* A unified vision for editorial collaboration
* Building a sustainable user experience together
* How to grow our technical community
Missing two facilitators
* A unified vision for editorial collaboration
* How to grow our technical community
Missing one facilitator
* Handling wiki content beyond plaintext
* Building a sustainable user experience together
* Artificial Intelligence to build and navigate content
ORGANIZATION
* Meet the Program committee. https://www.mediawiki.org/
wiki/Wikimedia_Developer_Summit/Program_committee
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hello all -
The next CREDIT showcase is a week from today - Wednesday, 7-December-2016
at 1900 UTC (1100 San Francisco).
https://www.mediawiki.org/wiki/CREDIT_showcase
If you have a demo, please add it here:
https://etherpad.wikimedia.org/p/CREDIT
Last month there were demos on offline, IFTTT, and File properties search &
new WDQS visualizations.
https://www.youtube.com/watch?v=NmfqtP3pr2Y&t=47
We welcome demos from Wikimedia community members and staff alike - from
polished features to something you just got working last night. Hope to see
you soon!
If you would like to invite anyone to CREDIT, feel free to use this
template.
*Hi <FNAME>*
*I hope all is well with you! I wanted to let you know about CREDIT, a
monthly demo series that we’re running to showcase open source tech
projects from Wikimedia’s Community, Reading, Editing, Discovery,
Infrastructure and Technology teams. *
*CREDIT is open to the public, and we welcome questions and discussion. The
next CREDIT will be held on December 7th at 11am PT / 2pm ET / 19:00 UTC. *
*There’s more info on MediaWiki
<https://www.mediawiki.org/wiki/CREDIT_showcase>, and on Etherpad
<https://etherpad.wikimedia.org/p/CREDIT>, which is where we take notes and
ask questions. You can also ask questions on IRC in the Freenode chatroom
#wikimedia-office (web-based access here
<https://webchat.freenode.net/?channels=%23wikimedia-office>). Links to
video will become available at these locations shortly before the event.*
*Please feel free to pass this information along to any interested folks.
Our projects tend to focus on areas that might be of interest to folks
working across the open source tech community: language detection,
numerical sort, large data visualizations, maps, and all sorts of other
things.*
*If you have any questions, please let me know! Thanks, and I hope to see
you at CREDIT.*
*-YOURNAME*
https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-11-30
= 2016-11-30 =
== Product ==
=== Reading ===
==== Android native app ====
* Last week:
** Continuing Q2 goals for Wikidata descriptions
** New fundraising announcement explore feed card in progress
** Fixing login and editing issues
* Next week (https://phabricator.wikimedia.org/project/view/2352/):
** More Q2 goals for Wikidata descriptions (tutorial and polish)
====Web====
* Current sprint:
https://phabricator.wikimedia.org/tag/reading-web-sprint-86-%F0%9F%94%AA%F0…
* This week:
** Stopped HoverCards A/B tests from Russian and Italian Wikipedias
** New readers work
** MobileFrontend regression fixes
** Make PageImages return the image in the lead section
** MobileFrontend tech debt
** Trending service
** Hovercards rewrite
====iOS====
* Last Week:
** Found and fixed notification bugs, crashes found in 5.3.0, ready for
5.3.1 release
** Finished announcement card updates, ready for 5.3.1 release
** Finished data layer updates, ready for beta in 5.3.2
** Continued dynamic font size updates to the app
* This week: 5.3.1 https://phabricator.wikimedia.org/project/view/2357/ &
5.3.2 https://phabricator.wikimedia.org/project/view/2281/
** Ship 5.3.1 (any remaining bug fixes)
** Beta 5.3.2
==== Mobile Content Service (MCS) ====
* Board: https://phabricator.wikimedia.org/tag/mobile-content-service/
* added Wikibase ID to mobile-sections output
* introducing eslint as part of the node template update
==== Reading Infrastructure ====
* working on random MediaWiki tech debt
* not blocking
* Still looking for reviews on the API error/warning i18n patches (see last
week)
=== Community tech ===
* Blocked: Nope
* Blocking: Nope
* Updates:
* Continued improvements to Copypatrol (
https://tools.wmflabs.org/copypatrol)
* Community wishlist survey is in voting phase:
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey
== Editing ==
=== Parsing ===
* Blocked: Tim asked for an ops person to work with him to puppetize
HTML5Depurate service; yet to hear back as of y'day
* Tim working on https://phabricator.wikimedia.org/T151702 with Ops;
* Arlo's work on Parsoid-native <gallery> extension is now merged. Once we
update the specs at https://www.mediawiki.org/wiki/Specs/HTML/1.3.0 and
chat with Services folks, we'll deploy this.
* Kunal continuing to work on the Linter extension (scheduled to be
deployed in Q3 2016-17).
* Scott busy with Dev Summit Planning this previous (short) week, but
trying to finish up patches in Parsoid to parse language variant markup.
== Technology ==
=== Technical Operations ===
* Will not be able to attend, apologies!
* '''Blocked'''
** None
* '''Blocking'''
** None
* Updates
** API outage investigation and actionables ongoing
** Q3 Goals discussion started, please inform ops of dependencies on them
** Goals on track, work ongoing
=== Analytics ===
* Auditing old logs on stat1002 for *deletion*, including: mobile-sampled,
api-usage, sampled, edits (from webrequest), glam_nara, zero. More at
https://phabricator.wikimedia.org/T84618
* Mediawiki history reconstruction project milestone: standard metrics ran
against the imported data give very similar results with much simpler
queries, test dataset loaded into Druid:
https://pivot.wikimedia.org/#edit-history-test
* Adding send-to-graphite functionality to Reportupdater
* Wikistats 2.0 design starting tomorrow
* New hire engineer will start December 12th
* Ongoing:
** upgrading stat boxes and other out-of-warranty boxes
** optimizing last step of mediawiki history reconstruction
** public event streams work
** varnishkafka integration testing
** reaching out to analysts and evengelizing reportupdater and pivot
=== Release Engineering ===
* '''Blocked'''
** None
* '''Blocking'''
** None?
* '''Updates'''
** Reminder that the [
https://lists.wikimedia.org/pipermail/wikitech-l/2016-November/086936.html
deployments
schedule gets weird] between now and the end of the year
** Phabricator replication should be a bit faster thanks to Mukunda
** Scap 3.4 is out -- see the [
https://phabricator.wikimedia.org/diffusion/MSCA/browse/release/debian/chan…]
for details
** MediaWiki and extensions 1.28.0 tarball is now available
=== Security ===
* Security Reviews
* LoginNotify completing from last week
* Recommendations API started this week
* One item need code review
* CentralAuth special pages: https://gerrit.wikimedia.o
<https://gerrit.wikimedia.o3rg/r/#/c/319055/>3
<https://gerrit.wikimedia.o3rg/r/#/c/319055/>rg/r/#/c/319055/
<https://gerrit.wikimedia.o3rg/r/#/c/319055/>
=== Fundraising Tech ===
* Watching logs, tuning fraud settings and queue jobs
* Tweaking internal dashboard
* Updated thank you email
** Parser output had some unexpected <br>s, wondering if that changed lately
**
https://meta.wikimedia.org/w/api.php?page=Fundraising/Translation/Thank_you…
=== Discovery ===
* Load-testing crosswiki searching backend code proceeds, looks fine so far
* New analysis of query features and performance published:
https://commons.wikimedia.org/wiki/File:Query_Features_and_Search_Performan…
* New analysis of BM25 scoring in https://phabricator.wikimedia.org/T147500 -
still working on how to best tokenize zh
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.