FWIW, I think the Babel bug was waiting for several days for review from
Niklas, the extension owner, who wasn't at wikimania. But the folks who
ended up taking action and doing the revert we're at wikimania -- I think
it's a general matter of lack of communication during wikimania, with folks
Deployments during the week of wikimania are always tough. I'm surprised
we even tried to do that this year.
--scott
On Mon, Jul 23, 2018, 7:23 PM Željko Filipin wrote:
> Hi,
>
> This is the second ever train I am conducting and it has been very
> interesting. I've been told that is not
> Deployments during the week of wikimania are always tough. I'm surprised
> we even tried to do that this year.
There is/was sufficient coverage from both RelEng and SRE so there
wasn't an issue of site outage without available people to respond. IOW,
no one from RelEng nor SRE was attending
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,
Hi,
This is the second ever train I am conducting and it has been very
interesting. I've been told that is not unusual. I have good news and bad
news.
Good news is that some problems are resolved. I would like to thank to
everybody that helped.
Bad news is that train is still blocked. :(
On Mon, Jul 23, 2018, 5:14 AM Jaime Crespo wrote:
> Thanks to all people involved,
>
> I just read about this new video format in the making/released [0].
>
> Of course, I am not asking to support this, as this seems like the future,
> and not the present, but being a complete noob on video
Thanks to all people involved,
I just read about this new video format in the making/released [0].
Of course, I am not asking to support this, as this seems like the future,
and not the present, but being a complete noob on video formats and codecs,
I would like to know if someone more
I'd like to share this relevant blog post[0] by Joaquin for work done
on the Popups extension and upcoming plans for other repos. The post
discusses some of the tradeoffs of Special:JavaScriptTest tests and
Node.js headless QUnit tests.
[0]
Well following the trail of links, leads me to this likely cause:
https://phabricator.wikimedia.org/T180171#4236340
The extension relies on grunt-contrib-qunit which depends on
> phantomjs-prebuild and run qunit tests with PhantomJS. The tests are under
> tests/qunit:
which indirectly is
