Google Code-in 2017 just started:
https://www.mediawiki.org/wiki/Google_Code-in/2017
You might remember the announcement email from a few weeks ago.[1]
In the next seven weeks, many young people are going to make their
first contributions to Wikimedia. Expect many questions on IRC and
on mailing lists by newcomers who have never used IRC or lists
before. Your help and patience is welcome to provide a helping hand!
Thanks to all mentors who have already registered & provided tasks!
You have not become a mentor yet? Please consider it!
You get some smaller tasks fixed and it is fun!
* Think of easy tasks in your area that you could mentor.
Areas are: Code, docs/training, outreach/research, quality
assurance, and user interface. "Easy" means 2-3h to complete for
you, or less technical ~30min "beginner tasks" for onboarding).
* OR: provide an easy 'clonable' task (a task that is generic and
could be repeated many times by different students).
* Note that you commit to answer to students' questions and to
evaluate their work within 36 hours (but the better your task
description the less questions. No worries, we're here to help!)
For the full info, please check out
https://www.mediawiki.org/wiki/Google_Code-in/Mentors
and ask if something is unclear.
Thank you again for giving young contributors the opportunity to learn
about and work on all aspects of Free & Open Source Software projects.
Now bring your tasks!
Cheers,
andre
[1] https://lists.wikimedia.org/pipermail/wikitech-l/2017-October/088956.html
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
The latest version of all major browsers support C/C++/etc code compiled to
WebAssembly <http://webassembly.org/> ("wasm") format, in addition to the
older "asm.js" style of compilation targeting a subset of JavaScript
directly.
As far as I know the first library that MediaWiki uses to support
WebAssembly is ogv.js, my codec & playback library which we use for playing
media on Safari, IE, and Edge. ogv.js is packaged with the
TimedMediaHandler extension, and we've used its asm.js mode for about two
years now.
I'd like to enable the WebAssembly mode in production for the faster
compilation times, but want to double-check that we've established some
best practices for WebAssembly usage first.
https://phabricator.wikimedia.org/T181451 -- I've started up a provisional
RFC, currently more of a document with a few pain points called out:
* packaging (check in binaries from a library, or use a package manager
like npm?)
* loading (loading .wasm or .js files as assets, vs what can use RL)
* security (where to concentrate for security reviews, etc)
This may grow into a recommendation on how to package & load things and
some tweaks to RL. If anybody has any questions about the scariness that is
wasm, give a shout. I want to make it not-too-scary. :)
-- brion
Hi Sarah,
thanks for working on this!
On Tue, Nov 21, 2017 at 2:31 PM, Sarah R <srodlund(a)wikimedia.org> wrote:
> Documentation like this is critical for our open software environment to
> work. I'm organizing a special interest group[4] to address
> documentation needs. If you have any questions or comments, please dont
> hesitate to reach out and share!
> [4] https://wikitech.wikimedia.org/wiki/SIGDOCS
>
Is there any particular reason to do it on wikitech? Most of the other SIGs
[1] and most of our documentation is on mediawiki.org (which is in general
a better maintained place). The ORES docs live there too, apart from a few
pages that are concerned with operations issues.
[1] https://www.mediawiki.org/wiki/Special_Interest_Groups
https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-11-22
= 2017-11-22 =
== Callouts ==
* If you use and process Parsoid HTML, please test your code with Parsoid
master (merged patches for section tag addition + use of figure-inline tag)
* It looks like Remex got turned off on the cluster on Oct 26 as part of
https://phabricator.wikimedia.org/T178632 .. I didn't know about this till
last week (because of some gaps in Phab notifications). When you switch off
a feature in production, please make sure the responsible folks know about
it. :-)
* [Performance] Seeing some performance regressions being reported under
Firefox 57; working with Mozilla to understand whether these are real or if
they're due to a bug in FF57 NavTiming.
* node service-runner provides node GC metrics to statsd from v2.4.3 so all
node services can have it out of the box
* Biggest fundraising campaign of the year starts Tuesday - please
double-check with fr-tech if you're about to do anything that might affect
CentralNotice or donatewiki.
== Audiences ==
=== Readers ===
==== iOS native app ====
* Blocked by:
* Blocking:
* Updates: still working on 5.8
https://phabricator.wikimedia.org/project/view/2913/
==== Android native app ====
* Blocked by:
* Blocking:
* Updates:
==== Reading Web ====
* Blocked by:
* Blocking:
* Updates:
** A print button was added to the mobile site
** We made progress with working out how to deploy Chromium inside
puppeteer and are continuing to work with services to get the pdf render
service up and running
==== Reading Infrastructure ====
* Blocked by:
* Blocking:
* Updates:
** working on Reading Lists performance improvements, hoping to deploy next
week
** work continues on summary and media endpoints
==== Multimedia ====
* Blocked by:
* Blocking:
* Updates: WMDE is moving on some work for MediaInfo, in the meantime
Multimedia is focusing on 3D, which should be ready to move out in early
December.
==== Discovery ====
* Blocked by:
* Blocking:
* Updates:
** Deployed SVGs on www.wikipedia.org portal
===== Maps =====
* Blocked by: None
* Blocking: None
* Updates:
** Paul attended training at PGConf Seattle and intends to put together a
learning session
** Ops person out this week
=== Community Tech ===
* Blocked by:
* Blocking:
* Updates:
** we were mostly conducting our survey.
=== Contributors ===
==== Editing ====
* Blocked by:
* Blocking:
* Updates:
==== Parsing ====
* Blocked by:
* Blocking:
* Updates:
** Next big Parsoid deploy
*** section-tag and figure-inline-tag patches merged; YET to bump HTML
version number to 1.6.0
*** html5 ids patch in WIP; depending on how that goes, we may bundle that
with the next deploy with a HTML version bump from 1.5.0 -> 1.6.0;
*** If you use and process Parsoid HTML, please test your code with Parsoid
master
*** Parsoid should be backward compatible for the html -> wikitext
direction; we should be able to process v1.5.0 or the newer HTML (or some
combination of the two as well :)). Please report bugs if you see any
problems.
*** If testing early next week goes okay and we get a green from everyone,
we will deploy next Thursday. If not, will push to the following week
** Tidy replacement
*** It looks like Remex got turned off on the cluster on Oct 26 as part of
https://phabricator.wikimedia.org/T178632 -- for whatever reason, Phab
didn't notify me when James added me to the ticket, and Tim may not have
known either. I've added both of us to the RemexHTML project .. so
hopefully will receive project notifications in the future. But, when you
switch off a feature in production, please make sure the responsible folks
know about it. :-)
*** Tim has fixed the problem and the fix will go out next week.
** Linter
*** Over the last week, I finished running a script to re-generate linter
issues for all pages on all (active) wikis. This should hopefully have
initialized linter issues for all wikis (and removed false positives based
on Parsoid fixes).
==== Global Collaboration ====
* Blocked by: nobody
* Blocking: ops on dumps, Roan STILL hasn't talked to Ariel, apologies
again, talking to Ariel as we speak
* Updates:
** Translate extension's RC filters are now converted to the new system,
that means almost all WMF wikis are fully converted except super edge cases
like incubator
** Live update on RC will probably be deployed next week, stay tuned for
announcement
==== Contributors Design ====
* Blocked by:
* Blocking:
* Updates:
== Technology ==
=== Analytics ===
* Blocked by:
* Blocking:
* Updates:
=== Cloud Services ===
* Blocked by:
* Blocking:
* Updates:
** Annual Toolforge survey kicked off on Monday; will run for 2 weeks --
https://phabricator.wikimedia.org/T177126
** After much load testing we think Labvirt1015 is fit for duty.
** Andrew back from vacation
** Cloud VPS instances were switched to use Puppet's future parser on Monday
=== MediaWiki Platform ===
* Blocked by:
* Blocking:
* Updates:
=== Performance ===
* Blocked by:
* Blocking:
* Updates:
** Seeing some performance regressions being reported under Firefox 57;
working with Mozilla to understand whether these are real or if they're due
to a bug in FF57 NavTiming.
=== Release Engineering ===
* Blocked by:
** ops: [https://phabricator.wikimedia.org/T180524 Upgrade latest
docker-registry.wikimedia.org/nodejs-devel to stretch]
* Blocking:
* Updates:
* [Team vacations] Mukunda is out all week. Dan is only working on Monday.
And of course Thurs/Fri for all US staff.
* [MediaWiki Train] Catching up after last week’s delay due to the wikidata
database crash. No MW train this week. Played catchup yesterday. All on
wmf.8
* [Offsite] More team offsite logistics. Will be doing some cross team
gathering with Reading (who we’re sharing a hotel/couple days overlap with).
* A lot of Gerrit repository and Github mirror administration this past
week.
* [Phabricator] Caused and fixed a degradation of Phabricator’s search
functionality last Wednesday night/Thursday morning (15th and 16th). We
apologize if you were affected by this. [wiki] [email]
=== Research ===
* Blocked by:
* Blocking:
* Updates:
=== Scoring Platform ===
* Blocked by:
* Blocking:
* Updates:
** https://mediawiki.org/wiki/ORES/FAQ &
https://wikitech.wikimedia.org/wiki/SIGDOCS
** draft_quality data coming to English Wikipedia, doing small DB key
things.
** wp10 (article quality) data is going to be available for English
Wikipedia
** Nov 20 outage on ruwiki and frwiki, Special:RecentChanges and Special:W
atchList caused by ORES. We're drafting an incident report by the end of
the day.
** We'd love to work with Global Collaboration to improve robustness on the
pages that rely on ORES, to provide graceful degradation.
** Perhaps Global Collaboration wants to share QA resources?
*** Roan: Happy to, on both.
=== Search Platform ===
* Blocked by: none
* Blocking: none
* Updates:
** Working on improvements to LTR training
https://phabricator.wikimedia.org/T177520
** Improving completion suggester interaction with namespaced prefix search
https://phabricator.wikimedia.org/T178474
** Preparing for next relevancy survey
https://phabricator.wikimedia.org/T176428
** Reviewing Serbian morphological libraries
https://phabricator.wikimedia.org/T178926
** Working on porting Selenium tests from Ruby to JS
** Working on upgrade to Elastic 5.5 - search clusters upgraded, logstash
next
** Working on indexing Wikidata descriptions and adding them to fulltext
search
=== Security ===
* Blocked by:
* Blocking:
* Updates:
** Reviews:
*** mediawiki-services-chromium-render
*** Ex:WikipediaExtracts
=== Services ===
* Blocked by: none
* Blocking: none
* Updates:
** Continuing to reshape cassandra cluster and moving more nodes to
Cassandra 3 cluster
** service-runner provides node GC metric now to statsd
*** After a deploy you will be able to make a GC graph this for your
service
***
https://grafana.wikimedia.org/dashboard/db/jobqueue-eventbus?panelId=13&ful…
=== Technical Operations ===
* Blocked by:
* Blocking:
* Updates:
== Wikidata ==
* We are aware of review requests for description indexing for Search, as
well as the request by the Structured Commons team.
* RDF exports support foreign repository now, needed for Structured Data on
Commons: https://phabricator.wikimedia.org/T161592
* Worked on making statements on Forms editable and persistent:
https://phabricator.wikimedia.org/T163724
* Worked on fine-grained usage tracking in Wikibase' Lua library:
https://phabricator.wikimedia.org/T172914
* Worked on caching constraint check results:
https://phabricator.wikimedia.org/T179849
== German Technical Wishlist ==
* Blocked by:
* Blocking:
* Updates:
==== Fundraising Tech ====
* CentralNotice:
** Aware that the Selenium tests are still on Ruby, would like to put off
the nodejs update till January.
** Deployed a little bit of debugging code for the large banner switch
campaign mixin
* Payments forms: deployed little style fixes to buttons, putting off
deploying validation changes till January
* CiviCRM: contact de-duplication improvements for large dollar amount
donors, de-duplicating organization records
* More refinements to stats reported to Prometheus
Hi,
I'm looking for someone who has ~15 minutes to check (and potentially
update) the ten mediawiki.org pages listed in
https://phabricator.wikimedia.org/T173815#3673839
I'd like to see the term "web API" replaced by either "action API" or
"REST API" to clarify for developers which API those pages refer to.
So if you feel knowledgeable enough in this area:
Your help on that Phabricator task is welcome!
Thanks in advance,
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
Rainbow colors! Here's a plain text one for those who can't read the fancy
colors:
Hi Everyone,
I've been working together with Adam and Aaron from the Scoring Platform
team to identiy technical documentation in need of improvement. This past
quarter, the team and I worked together on a FAQ for ORES[1], which is now
up and running. If you are interested in ORES, AI, or technical
documentation in general, ORES documentation is a great place to contribute.
We've got answers for most of the common questions, but we haven't finished
100% yet. You can help us by asking new questions on the discussion page
for the FAQ[2]. I hope you can join us in editing BOLDly[3] by working on
documentation that makes our projects more accessible and easier to
understand.
Documentation like this is critical for our open software environment to
work. I'm organizing a special interest group[4] to address documentation
needs. If you have any questions or comments, please dont hesitate to reach
out and share!
[1] https://mediawiki.org/wiki/ORES/FAQ
[2] https://mediawiki.org/wiki/Talk:ORES/FAQ
[3] https://en.wikipedia.org/wiki/Wikipedia:BOLD,_revert,_discuss_cycle
[4] https://wikitech.wikimedia.org/wiki/SIGDOCS
With much Kindness,
Sarah R. Rodlund
Senior Project Coordinator-Product & Technology, Wikimedia Foundation
srodlund(a)wikimedia.org
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
This meeting is an offer by WMDE’s tech team. Hosts of tomorrows meeting
are: @Lucas_WMDE & @Thiemo_WMDE.
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.
I've just now enable the feature flag on the Beta Cluster[1] that allows
MediaWiki to store comments longer than 255 bytes.
The web UI has not been updated to allow longer comments in places where it
enforces a limit, such as the edit summary box. But if you use the API to
edit, or perform page moves or do other things where long comments could be
entered and were truncated, you should now find that they're truncated at
1000 Unicode characters rather than 255 bytes.
Please test it out! If you find errors, or places in core features (not
comments in extensions such as SecurePoll, AbuseFilter, CheckUser, or Flow)
where *new* comments are still being truncated to 255 bytes, or places
where comments aren't showing up at all, please let me know. You can reply
to this message or post a task in Phabricator and add me as a subscriber.
If things go well, we'll look at rolling this out to production wikis once
the schema changes to the production databases are complete. See
https://phabricator.wikimedia.org/T174569 to follow progress there.
If anyone is interested in submitting patches for the web UI to reflect the
changed length limits, please do. I'll try to review them if you add me as
a reviewer.
[1]: https://deployment.wikimedia.beta.wmflabs.org/wiki/Main_Page
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
Hey there.
I love MediaWiki and have been using it everywhere for years. Recently
I've been doing some rather major documentation and I realised there
were three features which would be really handy for me (if these or
similar already exist I would love to know!):
1. For links to articles in sections on the same page it would be really
handy if we had syntax like: [[#unity|]] which would auto-complete to
[[#unity|unity]] for you.
2. For duplicated content it would be handy if you could define a bunch
of "variables" down the bottom of a page and then reference them from
elsewhere. I am aware of templates, but those are overkill and difficult
to maintain per my use case (my use case is documenting the "purpose" of
a computer, I duplicate this in various places, but don't want to
maintain templates for that).
3. It would be cool if for any given wiki page an "estimated reading
time" could be provided. Along with maybe a word count, character count,
etc.
Since I'm here, quick thanks to the MediaWiki community for creating
such wonderful wiki software!
Regards,
John Elliot V
--
E: jj5(a)jj5.net
P: +61 4 3505 7839
W: https://www.jj5.net/