Re: [Wikitech-l] RFC Discussion Wednesday - new namespace for collaborative judgments about wiki entities

[Stas Malyshev]

Hi!

> Hi, thanks for pointing this out!  Here are the workflows we've identified
> so far, and how JADE might affect them in the long-term:

On a cursory look, there's also some affinity between this and what
Wikibase Quality Constraints extension is doing. Though this data is not
human generated but automatic, but still this is quality-related data
which is linked to page content (and different for each revision AFAIU).
Currently if I understand right it has its own storage.

-- 
Stas Malyshev
smalys...@wikimedia.org

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] RFC Discussion Wednesday - new namespace for collaborative judgments about wiki entities

[Adam Wight]

On Wed, Aug 22, 2018 at 12:54 PM Ryan Kaldari 
wrote:

> It should also be noted that there are some existing stop-gap
> implementations for specific use-cases that could effectively be replaced
> by JADE such as the PageAssessments extension
> , the page tags
> system in the PageTriage extension
> 


Hi, thanks for pointing this out!  Here are the workflows we've identified
so far, and how JADE might affect them in the long-term:

* Huggle: JADE as a communication backend to indicate which pages have been
patrolled, what the damaging/not-damaging conclusion was, and any comments
the patrollers might leave.
* Recent changes patrol: Similar to Huggle.
* New pages patrol: Storage for sharing draftquality and draft topic data.
* Articles for creation: Similar to NPP.
* en:WP:RATER: Shared storage for articlequality data.
* FlaggedRevs: Similar to patrolling.
* PageTriage: Similar to patrolling.
* Wiki Labels: "blind", write-only store for labelers
* ORES training: high-quality data source for human-labeled observations.


> and ORES' existing database storage.
>

This last one is not a good fit, actually.  The ores_* tables and service
are optimized for bot requirements, for example we'll need to mass purge
all scores produced by an old model when an update is deployed.  These
scores should all be regenerated using the new model.  We're planning to
leave the ORES runtime architecture almost untouched, with one large
exception: JADE data will be provided in parallel, so a request for "all
scores on revision 123456" will give ORES scores and JADE data, and we'll
recommend that the client prefer JADE data since we expect it to be higher
quality.

-Adam

>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] RFC Discussion Wednesday - new namespace for collaborative judgments about wiki entities

[Ryan Kaldari]

It should also be noted that there are some existing stop-gap
implementations for specific use-cases that could effectively be replaced
by JADE such as the PageAssessments extension
, the page tags
system in the PageTriage extension
, and ORES' existing
database storage.

On Wed, Aug 22, 2018 at 12:11 PM Daniel Kinzler 
wrote:

> While preparing for this meeting, I came across this table which is
> burried in
> the task description:
>
>
> https://docs.google.com/spreadsheets/d/1y7CPeAFpjOO-FTXLhp9qfO3lx6-OsaroCMNSNJMUFqc/edit#gid=0
>
> This is a decision matrix exploring some alternatives to the current
> proposal.
> If you are interested in the upcoming discussion, perhaps have a look at
> this as
> well.
>
> Am 20.08.2018 um 23:46 schrieb Kate Chapman:
> > Hi All,
> >
> > A reminder that TechCom is hosting a RFC discussion via IRC on
> > Wednesday. Introduce a new namespace for collaborative judgments about
> > wiki entities 
> >
> > This meeting is to discuss the use of JADE to record the judgments and
> > discuss concerns related to this approach.
> >
> > The meeting is scheduled for 22 August at 2pm PST(21:00 UTC, 23:00 CET)
> > in #wikimedia-office
> > If you haven't joined a #wikimediaoffice meeting before more information
> > can be found here:
> > 
> >
> > More information regarding the TechCom RFC process is available here:
> >
> https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Processes#RFC_process
> >
> > Thanks,
> >
> > Kate
> >
>
>
> --
> Daniel Kinzler
> Principal Platform Engineer
>
> Wikimedia Deutschland
> Gesellschaft zur Förderung Freien Wissens e.V.
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] RFC Discussion Wednesday - new namespace for collaborative judgments about wiki entities

[Daniel Kinzler]

While preparing for this meeting, I came across this table which is burried in
the task description:

https://docs.google.com/spreadsheets/d/1y7CPeAFpjOO-FTXLhp9qfO3lx6-OsaroCMNSNJMUFqc/edit#gid=0

This is a decision matrix exploring some alternatives to the current proposal.
If you are interested in the upcoming discussion, perhaps have a look at this as
well.

Am 20.08.2018 um 23:46 schrieb Kate Chapman:
> Hi All,
> 
> A reminder that TechCom is hosting a RFC discussion via IRC on
> Wednesday. Introduce a new namespace for collaborative judgments about
> wiki entities 
> 
> This meeting is to discuss the use of JADE to record the judgments and
> discuss concerns related to this approach.
> 
> The meeting is scheduled for 22 August at 2pm PST(21:00 UTC, 23:00 CET)
> in #wikimedia-office
> If you haven't joined a #wikimediaoffice meeting before more information
> can be found here:
> 
> 
> More information regarding the TechCom RFC process is available here:
> https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Processes#RFC_process
> 
> Thanks,
> 
> Kate
> 


-- 
Daniel Kinzler
Principal Platform Engineer

Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] 2018-08-22 Scrum of Scrums meeting notes

[Grace Gellerman]

https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-08-22

= *2018-08-22*  =
== Callouts ==
* SRE:

Switchover/Switchback dates finalized

Services: Tuesday, September 11th 2018 14:30 UTC
Media storage/Swift: Tuesday, September 11th 2018 15:00 UTC
Traffic: Tuesday, September 11th 2018 19:00 UTC
MediaWiki: Wednesday, September 12th 2018: 14:00 UTC

Switchback:

Traffic: Wednesday, October 10th 2018 09:00 UTC
MediaWiki: Wednesday, October 10th 2018: 14:00 UTC
Services: Thursday, October 11th 2018 14:30 UTC
Media storage/Swift: Thursday, October 11th 2018 15:00 UTC

IMPORTANT: For the duration of the switchover (1 month), please refrain
from large db schema changes and please avoid deploying any kind of new
feature that requires creation of tables.
IMPORTANT: There will be a train freeze in the week of Sept 10th and Oct
8th.

* Release Engineering blocked by: Feedback needed (*how problems could have
been prevented*) from many people/teams on a recent MediaWiki train related
incident report.
** 1.32.0-wmf.13, 9 blockers, feedback needed for 8 of them:
https://wikitech.wikimedia.org/wiki/Incident_documentation/20180717-Train
** Aaron Schulz (Performance), Adam Wight (Scoring Platform), Bartosz
Dziewoński (Contributors), Brad Jorsch (MediaWiki Platform), C. Scott
Ananian (Contributors), Daniel Kinzler (Wikimedia Deutschland), Timo Tijhof
(Performance), Prateek Saxena (Audiences Design)
* Release Engineering looking for more participants to join the Code Health
Metrics working group. This group's purpose is to define and later
implement a set of core metrics that we will use to asses the health of our
code base.  More info:
https://www.mediawiki.org/wiki/Code_Health_Group/projects/Code_Health_Metrics


== Audiences ==
=== Readers ===
 iOS native app 
* Blocked by: -
* Blocking: -
* Updates:
**6.0.0 released (
https://phabricator.wikimedia.org/tag/ios-app-v6.0-walrus-on-a-unicycle/ )
** 6.0.1 to be released next week (
https://phabricator.wikimedia.org/tag/ios-app-v6.0.1-walrus-on-a-golf-cart/
)
** 6.1 up next, release date TBD (
https://phabricator.wikimedia.org/tag/ios-app-v6.1-narwhal-on-a-bumper-car/
)

 Android native app 
* Blocked by:
* Blocking:
* Updates:
** Finishing up polling Echo notifications (limited to certain types of
notifications initially)


 Readers Web 
* Blocked by:
* Blocking:
* Updates:
** Mobile website (MinervaNeue / MobileFrontend):
*** Page issues UI and instrumentation: T191528 T201124 T197932 T196150
*** Invest in the MobileFrontend & MinervaNeue frontend architecture:
T188937
*** Avoid abrupt and jarring white flash in media viewer: T197110
*** Other fixes and hygiene: T197499 T199000 T197497 T202021 T201956


 Readers Infrastructure 
* Blocked by:
* Blocking:
* Updates:
** PCS:
*** Separating pagelib CSS from base CSS this week
*** Adding simple header to mobile-html (title, description, page image)
** Maps:
*** Nothing to report.

 Parsing 
* Blocked by:
* Blocking:
* Updates:
** Nothing to report


 Multimedia 
* Blocked by:
* Blocking:
* Updates
** SDoC: Discussion with search team about searching for related statements
** SDoC: prototyping depicts search
** SDoC: design artwork
** No longer blocked by MCR


=== Contributors ===
 Community Tech 
* Blocked by:
* Blocking:
* Updates:
** No update.


 Anti-Harassment Tools 
* Blocked by:
* Blocking:
* Updates:
** Continuing work on Partial Blocks:
https://phabricator.wikimedia.org/T2674
** Updated the TechComm RFC to include Multiblocks:
https://phabricator.wikimedia.org/T199917

 Editing 
* Blocked by:
* Blocking:
** Updates:
** Improved/bug fixes: collapsed tables in visual diffs; insertion of
horizontal rules; pages with lots of tables in WTE 2017; switching between
visual editor and source mode; VE linking in IE11; regressions with icon
displays; etc.
** Compact multiple transactions into one:


 Growth 
* Blocked by:
** SRE: Query about plausibility of measuring e-mail traffic to our
no-reply addresses https://phabricator.wikimedia.org/T202329
* Blocking:
* Updates:
** No update.


 Language 
* Blocked by:
* Blocking:
* Updates:
** No update.


=== Audiences Design ===
* Blocked by:
* Blocking:
* Updates:
** No update.


 UI Standardization 
* Blocked by:
* Blocking:
* Updates:
** No update.


== Technology ==
=== Analytics ===
* Blocked by:
* Blocking:
* Updates:
** Changes to hash and salt (every 90 days) appinstallIDs are on, these
will be retained (hashed) forever
**Working with performance in making eventlogging javascript module lighter
so it can be loaded on 1st page load.
**Working on computing “top contributors” metric per project so it is
available in wikistats2, this is one of the most coveted reports by our
community.
**Spark available now in Jupyter notebooks.
**Meetings around modern event data platform to define what parts will we
start developing next quarter.


=== Cloud Services ===
* Blocked by:
* Blocking:
* 

[Wikitech-l] ORES repositories are now moved to wikimedia organization in github

[Amir Sarabadani]

Hey,
ORES repositories used to exist in wiki-ai organization in github.com. For
example you could reach them at github.com/wiki-ai/ores or
github.com/wiki-ai/wikilabels
They all are now moved to wikimedia organization. So they exist in
github.com/wikimedia/ores or github.com/wikimedia/wikilabels. You can get
list of all of scoring platform team repos in [1]

This is needed for better organizational hierarchy and maintenance and also
better support for git LFS [2]. The old URLs redirect to the new ones so
you should not face any issues in developments but at one point in really
far future these might stop working, so please make sure you update the
urls. Also, if you encounter any issues, let me know.

Sorry for any inconvenience and thank you for your contribution.

[1]: https://github.com/orgs/wikimedia/teams/scoring-platform/repositories
[2]: https://git-lfs.github.com/

Best
-- 
Amir Sarabadani
Software Engineer

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/029/42207.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l