Property:Description
From atwg
0
We need a build system that supports pre-compilation of assets (JS, CSS, templates) during integration rather than immediately prior to delivery in order to support modern tooling. +
We need a system for defining and running A/B tests that run in isolation from those defined by other teams and that don't require source code edits to initiate. +
We need a system for capturing analytics events that doesn't require synchronisation with Analytics Engineering. (see also: https://wikitech.wikimedia.org/wiki/User:Ottomata/Stream_Data_Platform) +
It should be possible to define and render UI components on the client and server without expertise of two distinct languages and stacks. +
We need to maintain a services stack that is independent of mediawiki to deliver data that is not mediawiki related +
Too many Readers technical and product initiatives (e.g., the native apps, marvin, MCS to some extent) do not have much (or any) Technology department buy-in. +
In turn, there's an increasing (and unfortunate) tendency for some product teams to self-isolate. +
We don't have any consensus on whether it's valid or valuable for WMF to build user-facing products that are not MediaWiki +
Certain longstanding MediaWiki technical guildelines (that it run in a shared hosting environment, that it not require JavaScript) are too conservative and are seriously impeding modernization effort +
Investment in native device products has a questionable return on investment vs a single responsive, progressively enhanced, device and vendor agnostic web experience +
We need consistent localization practices, well-integrated with translatewiki and our other language infrastructure +
We need to erode the hard barriers between template, lua module, gadget, extension, skin, and core code to make it easier to develop and deploy code written by the community +
We need to reduce our dependence on WMF-proprietary wikitext and allow non-WMF wikis to use whatever markup they prefer (this is a controversial opinion, I know) +
If we are investing time in native apps, non-WMF users should be able/encouraged to customize & use those apps as well. We need community participation in all of our code bases. +
Third-parties should be able to reference and use Wikidata in the same way they can reference and use Commons +
We need a better "innovation" process that lets teams create MVPs of disruptive products (ie, the mobile app experience, services, new skins, machine learning, etc) without creating long-lived splits and silos +
We need a larger more independent community of developers (currently 78% commits over past two years from WMF/WMF-DE; compared to eg 10% employee committs for Automattic) +
