Wikitech-l November 2019

wikitech-l@lists.wikimedia.org

53 participants
66 discussions

TechCom Radar 2019-11-20
by Alexandra Paskulin 21 Nov '19

21 Nov '19

Hi all, Here are the minutes from this week's TechCom meeting: * Discussed: RFC OpenGraph descriptions in wiki pages < https://phabricator.wikimedia.org/T213505>. This RFC discusses two approaches for generating wiki page descriptions in OpenGraph protocol. * Discussed: RFC Balanced templates < https://phabricator.wikimedia.org/T114445>. This RFC discussed the specification and implementation for a balance property that can be added to templates in MediaWiki. * Discussed: RFC Process 2019 amendments < https://phabricator.wikimedia.org/T216308>. This RFC was discussed during last week’s Wikimedia Technical Conference. See the task for notes from the unconference session. * No IRC discussion next week. You can also find our meeting minutes at <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes> See also the TechCom RFC board <https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>. If you prefer you can subscribe to our newsletter here <https://www.mediawiki.org/wiki/Newsletter:TechCom_Radar> Best, - Alex -- Alex Paskulin Technical Writer Wikimedia Foundation

1 0

[Wikimedia Tech Talks] Happening Now! Wikidata, behind the curtain
by Sarah R 20 Nov '19

20 Nov '19

Hi All, Just a reminder! This talk is happening now! The link to the Youtube Livestream can be found here: https://www.youtube.com/watch?v=uWqKyC7gt0s See you there! On Thu, Nov 14, 2019 at 11:33 AM Sarah R <srodlund(a)wikimedia.org> wrote: > Hi Everyone, > > It's time for Wikimedia Tech Talks 2019 Episode 10! This talk will take > place 20, November, 2019 at 7PM UTC. > > *Title: *Wikidata, behind the curtain > > *Speaker: *Amir Sarabadani, Software developer, Wikimedia Deutschland > > *Summary:* > > Wikidata is a complex and large-scale project. We all know how to use it > and how to contribute to it but it's a little bit hard to understand how it > actually works, how it scales and what parts are tricky about it. To lots > of developers, it's a black box and this is not good. This talk plans to > explain internals of Wikidata to other developers and explain future > changes to Wikidata on its technical layer. > > The link to the Youtube Livestream can be found here: > https://www.youtube.com/watch?v=uWqKyC7gt0s > > During the live talk, you are invited to join the discussion on IRC at > #wikimedia-office > > You can watch past Tech Talks here: > https://www.mediawiki.org/wiki/Tech_talks > > If you are interested in giving your own tech talk, you can learn more > here: > https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Te… > > *Note:* > *Please feel free to distribute this email to any lists that you feel are > appropriate!* > Hope to see you there! > > Sarah R. Rodlund > Technical Writer, Developer Advocacy > <https://meta.wikimedia.org/wiki/Developer_Advocacy> > srodlund(a)wikimedia.org > >

1 0

(sin asunto)
by Charly Donnari 20 Nov '19

20 Nov '19

Enviado desde mi smartphone Samsung Galaxy.ow31112qqwqqqqwwwqqw22w22

1 0

(sin asunto)
by Charly Donnari 20 Nov '19

20 Nov '19

Enviado desde mi smartphone Samsung Galaxy.5

1 0

Parsoid/PHP enabled on test and test2 wikis and the beta cluster
by Subramanya Sastry 19 Nov '19

19 Nov '19

Hello everyone, Some of might know that the parsing team has been porting Parsoid from Javascript to PHP this year [1]. Over the last couple months, we have done intensive testing in various modes (parser tests, round trip testing, HTML string diff testing) to verify correctness of Parsoid/PHP relative to Parsoid/JS and continued to fix bugs (both Parsoid/PHP & Parsoid/JS). We have also had some client testing and QA on beta cluster via host headers. With all that behind us, we believe it is time to do a bit more intensive live QA. So, we have switched over the beta cluster to use Parsoid/PHP (instead of Parsoid/JS). We have also switched the production test.wikipedia.org and test2.wikipedia.org to use Parsoid/PHP instead of Parsoid/JS. With this change, VisualEditor, Content Translation, and Mobile Content Translation will use Parsoid/PHP on these wikis. Flow / StructuredDiscussions will need a separate config change and will continue to use Parsoid/JS in all these places till that change is written and deployed. If you are able to, please test visual editing and content translation on test and test2 wikis and file phabricator tasks. Bug reports [2] are greatly appreciated. :-) Incident-free switchover from Parsoid/JS to Parsoid/PHP has been our goal and this testing is the next step along that way. You can follow along progress and changes via the tracking phab task [3]. Thanks, Subbu. (on behalf of the parsing team). 1. https://www.mediawiki.org/wiki/Parsing#Current_projects 2. https://phabricator.wikimedia.org/tag/parsoid-php/ 3. https://phabricator.wikimedia.org/T229015

1 0

The difference between fileexists-no-change and backend-fail-alreadyexists for action=upload
by Chen Xinyan 19 Nov '19

19 Nov '19

Hi there, Hope I've found the correct list for asking this question. I was setting up a CI test case for my MediaWiki Client Library to run a bot that will upload a file to https://en.wikipedia.beta.wmflabs.org in chunked stash mode. For most of the time, when I perform the final upload with filekey parameter, I will receive a fileexists-no-change error from the MW API server. This is expected, as there is already a same file with the same title on the site. However, today I received backend-fail-alreadyexists. The error message looks like backend-fail-alreadyexists: The file "mwstore://local-swift-eqiad/local-public/archive/9/95/20191116051316!Test_image.jpg" already exists. Does this error usually occurs when user tries to upload the same file? What's the difference between fileexists-no-change and backend-fail-alreadyexists? Thanks, Xinyan

2 2

s6 primary master switchover (read-only required) 19th Nov 05:00 AM UTC
by Manuel Arostegui 19 Nov '19

19 Nov '19

Hello, We have requested a 30 minutes read-only window for s6 wikis (T235475) for the 19th Nov from 05:00-05:30 AM UTC to switchover that section primary database master (T235469) db1061 is an old host and out of warranty that will be decommissioned (T217396). The new master will be db1131. We are going to do this on Tuesday 19th Nov from 05:00 to 05:30 AM UTC (we do not expect to use the 30 minutes window, if everything goes as expected). Impact: Writes will be blocked on the following wikis frwiki jawiki ruwiki Reads will remain unaffected. Communication will happen at #wikimedia-operations If you are around at that time and want to help with the monitoring, please join us! Thanks

1 2

Composer does not know mediawiki/mediawiki on dry-runs
by Stephan Gambke 17 Nov '19

17 Nov '19

When running `composer update` MediaWiki injects a mediawiki/mediawiki package, so extensions can declare a dependency on a particular MW version range. However, when doing a `composer update --dry-run` this package gets not injected causing the dry run to fail. Does anybody know a solution/workaround? Stephan

6 8

WM Technical Conference 2019 update - day 4
by Deb Tankersley 15 Nov '19

15 Nov '19

Hello and thanks for reading! We wanted to give a quick update on what happened during the final day of the Wikimedia Technical Conference <https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019>, in Atlanta, Georgia. *Friday <https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019/Program#…>, November 15, 2019:* The first morning session looked at LocalDev: complex multi-service MediaWiki development and use cases / personas that need tailored development environments (ticket <https://phabricator.wikimedia.org/T235372>). We also discussed API Integration Testing concentrating on functions, stories, and scenarios (ticket <https://phabricator.wikimedia.org/T234636>). After we dot voted on Thursday morning, we finished up the last unconference sessions on Friday: - New CI / Argo k8s for CI workloads challenges, details, paths forward ( ticket <https://phabricator.wikimedia.org/T238261>) - Wikimedia Space solves all your (communication) problems* (ticket <https://phabricator.wikimedia.org/T238237>) - The test pyramid and speeding up your results (ticket <https://phabricator.wikimedia.org/T234637>) - kiwix / open ZIM. portfolio software stack, future ?, tech needs - What is a technical contribution? (ticket <https://phabricator.wikimedia.org/T238262>) - JS Framework Experience Sharing (ticket <https://phabricator.wikimedia.org/T238264>) - Global templates! Let's flesh it out (ticket <https://phabricator.wikimedia.org/T238251>) - Logspam - how do we have less / surface it to the right people? (ticket <https://phabricator.wikimedia.org/T238250>) - PHPUnit: what can we improve, can we remove phpunit.php wrapper script, etc (ticket <https://phabricator.wikimedia.org/T238227>) - What user analytics would help you as a developer? (ticket <https://phabricator.wikimedia.org/T238274>) - I'll help you replace Travis with Actions for GitHub-mastered repos ( ticket <https://phabricator.wikimedia.org/T238244>) - The gradation of participation - what is a third party? Defining a common phrase with a common – and shared – understanding (ticket <https://phabricator.wikimedia.org/T238234>) - Ukulele to wikitext (ticket <https://phabricator.wikimedia.org/T238290> ) The last session was a Recap and Reflection gathering using a world cafe style discussion (ticket <https://phabricator.wikimedia.org/T238406>) - each of the 5 themes have a notes document that is in their respective epic tickets: - Local Development and onboarding (ticket <https://phabricator.wikimedia.org/T234087>) - Testing (ticket <https://phabricator.wikimedia.org/T234088>) - Deploying and Hosting (ticket <https://phabricator.wikimedia.org/T234089>) - Standardization Decisions (ticket <https://phabricator.wikimedia.org/T234090>) - People and Processes (ticket <https://phabricator.wikimedia.org/T234091>) We also did a group photo <https://commons.wikimedia.org/wiki/File:Wikimedia_Technical_Conference_2019…> in-between raindrops! We ended the day with our last documentation sprint, copying info from the day's sessions and moving them into the phabricator tickets (to keep all the data in one place), taking pictures of the session sticky notes / diagrams, and then adding them also into the phabricator tickets. whew! Photos and documentation that have been uploaded can be viewed using this category <https://commons.wikimedia.org/wiki/Category:Wikimedia_Technical_Conference_…> (look for day 4 <https://commons.wikimedia.org/wiki/Category:Wikimedia_Technical_Conference_…>) on Commons: Category:Wikimedia Technical Conference 2019 <https://commons.wikimedia.org/wiki/Category:Wikimedia_Technical_Conference_…> (sample demo: ukulele to wikitext <https://commons.wikimedia.org/wiki/File:Wikimedia_Technical_Conference_sess…> video). Cheers, The Wikimedia Technical Conference Program Committee -- deb tankersley (she/her) program manager, engineering Wikimedia Foundation

1 0

help once
by Fokou Joel 15 Nov '19

15 Nov '19

I am a student in the Faculty of Engineering and Technology in University of Buea(Cameroon). Thank you!

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l November 2019