Re: [Wikitech-l] Coolest Tool Award 2019: Call for Nominations

[Srishti Sethi]

Hello everyone,

Sending a reminder that only a few days are left to recommend tools for the
Coolest Tool Award 2019:
https://meta.wikimedia.org/wiki/Coolest_Tool_Award. Nominate
your favorite tools by July 29 :-)

Cheers,
Srishti

*Srishti Sethi*
Developer Advocate
Wikimedia Foundation 



On Tue, Jul 16, 2019 at 3:43 PM Bryan Davis  wrote:

> On Tue, Jul 16, 2019 at 4:32 PM Brian Wolff  wrote:
> >
> > To clarify, does this mean tool in the sense of "tool"server? (Aka
> coolest
> > thing hosted using cloud services) or is it more general including
> gadgets,
> > standalone apps or any other piece of technology in the wikimedia
> ecosystem
> > that's "cool"?
>
> Any Wikimedia related software is eligible. Gadgets, Lua modules, user
> scripts, bots no matter where they normally run, web tools no matter
> where they are hosted, desktop tools, mobile apps, ...
>
> We have a huge ecosystem of things that people build and use to make
> working on the Wikimedia projects easier and the Coolest Tool Academy
> wants to hear about all of them. You could honestly even nominate your
> favorite GNU Linux distribution if you can explain how it makes life
> as a Wikimedian better.
>
> Bryan
> --
> Bryan Davis  Wikimedia Foundation
> [[m:User:BDavis_(WMF)]] Manager, Technical EngagementBoise, ID USA
> irc: bd808v:415.839.6885 x6855
>
> ___
> 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

[Wikitech-l] CI now runs selenium tests from extension/skin

[Antoine Musso]

Hello,

Adam Wight enhanced our MediaWiki test runner (Quibble) so that it now 
detects whether an extension / skins has a 'selenium-test' script 
defined in package.json. If so, for each repositories it will:


   npm install
   npm run selenium-test

The feature has been long awaited, that will lets developers upgrade 
webdriver.io at their own pace and use their preferred framework (mocha 
or cucumber).



Until now, we were running the Selenium tests from mediawiki/core which 
made it next to impossible to upgrade webdriver.io.



The task was: https://phabricator.wikimedia.org/T199116

cheers,

--
Antoine "hashar" Musso


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

[Wikitech-l] Thank you Thursday

[Kunal Mehta]

Hi,

This week I'd like to thank:
* Daimona, bawolff, and sbassett for their work on v2.0 of the
phan-taint-check-plugin, which has been instrumental in catching real
security issues.
* James_F for picking up a lot of CI maintenance
* MatmaRex for seeing through a patch to allow skins to have custom OOUI
themes, 2 years after beginning work on it!

If there's anyone you want to thank or give a shout out to - please do!

-- Legoktm

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

[Wikitech-l] [BREAKING CHANGE] Remove support for 'object' in wgResourceModules

[Krinkle]

TL;DR: The pre-2011 option of setting a ResourceLoaderModule instance in
$wgResourceModules, or calling ResourceLoader->register with an object as
second parameter, will be removed in MediaWiki 1.34.0 (release expected in
Nov 2019). Change these to an array using the 'class' or 'factory' keys
instead. (Examples below.)

This only affects legacy extensions using PHP files to register modules. If
your extension already registers its modules via extension.json, then this
change does not affect you.

---

During the experimental release of ResourceLoader in MediaWiki 1.16 (2010),
modules had to be registered via $wgResourceModules as an object instance
of ResourceLoaderModule.

In MediaWiki 1.17.0 (2011), as part of the first default-on public release
of ResourceLoader, this was replaced with the ability to register a
declarative array instead. [1] This allowed modules to be lazy-instantiated
by ResourceLoader. These arrays can be class-based (this is the default,
using the  'class' option), or closure-based (using the 'factory' key).

This option was removed as part of refactoring to make ResourceLoader
(more) standalone. I did not want to incur the overhead of maintaining it
for another release cycle through deprecation first. It has been
undocumented since before the first non-experimental release of
ResourceLoader in 1.17.0 (it was kept "temporarily" for compat with
1.17alpha at WMF). No known usage was found in Gerrit-hosted extensions,
nor in any of the Codesearch-index repos hosted externally. It also can't
affect extensions using extension.json for module registration (since MW
1.25).

Examples of the needed conversion:

```
# Before (no longer supported)
$wgResourceModules['ext.Foo'] = new MyModuleSubClass();
$wgResourceModules['ext.Bar'] = new MyModuleSubClass( [
  'xyz' => true,
] );
$wgResourceModules['ext.Baz'] = efComposeSomeComplexObject();

# After (PHP)
$wgResourceModules['ext.Foo'] = [ 'class' => MyModuleSubClass::class ];
$wgResourceModules['ext.Bar'] = [ 'class' => MyModuleSubClass::class, 'xyz'
=> true ];
$wgResourceModules['ext.Baz'] = [ 'factory' => 'efComposeSomeComplexObject'
];

# After (JSON, recommended)
"ResourceModules": {
  "ext.Foo": { "class": "MyModuleSubClass" },
  "ext.Bar": { "class": "MyModuleSubClass", "xyz": true },
  "ext.Baz": { "factory": "MyExtHooks::composeSomeComplexObject" }
```

-- Timo

[0] https://phabricator.wikimedia.org/T222637
[1]
https://gerrit.wikimedia.org/g/mediawiki/core/+/dac5084f6d61b6c45bfae491a2b91d96f61ad778
 - https://github.com/wikimedia/mediawiki/commit/dac5084f6d
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Blubber v0.8.0/blubber.yaml update

[Tyler Cipriani]

Hi all!

CAVEAT EMPTOR: If you don't use the Deployment Pipeline[0] or Blubber[1] 
then this email may mean nothing to you.


A new version of Blubber has been released -- v0.8.0[2].

The main change is that we've eliminated the "artifacts" command for use 
in multistage builds. The details of this change are available in the 
Blubber User Guide[3].


I've created patches that preserve the current functionality of Blubber 
for the Deployment Pipeline and tagged all of them "blubber-v4" in 
Gerrit[4].


Thanks!
-- Tyler

[0]. 
[1]. 
[2].  
[3].  
[4]. 


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