Hi,
kraz, the server running irc.wikimedia.org, will be rebooted next Monday
during the CEST morning. In all previous reboots we found most
clients/tools to reconnect automatically, but if that's not case for
something you care about, please keep an eye on it (and ideally fix it to
reconnect automatically).
Cheers,
Moritz
How did we do in our strive for operational excellence since last month?
Read on to find out!
## The month in numbers
* 2 documented incidents since July 19. [1]
* 55 Wikimedia-log-errors tasks closed after July 19. [2]
* 31 Wikimedia-log-errors tasks created after July 19. [3]
Logstash (type=mediawiki, last 7 days):
* 2,048 fatals. (channel=fatal)
* 117,372 exceptions. (channel=exception)
* 21,043 PHP errors. (channel=error)
* 6,368,647 total error-level events. (channel=*, level=ERROR)
## Highlights
### New database partition
@Josve05a reported that Special:Log was timing out on commons.wikimedia.org
for certain queries. Database administrator @Marostegui, investigated the
underlying query and found out this was caused by one of the backend
database servers having an unpartitioned 'logging' table. Manuel took the
server out of rotation for re-partitioning, which was completed later that
day.
– https://phabricator.wikimedia.org/T199790
### Disappearing audio players, mystery solved
When Étienne Beaulé (@Ebe123) found PHP-Notice errors in the Score
extension, they immediately investigated. It began as the fixing of a typo
that caused
inefficient (but working) parsing of audio data. Upon closer inspection, a
bigger story was uncovered. The computation of audio lengths was being
skipped due to a mismatch in MIME-types between Score and
TimedMediaHandler. The player needs this length, and as a result, browsers
had to download and parse the audio data entirely client-side, creating a
delay of 5-20 seconds or more.
Four months earlier, Andre reported that pressing play on an audio player,
made the player disappear for a long time.
It all makes sense now.
– https://phabricator.wikimedia.org/T192550 /
https://phabricator.wikimedia.org/T200835
### Packet loss
After noticing that exception IDs from error pages were not found in
Logstash, Tim Starling started an investigation. He created a new Grafana
dashboard and the culprit was quickly identified. Over 3000 packets were
being dropped, every second. That's over 90% of server logs – missing!
14 deployments, 9 SAL entries, and 6 days later, we finally reached 0%
packet loss.
Many thanks to Filippo Giunchedi, @BBlack, @herron, @Gehel who got to the
bottom of this.
Our weekly error numbers increased 100X since last month, and.. that's a
good thing!
–
https://grafana.wikimedia.org/dashboard/db/logstash?orgId=1&from=1530097200…
– https://phabricator.wikimedia.org/T200960
### Vips or no Vips
We use the VipsScaler extension to create thumbnails of large TIFF and PNG
files in some cases. Test requests for it failed with "10.2.1.21 port 80:
Connection refused". The error was puzzling because the IP does not belong
to MediaWiki or an image-scaling service. Rather, it belongs to Proton, a
Chromium PDF service.
Investigation from @MoritzMuehlenhoff, @Reedy, and others revealed the
service IP used by Proton since June 2018 previously belonged to the
mediawiki-imagescaler pool (dissolved in April 2018). Configuration for
VipsScaler was outdated and stopped working in April. The issue was not
noticed until the IP address started working again, with an unrelated
service producing errors.
– https://phabricator.wikimedia.org/T199937 /
https://phabricator.wikimedia.org/T199938
## Higher impact
These cause users (of web or api) to see errors.
New:
* [ProofreadPage extension] https://phabricator.wikimedia.org/T201506 -
MWContentSerializationException: The serialization is an invalid JSON array.
* [Flow extension] https://phabricator.wikimedia.org/T201654 -
InvalidArgumentException
"The Title object yields no ID" from Flow\LinksTableUpdater.
* [MediaWiki-Logging] https://phabricator.wikimedia.org/T201411 - Date
input on Special:Log can cause fatal error.
Carried over:
* [Page deletion] https://phabricator.wikimedia.org/T195692 - Undelete for
certain pages aborted by IncompleteRevisionException.
* [AbuseFilter extension] https://phabricator.wikimedia.org/T187153 -
Special:Abuselog throws BadMethodCallException on details/examine.
* [Flow extension] https://phabricator.wikimedia.org/T70526 -
InvalidDataException "Flow workflow is for different page".
* [MobileFrontend] https://phabricator.wikimedia.org/T199066 -
Special:MobileContributions shows "Special:Badtitle" (Revision::ensureTitle
error).
## Noise
These are caused by code behaving unexpectedly, but with limited impact due
to graceful recovery by PHP, or other handling. These harm our ability to
detect and prevent higher impact issues (through Scap and Fatal-Monitor),
and may be masking other issues.
New:
* [FileImporter extension] https://phabricator.wikimedia.org/T200837 - PHP
Notice: Undefined index from WikiTextContentCleaner.php.
* [PagedTiffHandler] https://phabricator.wikimedia.org/T200839 - PHP
Notice: Undefined index from PagedTiffHandler_body.php.
Carried over: None!
All of last month's noise mentions were fixed! 🎉
## Thank you
Thank you to everyone for helping investigate/resolve #Wikimedia-log-errors.
Including:
* Jdforrester-WMF (James D. Forrester)
* matmarex (Bartosz Dziewoński)
* Marostegui (Manuel Aróstegui)
* zeljkofilipin (Željko Filipin)
* Ebe123 (Étienne Beaulé)
* jcrespo (Jaime Crespo)
* dcausse (David Causse)
* Jdlrobson (Jon Robson)
* Addshore (Adam_WMDE)
* EBjune (Erika Bjune)
* Anomie (Brad Jorsch)
* Aaron (Aaron Schulz)
* Reedy (Sam Reed)
Thanks!
Until next time,
-- Timo Tijhof
[1]
https://wikitech.wikimedia.org/w/index.php?title=Category:Incident_document…
[2] https://phabricator.wikimedia.org/maniphest/query/h1j5IXlqAUPJ/#R
[3] https://phabricator.wikimedia.org/maniphest/query/MtotJEtlSU5_/#R
Hello,
I'd like to request advice on handling a task at hand.
It results that Extension:ArticleToCategory2
<https://github.com/wikimedia/mediawiki-extensions-ArticleToCategory2>
is using some sort of old-fashioned way to name their user rights (ie:
ArticleToCategory2AddCat instead of all lowercase; or
ArticleToCategory2 which is somewhat confusing). I'd like to fix that,
but I was wondering if that'd cause undue complications in existing
installs and, if so, if it should go first via a deprecation process
or other process I am not aware off.
Thanks in advance for any help or advice you can offer.
Best regards, M.
https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-08-08
= 2018-08-08 =
== Callouts ==
* Need help reviewing https://gerrit.wikimedia.org/r/#/c/mediawiki/
extensions/WikimediaEvents/+/450021/Anyone? (I added Timo as a reviewer -
Ian)
* Release Engineering: feedback needed from various teams on two recent
MediaWiki train related incident reports. Specifically, how problems could
have been prevented.
*** 1.32.0-wmf.13, 9 blockers, feedback needed for all of them (Audiences
Design, Contributors, MediaWiki Platform, Performance, Scoring Platform,
Wikidata): https://wikitech.wikimedia.org/wiki/Incident_
documentation/20180717-Train
*** 1.32.0-wmf.14, 6 blockers, feedback needed for 2 of them (Performance,
Readers, Wikidata): https://wikitech.wikimedia.org/wiki/Incident_
documentation/20180724-Train
== Audiences ==
=== Readers ===
==== iOS native app ====
* Blocked by:
* Blocking:
* Updates:
**6.0 in beta (https://phabricator.wikimedia.org/tag/ios-app-v6.
0-walrus-on-a-unicycle/) til 8/20
**We'll begin working on 6.0.1 soon (https://phabricator.
wikimedia.org/tag/ios-app-v6.0.1-walrus-on-a-golf-cart/)
==== Android native app ====
* Blocked by:
* Blocking:
* Updates:
** Maintenance update released to production.
** Beginning work on Notifications support: https://phabricator.
wikimedia.org/project/view/3505/
==== Readers Web ====
* Blocked by:
* Blocking:
* Updates:
** Mobile website (MinervaNeue / MobileFrontend):
*** Page issues UI and instrumentation: T191532 T197932 T191528
*** Invest in the MobileFrontend & MinervaNeue frontend architecture:
T188261 T197133
*** Other fixes and hygiene: T199282 T193172 T201131 T197110 T197931
T200867 T200518
==== Readers Infrastructure ====
* Blocked by:
* Blocking:
* Updates:
** MCS patch to prepare for Parsoid <audio> tags in code review:
https://gerrit.wikimedia.org/r/c/mediawiki/services/mobileapps/+/450896,
hope to deploy today
** MCS preparing announcement for Android app multi-language features:
T191640
** Continuing work on mobile-html endpoint improvements (see open subtasks
of T177433)
** Maps (*ping Gehel*):
*** deployment-maps04 is up and running for testing Maps on Stretch in the
BC
*** we're ready for the maps cluster switchover to Stretch
*** maps-test cluster can be decom'd (perhaps, but not necessarily, after
the maps cluster switchover to Stretch)
==== Multimedia ====
* Updates
** Engineering spinning back up
** Search work is progressing and getting merged - the Search team has
promised to do some re-indexing on our behalf
** Fixed an UploadWizard bug for WLM that needs review -
https://phabricator.wikimedia.org/T183075
** Filed a task for security review of MediaInfo (but it's not urgent) -
https://phabricator.wikimedia.org/T200279
** Upcoming work on MediaInfo, MCR
=== Contributors ===
==== Community Tech ====
* Blocked by:
** Security for TemplateWizard review https://phabricator.
wikimedia.org/T198666
* Blocking:
* Updates:
**
==== Anti-Harassment Tools ====
* Blocked by:
* Blocking:
* Updates:
** IRC meeting today about Partial Blocks RFC: https://phabricator.
wikimedia.org/T199917
==== Editing ====
* Blocked by:
* Blocking:
** Updates:
**
==== Parsing ====
* Blocked by:
* Blocking:
* Updates:
- Post-Tidy replacement: Added new lint detection for pages that might
have been affected by Tidy removal: https://www.mediawiki.org/wiki/Help:
Extension:Linter/misc-tidy-replacement-issues
<https://www.mediawiki.org/wiki/Help:Extension:Linter/misc-tidy-replacement-…>
==== Growth ====
* Blocked by:
* Blocking:
* Updates:
**
==== Language ====
* Blocked by:
* Blocking:
* Updates:
** ContentTranslation merge blocker is resolved!
** Niklas responded to Community Tech to inquiry about TranslateSVG:
https://phabricator.wikimedia.org/T201207#4488381
=== Audiences Design ===
==== UI Standardization ====
* Blocked by:
* Blocking:
* Updates:
** OOUI next minor release v0.28 in preparation.
*** Supporting GSOC student Hagar Shilo in finishing up new OOUI
“Tutorials” section, thanks also to Moriel for initiative
*** Preparation of some UI fine-tuning for frameless buttons
** Finishing up SVG optimization in Popups (last product resolved)
https://phabricator.wikimedia.org/T185596
== Technology ==
=== Analytics ===
* Blocked by:
* Blocking:
* Updates:
** “Total article count metric” vetted, available on API now and Wikistats
UI soon
** Eventlogging outage due to attack using very long user agents solved
with “band aid” patch, working on a timeout-for-long-regexes defense:
https://wikitech.wikimedia.org/wiki/Incident_documentation/20180728-
eventlogging
** Data available in wikistats for July, this was the shortest
reconstruction, it took less than 48hrs. Edits split by editor types for
all wikis: https://stats.wikimedia.org/v2/#/all-projects/contributing/edits/
normal
** Took decision of using Json schema (rather than avro) for the Modern
Event Data Platform. Take a look: https://tools.wmflabs.
org/meetbot/wikimedia-office/2018/wikimedia-office.2018-08-01-21.00.log.html
=== Cloud Services ===
* Blocked by:
* Blocking:
* Updates:
**
=== Fundraising Tech ===
* Blocked by:
* Blocking:
* Updates:
** More work on new API integration for main card processor
** More work on email opt-in
** More work on CiviCRM donor data deletion requests
** Ready to start publishing exchange rates to internal Google Doc
** Work almost done on pipeline for EventLogging banner & landiing page data
** Prepping for Monday maintenance window
*** upgrade payments-wiki to new Mediawiki LTS
*** add new columns and indexes to Civi log tables, update db replication
mode
=== MediaWiki Core Platform ===
* Blocked by:
* Blocking:
* Updates:
** Pingback flood issue (T200864)
*** Fixed and filtered erroneous data from graphs
** While investigating pingback, noticed an issue with SQLite upgrade,
fixed (T200861)
** Investigated reports of events lost from Logstash. Created Grafana
dashboard https://grafana.wikimedia.org/dashboard/db/logstash and task
T200960.
** Investigated PHP notice from RemexHtml (T200827)
** Followup change on logging detail globals, complete and merged (T16576)
*** Pushed 3 changesets for unregistered options on maintenance scripts. 1
merged, following up on other 2 (T110209)
** HTTP library discussion Guzzle/Requests, localization (T110022)
** Platform Evolution stakeholder meetings
=== Performance ===
* Blocked by:
** Need access to labstore servers, Cloud Services is already aware
* Blocking:
**
* Updates:
** All wikis are now using mcrouter for memcache reads, instead of
nutcracker
** ResourceLoader changes to defer jQuery dependency and to remove a
roundtrip are in final review, will likely be on the train next week
** Collecting data on how people understand outage response. Survey has
gone out to Technology, will go out to Audiences later on (next week-ish)
** Working on sitemaps generation in order to address https://phabricator.
wikimedia.org/T199252 (and quite a few additional tickets as well)
=== Release Engineering ===
* Blocked by:
** Feedback needed from various teams (too many to name each one) on two
recent MediaWiki train related incident reports. Specifically, how problems
could have been prevented.
*** 1.32.0-wmf.13, 9 blockers, feedback needed for all of them (Audiences
Design, Contributors, MediaWiki Platform, Performance, Scoring Platform,
Wikidata): https://wikitech.wikimedia.org/wiki/Incident_
documentation/20180717-Train
*** 1.32.0-wmf.14, 6 blockers, feedback needed for 2 of them (Performance,
Readers, Wikidata): https://wikitech.wikimedia.org/wiki/Incident_
documentation/20180724-Train
* Blocking:
* Updates:
**
=== Research ===
* Blocked by:
** Code review of https://gerrit.wikimedia.org/r/#/c/mediawiki/
extensions/WikimediaEvents/+/450021/
* Blocking: None
* Updates:
** Carrying out an online experiment as part of "Research:Voice and exit in
a voluntary work environment/Elicit new editor interests"
- https://meta.wikimedia.org/wiki/Research:Voice_and_exit_
in_a_voluntary_work_environment/Elicit_new_editor_interests
<https://meta.wikimedia.org/wiki/Research:Voice_and_exit_in_a_voluntary_work…>
** Participating in a Platform Evolution survey.
=== Scoring Platform ===
* Blocked by:
* Blocking:
* Updates:
=== Search Platform ===
* Blocked by:
* Blocking:
* Updates:
**
=== Security ===
* Blocked by:
* Blocking:
* Updates:
**
=== Site Reliability Engineering ===
* Blocked by:
* Blocking:
* Updates:
** Network issues with switches - T201039 T201145
** Logstash packet loss much much better now - T200960
== Wikidata ==
* Blocked by:
* Blocking:
** We're aware of RelEng waiting for us following up on recent incident
reports. We'll finally do it soon (tm)
* Updates:
**Unblocked Content Translation: https://phabricator.wikimedia.org/T200693
**Work in Lexicographical data continues:
*** adding senses
*** improving the editor workflow
*** https://phabricator.wikimedia.org/project/view/2292/
** Experiment without not using secondary SQL table for formatting item
links coming live soon
*** https://phabricator.wikimedia.org/T196882
== German Technical Wishlist ==
* Blocked by:
Nothing
* Blocking:
No one
* Updates:
** Working on:
*** TwoColConflict
*** Wikidiff2
*** AdvancedSearch
*** FileImporter
== Multi-Content Revisions ==
* Blocked by:
* Blocking:
* Updates:
** Switched all wikis to the "write both, read old" migration stage
(T197816)
** Fixed resulting breakage of wikitech.wikimedia.org (T200963)
** Ran populateContentTables.php on four wikis (T183488)
== SoS Meeting Bookkeeping ==
* Updates:
**
On Wed, Aug 8, 2018 at 8:29 PM, Amir Ladsgroup <ladsgroup(a)gmail.com> wrote:
[...]
> 2) the duration of block which is for one week was determined and
> communicated in the email. You can check the email as it's public now.
Can you be more specific? I'm not sure I see where this is public.
> 3) not being able to discuss cases clearly also bothers me too as I can't
> clarify points. But these secrecy is there for a reason. We have cases of
> sexual harassment in Wikimedia events, do you want us to communicate those
> too? And if not, where and who supposed to draw the line between public and
> non-public cases? I'm very much for more transparency but if we don't iron
> things out before implementing them, it will end up as a disaster.
>
Sure, there are cases where things need to be private to protect
people. This particular case seems like the most clear cut example of
something that does not need to be private. And even in more sensitive
cases, things such as, User X is no longer to do Y for Z time surely
should be public even if some of the details can't be.
--
Brian
So let me just clarify, so despite a few weeks ago the decision was
effectively "we highly encourage but won't require", now it's if you do not
include the coc then we will ban you from phabricator?
Just want to make sure I understand the current stance...
On Wed, Aug 8, 2018, 8:01 AM <wikitech-l-request(a)lists.wikimedia.org> wrote:
> Send Wikitech-l mailing list submissions to
> wikitech-l(a)lists.wikimedia.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> or, via email, send a message with subject or body 'help' to
> wikitech-l-request(a)lists.wikimedia.org
>
> You can reach the person managing the list at
> wikitech-l-owner(a)lists.wikimedia.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Wikitech-l digest..."
>
>
> Today's Topics:
>
> 1. Wednesday: Technical Advice IRC Meeting (Michael Schönitzer)
> 2. My Phabricator account has been disabled (MZMcBride)
> 3. Re: My Phabricator account has been disabled (Mukunda Modell)
> 4. Re: My Phabricator account has been disabled (Alex Monk)
> 5. Re: My Phabricator account has been disabled (MZMcBride)
> 6. SEMANTiCS 2018, Vienna, Sep 10-13, Contribute to the
> Vocarnival & the DBpedia Day (Sebastian Hellmann)
> 7. Re: My Phabricator account has been disabled (Amir Ladsgroup)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 7 Aug 2018 14:57:12 +0200
> From: Michael Schönitzer <michael.schoenitzer(a)wikimedia.de>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>,
> wikitech-ambassadors(a)lists.wikimedia.org,
> wikidata(a)lists.wikimedia.org, wikidata-tech(a)lists.wikimedia.org,
> Wikimedia Cloud Services general discussion and support
> <cloud(a)lists.wikimedia.org>
> Subject: [Wikitech-l] Wednesday: Technical Advice IRC Meeting
> Message-ID:
> <CA+deL=3NGZz2ky9mdDM+Xcj-aHn652tEhxnP=
> x5JoAakoYFCWg(a)mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Sorry for cross-posting!
>
> Reminder: Technical Advice IRC meeting again **Wednesday 3-4 pm UTC** on
> #wikimedia-tech.
>
> The Technical Advice IRC Meeting (TAIM) is a weekly support event for
> volunteer developers. Every Wednesday, two full-time developers are
> available to help you with all your questions about Mediawiki, gadgets,
> tools and more! 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
>
> Hope to see you there!
>
> Michi (for the Technical Advice IRC Meeting crew)
>
>
> --
> 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.
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 07 Aug 2018 19:28:16 -0400
> From: MZMcBride <z(a)mzmcbride.com>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: [Wikitech-l] My Phabricator account has been disabled
> Message-ID: <D78FA2D0.F1708%z(a)mzmcbride.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Hi.
>
> My Phabricator account has been disabled. I don't seem to have any e-mail
> about this action, so I'm mostly just curious who did it and why. If
> there's a log entry somewhere, that would be nice, but I don't know how
> transparent Phabricator or its admins are. I suppose it would also be nice
> to know if the person ever plans on undoing this unexplained disablement.
>
> I have over 56,000 unread e-mails in my "Phabricator" folder, so if I've
> overlooked an explanatory e-mail, please let me know!
>
> In the meantime, I guess I'll just, uhh, log out to view Phabricator.
>
> MZMcBride
>
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 7 Aug 2018 19:17:14 -0500
> From: Mukunda Modell <mmodell(a)wikimedia.org>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] My Phabricator account has been disabled
> Message-ID:
> <
> CABujXRu0cJbzB2aGLrXW6bMgBva8UF4Wa4nvXDEvcLOJ4nKiAQ(a)mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> I think you were a victim of a false-positive with the anti-vandalism tech
> that's been recently deployed in phabricator.
> Unfortunately there isn't a log entry to verify that fact because the
> logging function hasn't been deployed yet.
>
> Regardless, I've re-enabled your account.
>
> I apologize for the inconvenience, I'll make some adjustments to the filter
> to hopefully prevent more false positives.
>
> On Tue, Aug 7, 2018 at 6:28 PM MZMcBride <z(a)mzmcbride.com> wrote:
>
> > Hi.
> >
> > My Phabricator account has been disabled. I don't seem to have any e-mail
> > about this action, so I'm mostly just curious who did it and why. If
> > there's a log entry somewhere, that would be nice, but I don't know how
> > transparent Phabricator or its admins are. I suppose it would also be
> nice
> > to know if the person ever plans on undoing this unexplained disablement.
> >
> > I have over 56,000 unread e-mails in my "Phabricator" folder, so if I've
> > overlooked an explanatory e-mail, please let me know!
> >
> > In the meantime, I guess I'll just, uhh, log out to view Phabricator.
> >
> > MZMcBride
> >
> >
> >
> > _______________________________________________
> > Wikitech-l mailing list
> > Wikitech-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 8 Aug 2018 01:39:23 +0100
> From: Alex Monk <krenair(a)gmail.com>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] My Phabricator account has been disabled
> Message-ID:
> <CALMPGzWPHEHRCk9KJBtdJ-JeDw5POBotxk8=zdBJOSa=
> PmDOBA(a)mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> If there isn't any logging of this stuff how do we know it's your anti
> vandalism bot and not a rogue admin?
>
> On Wed, 8 Aug 2018, 01:17 Mukunda Modell, <mmodell(a)wikimedia.org> wrote:
>
> > I think you were a victim of a false-positive with the anti-vandalism
> tech
> > that's been recently deployed in phabricator.
> > Unfortunately there isn't a log entry to verify that fact because the
> > logging function hasn't been deployed yet.
> >
> > Regardless, I've re-enabled your account.
> >
> > I apologize for the inconvenience, I'll make some adjustments to the
> filter
> > to hopefully prevent more false positives.
> >
> > On Tue, Aug 7, 2018 at 6:28 PM MZMcBride <z(a)mzmcbride.com> wrote:
> >
> > > Hi.
> > >
> > > My Phabricator account has been disabled. I don't seem to have any
> e-mail
> > > about this action, so I'm mostly just curious who did it and why. If
> > > there's a log entry somewhere, that would be nice, but I don't know how
> > > transparent Phabricator or its admins are. I suppose it would also be
> > nice
> > > to know if the person ever plans on undoing this unexplained
> disablement.
> > >
> > > I have over 56,000 unread e-mails in my "Phabricator" folder, so if
> I've
> > > overlooked an explanatory e-mail, please let me know!
> > >
> > > In the meantime, I guess I'll just, uhh, log out to view Phabricator.
> > >
> > > MZMcBride
> > >
> > >
> > >
> > > _______________________________________________
> > > Wikitech-l mailing list
> > > Wikitech-l(a)lists.wikimedia.org
> > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> > _______________________________________________
> > Wikitech-l mailing list
> > Wikitech-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 07 Aug 2018 20:56:14 -0400
> From: MZMcBride <z(a)mzmcbride.com>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] My Phabricator account has been disabled
> Message-ID: <D78FB7B3.F170E%z(a)mzmcbride.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Mukunda Modell wrote:
> >I think you were a victim of a false-positive with the anti-vandalism tech
> >that's been recently deployed in phabricator.
> >Unfortunately there isn't a log entry to verify that fact because the
> >logging function hasn't been deployed yet.
> >
> >Regardless, I've re-enabled your account.
> >
> >I apologize for the inconvenience, I'll make some adjustments to the
> >filter to hopefully prevent more false positives.
>
> Ah, okay. Thank you for the quick reply and remedy! I appreciate it.
>
> MZMcBride
>
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 2 Aug 2018 11:16:59 +0200
> From: Sebastian Hellmann <pr-aksw(a)informatik.uni-leipzig.de>
> To: wikitech-l(a)lists.wikimedia.org
> Subject: [Wikitech-l] SEMANTiCS 2018, Vienna, Sep 10-13, Contribute to
> the Vocarnival & the DBpedia Day
> Message-ID:
> <a4ee28c6-eb46-bf2f-0449-2b67469a4fd6(a)informatik.uni-leipzig.de>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> *# Vocarnival*
>
> The Vocabulary Carnival (Vocarnival) at SEMANTiCS 2018 is a unique
> opportunity for vocabulary publishers to showcase and share their work,
> meet the growing community of vocabulary publishers and users, and build
> useful semantic, technical and social links. The Vocarnival forms part
> of the SEMANTiCS programme with the Carnival Minute Madness and the
> marketplace.
>
> *Which are the expected vocabulary types? *
>
> All types! A very wide vocabulary definition applies to this
> competition, including ontologies, classifications, thesauri, concept
> and metadata schemes, independently of their format, be it RDF or not.
>
> *When is the submission deadline?*
>
> The submission deadline is set for September 3, 2018, 23:30 CET time.
>
> Get familiar with the technical requirements and the presentation format
> for your vocabulary submission. Afterwards, follow the steps below and
> get honored by a special prize if you have one of the best three
> posters. The winners will be announced during the respective Vocarnival
> Session at SEMANTiCS 2018. Please find all information here:
> _https://2018.semantics.cc/vocabulary-carnival_
>
>
> *How to submit your Vocabulary to the Carnival? *
>
> *Step 1:*Make sure your vocabulary is accessible on the Web via a public
> URI.
>
> *Step 2:*Submit your vocabulary here:
> _https://2018.semantics.cc/submit-vocabulary-vocarnival_
>
> *Step 3:*Register to SEMANTiCS 2018: _https://2018.semantics.cc/prices_
>
> *Step 4:*Every poster will be presented in our exhibition area. The
> organising committee will select the best vocabulary poster and
> presentation for the awards.
>
>
> *# DBpedia Day - Call for Participation*
>
> At the beginning of SEMANTiCS 2018, the DBpedia Community will get
> together on the**10th of September for the DBpedia Day. Besides the
> following highlights, we want you to be a part of the day by telling us
> what cool things you do with DBpedia. Submit your proposal in our form:
> _https://goo.gl/forms/ngRWCjgH9ocDCrEb2_!
>
> *Highlights*
>
> - Keynote #1: Dealing with Open Domain Data by Mathieu d’Aquin (NUI Galway)
>
> - Keynote #2: Linked Open Data cloud - act now before it’s too late by
> Javier Fernández García (WU Wien)
>
> - DBpedia Association hour
>
> - DBpedia Chapter Session
>
> *Important Facts*
>
> - Web URL: _http://wiki.dbpedia.org/meetings/Vienna2018_
>
> - When: September 10th, 2018
>
> - Where: Gußhaus Campus of Vienna's Technical University, Gußhausstraße
> 27-29, 1040 Vienna, Austria
>
> - Call for Contribution: Submit your proposal in our form
> _https://goo.gl/forms/ngRWCjgH9ocDCrEb2_
>
> - Attending the DBpedia Community Meeting costs €50 (excl. registration
> fee and VAT). DBpedia members get free admission, please contact your
> nearest DBpedia chapter or the _DBpedia Association_
> <mailto:holze@infai.org>for a promotion code.
>
> /We are looking forward to your contributions and to seeing you at the
> SEMANTiCS in Vienna! /
>
>
>
> ------------------------------
>
> Message: 7
> Date: Wed, 8 Aug 2018 12:08:03 +0200
> From: Amir Ladsgroup <ladsgroup(a)gmail.com>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] My Phabricator account has been disabled
> Message-ID:
> <CA+ttme0ez9Pkj9WZ_6VC4oED9vpNvWyQP-XZQcphP=
> vYXw8Urw(a)mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> I disabled the account and now I disabled it again. It's part of a CoC ban.
> We sent the user an email using the "Email to user" functionality from
> mediawiki.org the moment I enforced the ban.
>
> We rather not to discuss details of cases publicly but I feel this
> clarification is very much needed.
>
> Best
>
> On Wed, Aug 8, 2018 at 2:56 AM MZMcBride <z(a)mzmcbride.com> wrote:
>
> > Mukunda Modell wrote:
> > >I think you were a victim of a false-positive with the anti-vandalism
> tech
> > >that's been recently deployed in phabricator.
> > >Unfortunately there isn't a log entry to verify that fact because the
> > >logging function hasn't been deployed yet.
> > >
> > >Regardless, I've re-enabled your account.
> > >
> > >I apologize for the inconvenience, I'll make some adjustments to the
> > >filter to hopefully prevent more false positives.
> >
> > Ah, okay. Thank you for the quick reply and remedy! I appreciate it.
> >
> > MZMcBride
> >
> >
> >
> > _______________________________________________
> > Wikitech-l mailing list
> > Wikitech-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
> ------------------------------
>
> End of Wikitech-l Digest, Vol 181, Issue 11
> *******************************************
>
Hi folks,
When I go to https://status.wikimedia.org/ I get the following text:
"status.wikimedia.org has been deprecated
The page previously known as status.wikimedia.org has been deprecated,
more information at T199816 and related subtasks.
For user-facing HTTP errors please see frontend traffic dashboard and
related dashboards on Grafana. "
Both https://phabricator.wikimedia.org/T199816 and
https://grafana.wikimedia.org/dashboard/db/frontend-traffic throw the
same "Our servers are currently under maintenance or experiencing a
technical problem. " error (just like every other Wikimedia site). What
is the current place to check if shit is hitting the fan and it's a good
moment to do something else?
Maarten
That was about the other thing, putting Code of Conduct file into every
MediaWiki extension. Wikimedia Phabricator is by design a MediaWiki
development space, so it’s under code of conduct by all definitions.
(Although I must comment that banning a person for a ‘WTF’ type of
comment is really unwarranted, especially when said to Wikimedia
employees as opposed to volunteers.)
Oleg
I’m sorry, but no, even the evidence that Jimmy Wales is a worst human
being on the entire planet Earth wouldn’t make some kinds of language
(like the one you are quoting from) acceptable in a collaborative
environment. Of course, he should apologise, but CoCC doesn’t have any
authority about that, so it’s not reasonable to discuss it in such context.
Please do not derail the conversation about this particular incident by
going on a tangent about unrelated issues or ‘snowflakes’. The problem
here is the repercussions too harsh for the language that is being
quoted, not some general idea that MediaWiki development spaces should
have some kind of rules.
Oleg
On 08/08/2018 17:44, wikitech-l-request(a)lists.wikimedia.org wrote:
> Saying "WTF" is by default acceptable for all projects unless the WMF
> board agrees a resolution and enforces it on its own board members, as
> well as volunteers and WMF employees. If anyone is blocked or banned
> under the Technical CoC for using similar language which has been
> published by WMF board members, this should be grounds for a
> successful appeal unless and until the same standards are seen to be
> applied to WMF board members along with the same block and ban
> actions.
>
> Just in case readers here missed the precedent set in 2016, Wales has
> never retracted nor apologised for writing on the English Wikipedia
> that a statement by Heilman was "utter fucking bullshit". Both parties
> were Wikimedia Foundation board members at the time, and are board
> members now.[1][2]
>
> Links
> 1. https://en.wikipedia.org/w/index.php?title=User_talk:Jimbo_Wales&diff=70167…
> 2. https://motherboard.vice.com/en_us/article/8q8gvg/wikipedias-secret-google-…
>
> Fae