Search by property

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

List of results

• Output 5.2 (ARCHIVED)  + (easy installation, update, and deployment of the full technology stack)
• Output 2.3 (ARCHIVED)  + (full featured workflows on mobile form factors)
• Issue:057  + (having multiple systems with different deploy cadence (apps, MW core, services) works fine for greenfield development but increases coordination costs of maintenance)
• Issue:061  + (lack of clarity around new frontend plans (e.g. how will the desktop look and who will maintain it?))
• Issue:060  + (lack of clarity on the status of various projects which have been tagged as RfCs but never had an official decree or discussion)
• Issue:048  + (lack of feature parity and widespread adoption in services means we are forced to maintain both the MediaWiki and the service version)
• Issue:055  + (making MediaWiki less useful for third parties cannibalizes our ability to attract volunteer developers, yet this consideration is routinely ignored)
• Issue:059  + (mismatch between TechCom definition of when an RfC is needed (strategic/cross-cutting/hard to undo) and how some Audiences teams interpret it (no RfC if the technical changes are not large, even if it has a serious strategic impact))
• Issue:062  + (mismatch between how Technology and Readers understands the role of RESTBase)

• Output 1.2  + (modularized MediaWiki)

• Output 1.3  + (modularized RESTBase)
• Output 2.2  + (personalized and non-personalized content can be assembled into a page outside of the MediaWiki application)
• Issue:052  + (replacing Cassandra with ParserCache and moving the changeprop mechanism into MediaWiki would significantly reduce server costs and the functionality would be useful for many third-party extensions)
• Issue:053  + (resourcing of the various interfaces is not commensurate with their actual usage)
• Issue:047  + (services complicate the installation process, both for developers and for third parties)
• Issue:049  + (services result in duplicated infrastructure which results in increased server spending)
• Issue:056  + (to preserve coherence as a software framework, services should extend from MediaWiki (e.g. have a REST router in core then override it with an external service where it makes sense), not live in a parallel dimension)
• Issue:051  + (we should investigate how to better integrate Parsoid with PHP, to reduce system boundaries +1)