Re: [Wikitech-l] MediaWiki Language Extension Bundle 2017.01 release

On Wed, Jan 25, 2017 at 7:47 PM, Kartik Mistry wrote: > I would like to announce the release of MediaWiki Language Extension > Bundle 2017.01. This bundle is The bundle is compatible with MediaWiki > 1.26 and 1.27 or above and requires PHP 5.5.9 or above. Correction:

Re: [Wikitech-l] [Wikitech-ambassadors] Developer Wishlist Survey: propose your ideas

Remember, the deadline for proposing developer wishes is TODAY, January 31 at 23:59 UTC . The Developer Wishlist voting phase is planned to start next Monday, February 6.

Re: [Wikitech-l] MVVM/Single-State solution for our UIs?

This discussion seems exactly what we have a Frontend Standards group for: https://www.mediawiki.org/wiki/Front-end_standards_group https://phabricator.wikimedia.org/project/profile/1616/ DJ On Mon, Jan 30, 2017 at 2:57 PM, Jan Dittrich wrote: > Hello Wikitext-l, > >

Re: [Wikitech-l] MVVM/Single-State solution for our UIs?

I think at this point Mediawiki's frontend stack and its dependencies on RL and supporting user gadgets don't lend itself well to frameworks like React or Vue. With regards to moving away from jQuery UI your path of least resistance inside MediaWiki feels like it might be to use a library such as

[Wikitech-l] Weigh in on whether to finalize "Committee" section of Code of Conduct

Please comment on whether to approve the "Creation and renewal of the Committee" section of the draft Code of conduct for technical spaces. The draft text is at https://www.mediawiki.org/w/index.php?title=Code_of_Conduct/Draft=2374387#Creation_and_renewal_of_the_Committee . You can comment

[Wikitech-l] Request for Comment: TemplateStyles

Hi all, we are seeking input on the best way to enable CSS styling in wiki templates. There are some architecture decisions to be made about the storage, parsing and delivery to the client; we would appreciate insights from people experienced with the MediaWiki parser, Parsoid, VisualEditor and

Re: [Wikitech-l] Account creation on Phabricator currently restricted

On Mon, Jan 30, 2017 at 7:16 PM Chad wrote: > Hi, > > Due to a current vandalism/spam threat, I've enabled administrator approval > of all new accounts. Hopefully this won't have to stay enabled long. > > Will update when it's turned back off. > > Forgot to mention,

[Wikitech-l] Phabricator monthly statistics - 2017-01

Hi Community Metrics team, This is your automatic monthly Phabricator statistics mail. Accounts created in (2017-01): 275 Active users (any activity) in (2017-01): 893 Task authors in (2017-01): 492 Users who have closed tasks in (2017-01): 256 Projects which had at least one task moved from

Re: [Wikitech-l] MVVM/Single-State solution for our UIs?

Hi Jan, Regardless of UI framework, for state management I'd strongly recommend using redux , and after the fact pair it with whatever UI framework you prefer. Here are some of the reasons for using it: - Very popular and widely used - Excellent documentation (see

Re: [Wikitech-l] MVVM/Single-State solution for our UIs?

Certainly a topic for the front-end standards group, but to give my two cents: Many of these new JS libraries, such as React, have some very heavy dependancies. React requires JSX which needs to be transpiled into JS, ES6 Class syntax which needs to be transpiled into ES5, which requires Babel

[Wikitech-l] Proposal: Make $wgRawHTML not apply to system messages

Most of the time we assume that writing code like: wfMessage( 'foo' )->params( $this->getRequest()->getVal( 'bar' ) )->parse(); is totally safe. However, in a wiki with $wgRawHTML = true; this code would be an XSS. I've looked through core, and couldn't find any examples of using unsanitized