Curious what the Community Tech team has been up to for the past few
months? Come to our showcase presentation at 2pm PDT (9pm UTC) in room 112
(the super big conference room), or watch it on the public YouTube stream:
https://www.youtube.com/watch?v=Cm02V1ytJ0Y
We will be covering:
* CodeMirror (syntax highlighting)
* LoginNotify
* Global Preferences
* XTools
* Popular Pages Bot
* Internet Archive Upload Tool
* Unicode Section IDs
* and ACTRIAL
Hey folks,
We were way overdue for an update, so we just put one together. In the
last 3 months, we added new language support for Bengali, Greek, and Tamil.
New advance edit quality support for Albanian and Romanian. We cleaned up
the old 'reverted' models where better support is available. We're working
on moving to a new dedicated cluster. We improved some models by exploring
new sources of signal and cleaning datasets. We started work on JADE and
presented on The Keilana Effect at Wikimania.
Read more on our blog
https://phabricator.wikimedia.org/phame/post/view/77/status_update_october_…
-Aaron
On Sat, Jun 3, 2017 at 3:28 PM, Aaron Halfaker <aaron.halfaker(a)gmail.com>
wrote:
> Hey folks,
>
> I'll be starting to post updates here on our new blog[1], but if you'd
> prefer to be notified via the mailing lists we used to post to, that's OK.
> I'll make sure that the highlights and the link to these posts gets pushed
> there too.
>
> We had a big presence at the Wikimedia Hackathon 2017 in Vienna. We kicked
> off a lot of new language focused collaborations (Greek, Tamil, Bengali)
> and we deployed a new Item Quality model for Wikidata.
>
> French and Finnish Wikipedias now have advance edit quality prediction
> support!
>
> ORES is available through api.php again via rvprop=orescores and
> rcprop=oresscores.
>
> Wiki labels now has a new stats reporting interface. Check out
> https://labels.wmflabs.org/stats
>
> We had a major hiccup when failing over to CODFW, but we worked it out and
> ORES is very happy again.
>
> See more details on our new blog: "Score all the things"
> https://phabricator.wikimedia.org/phame/blog/view/8/
>
> -Aaron
> Principal Research Scientist @ WMF
> Head of the Scoring Platform team
>
As you may be aware, the Timeless skin has been undergoing deployment to
various Wikimedia projects over the past couple of months, thus far
deployed to five french projects, with a pending deployment for five
more hebrew, german, and english projects in the works.
As the primary developer and designer on Timeless, it falls to me to
address most of the issues as they come up, but to be quite blunt, I no
longer have the financial stability to actually do this effectively, so
I have submitted a grant proposal asking for funding for post-deployment
support for Timeless. While the deadline for the community comments
period is technically today, I have unfortunately been ill and unable to
finish the proposal or get word out until now, and so would ask that
anyone with comments, concerns, or other feedback (including and
especially 'the proposal is completely incoherent'), please comment
anyway within the next week (by the 24th) as this way it may be possible
to incorporate and address them such that the grants Committee members
will still be able to review them within the period. Even if not,
comments and such may still prove useful for other purposes - task
prioritisation, demonstration of support if needing to seek funding
elsewhere, etc.
Timeless skin documentation: https://www.mediawiki.org/wiki/Skin:Timeless
Deployment task: https://phabricator.wikimedia.org/T154371
Grant proposal:
https://meta.wikimedia.org/wiki/Grants:Project/Isarra/Post-deployment_suppo…
Thanks!
-Isarra
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow 3-4 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 todays meeting are:
@addshore & @CFisch_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.
(cross-posting to Wikitech and Wikidata; Wikidata is getting this due to
the general interest in data sets and databases)
Greetings,
The Platform Scoring Team at the Wikimedia Foundation are developing an
auditing tool for ORES, the Judgement and Dialogue Engine (JADE) [0]. It's
largely inspired by the false positive reporting work that currently occurs
by hand on wiki pages. JADE's purpose is to provide human oversight to
ORES's AI work.
The team is seeking input in two areas as development begins in two
technical areas: the database schema [1], and the implementation strategy
[2]. If you have thoughts or experience to share in how to best set these
up, please have a look over the pages. Questions, comments, concerns are
welcome on the talk pages [3][4].
Feedback and stories on using ORES in production is also welcome, to help
give the team general ideas about areas of concern and/or improvement that
JADE should keep in mind [5].
Thank you for your time, see you on the wikis.
0. https://www.mediawiki.org/wiki/JADE
1. https://www.mediawiki.org/wiki/JADE/Schema
2. https://www.mediawiki.org/wiki/JADE/Implementations
3. https://www.mediawiki.org/wiki/Talk:JADE/Schema
4. https://www.mediawiki.org/wiki/Talk:JADE/Implementations
5. https://www.mediawiki.org/wiki/Talk:JADE
--
Keegan Peterzell
Technical Collaboration Specialist
Wikimedia Foundation
Dear Wikimedia developers,
TLDR: Please give this a try, subscribe, and forward the link to other
mailing lists or projects: https://www.mediawiki.org/
wiki/Newsletter:Tech_Showcase.
I am of course biased, but I do believe that this newsletter is interesting
basically for any active contributors. The simplest and easiest way to know
about interesting software being developed by staff or volunteers for our
readers and our contributors.
No tech knowledge needed and no time commitment required either. You will
just receive one sentence notifications linking to the fresh software
showcased.
PS: This is a new concept of newsletter for experienced Wikimedians as
well. The Technical Collaboration team hopes that these types of
newsletters will reach new audiences and new voices beyond the power users
following Village Pumps, mailing lists or Phabricator.
---------- Forwarded message ----------
From: Quim Gil <qgil(a)wikimedia.org>
Date: Fri, Oct 13, 2017 at 12:18 PM
Subject: New newsletter: Tech Showcase
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>
Tech curious? This is for you:
Tech Showcase <https://www.mediawiki.org/wiki/Newsletter:Tech_Showcase>
A newsletter (*) about fresh software for Wikimedia caught on the spot.
Plans, prototypes, releases... Do you have a scoop? Tell us in the Talk
page!
Just click "Subscribe" and you will be notified in your preferred Wikimedia
wiki.
https://www.mediawiki.org/wiki/Newsletter:Tech_Showcase
(*) This is a newsletter powered by the Newsletter extension
<https://www.mediawiki.org/wiki/Help:Extension:Newsletter>. Expect one
sentence notifications linking to the tech showcased, not lengthy articles
and prose.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
(sorry for cross-posting)
Dear all,
*TL;DR: *If you don't want to wait until you run into a real edit conflict
to tryout *Two Column Edit Conflict View* [1], you can now test the new
interface on a temporary testpage where you will get simulated edit
conflicts.
*About Two Column Edit Conflict View*
Improving the current UI of the edit conflict resolution page was wish #1
in the 2015 Technical wishes survey of the German-speaking community [2].
The TwoColConflict extension ("Two Column Edit Conflict View") [3]
highlights differences between the editor's and the conflicting change
directly in the textfield for an easy possibility to copy and paste desired
pieces of the text and resolving the conflict. It has been a beta feature
on all wikis for 5 months now and users have been invited to test it and
give feedback. [4]
Here is a rough visualisation of how the Two Column Edit Conflict view
works:
https://commons.wikimedia.org/wiki/File:Two_Column_Edit_Conflict_View_-_rou…
:-)
*The challenge*
We got some feedback on the beta feature, but not enough to get a good
feeling if the product is already great as it is now, or if some changes
are still needed. We assume that's because in order to give feedback,
people have to have the beta feature activated AND have an edit conflict
AND share their feedback - that's a pretty rare combination.
*More testing!*
We've implemented a temporary Special page that serves as a *test page* [5]
where you will get simulated edit conflicts: The new interface can be
tested now without actually having an edit conflict, and without the risk
of messing up real wiki pages.
We'd like to invite everyone to test the new interface with the test page
until November 9, 2017!
Please go to *https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Edit_Conflicts/Feedback_Round_Test_Page
<https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Edit_Conflicts/Feedba…>
*for more informations.
If you know people who might be interested in testing, please spread the
word!
Thank you so much,
Birgit (for the Technical Wishes team)
Links:
[1] Multilingual help page
<https://www.mediawiki.org/wiki/Help:Two_Column_Edit_Conflict_View>
[2] Main project page
<https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Edit_Conflicts>
[3] Extension manual
<https://www.mediawiki.org/wiki/Extension:TwoColConflict>
[4] Central feedback page
<https://www.mediawiki.org/wiki/Help_talk:Two_Column_Edit_Conflict_View>
[5] Ticket on Phab for the Special page
<https://phabricator.wikimedia.org/T170375>
--
Birgit Müller
Community Communications Manager
Software Development and Engineering
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.
https://www.fsf.org/blogs/licensing/update-on-artifex-v-hancom-gnu-gpl-comp…
-------- Messaggio inoltrato --------
Oggetto: Update on Artifex v. Hancom GNU GPL compliance case
Data: Thu, 12 Oct 2017 03:05:18 -0400
[...]
Hancom here made several arguments against the contract claim, but one
is of particular interest. Hancom argued that if any contract claim is
allowed, damages should only be considered prior to the date of their
initial violation. They argued that since the violation terminated their
license, the contract also ended at that point. The judge noted that:
/the language of the GPL suggests that Defendant’s obligations
persisted beyond termination of its rights to propagate software
using Ghostscript ... because the source code or offer of the source
code is required each time a “covered work” is conveyed, each time
Defendant distributed a product using Ghostscript there was arguably
an ensuing obligation to provide or offer to provide the source code./
The judge also found that there was insufficient evidence at this point
to rule on this issue, so we can't read too much into it. [...]
