Property:Description

Usage

Filter<p>The <a rel="nofollow" class="external text" href="https://www.semantic-mediawiki.org/wiki/Help:Property_page/Filter">search filter</a> allows the inclusion of <a rel="nofollow" class="external text" href="https://www.semantic-mediawiki.org/wiki/Help:Query_expressions">query expressions</a> such as <code>~</code> or <code>!</code>. The selected <a rel="nofollow" class="external text" href="https://www.semantic-mediawiki.org/wiki/Query_engine">query engine</a> might also support case insensitive matching or other short expressions like:</p><ul><li><code>in:</code> result should include the term, e.g. '<code>in:Foo</code>'</li></ul><ul><li><code>not:</code> result should to not include the term, e.g. '<code>not:Bar</code>'</li></ul>

Showing 20 pages using this property.

0

080 +

Our event logging data stores may run out of space if event logging load increases non-linearly +

081 +

We will run out of disk space if there's explosive growth in large files +

082 +

Resourcing of service development is now augmented by front end engineers, which natuarlly gravitate towards JS. Moving to pure PHP is possible, but that would mean a responsibility shift back tot tech for APIs OR a change in hiring strategy for audiences +

083 +

What responsibility do we have for the security of our platform? For protecting the privacy of our users? +

O

Outcome 1 (ARCHIVED) +

Infrastructure for Wikimedia projects can be more easily scaled due to increased modularization, re-use, maintainability, and testability of the technology stack +

Outcome 2 (ARCHIVED) +

More of the full functionality of MediaWiki can be delivered across all interfaces, devices, and form factors while maintaining usability, accessibility, and internationalization standards +

Outcome 3 (ARCHIVED) +

WMF and volunteer engineers and developers are more effectively onboarded using new and improved documentation that is clear, complete, and cohesive +

Outcome 4 (ARCHIVED) +

Session management system is isolated from the rest of the platform +

Outcome 5 (ARCHIVED) +

It is easier to install, update, deploy, and configure our development, testing, and production environments as well as simple third-party instances of our technology stack +

Output 1.1 +

architecture for the flow of control and information from the user down to the database and back +

Output 1.2 +

modularized MediaWiki +

Output 1.3 +

modularized RESTBase +

Output 1.4 +

Unified Parser +

Output 2.1 +

REST API for MediaWiki +

Output 2.2 +

personalized and non-personalized content can be assembled into a page outside of the MediaWiki application +