Search by property
From platformevolution
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
- Milestone 1.2.2 + (Milestone 1.2.2: Design MediaWiki REST API)
- Milestone 1.3.1 + (Milestone 1.3.1: Refactor Parsoid to support porting)
- Milestone 1.3.2 + (Milestone 1.3.2: Prototype PHP implementation of Parsoid)
- Milestone 1.3.3 + (Milestone 1.3.3: Test PHP implementation of Parsoid)
- Milestone 2.1.1 + (Milestone 2.1.1: Make REST Routing possible in MediaWiki)
- Milestone 2.1.2 + (Milestone 2.1.2: Begin development of one REST API)
- Milestone 2.2.1 + (Milestone 2.2.1: Refactor the RESTBase stack into logical components)
- Milestone 2.2.2 + (Milestone 2.2.2: Create a multi-purpose key/value storage component)
- Milestone 2.3.1 + (Milestone 2.3.1: Define an API that can serve use cases and be plugged into MediaWiki)
- Milestone 2.3.2 + (Milestone 2.3.2: Deploy the session service to production)
- Milestone 2.4.1 + (Milestone 2.4.1: Prototype page assembly)
- Milestone 2.4.2 + (Milestone 2.4.2: Deliver page assembly capability)
- Milestone 2.5.1 + (Milestone 2.5.1: Begin development)
- Milestone 2.8.1 + (Milestone 2.8.1: Adopt OOUI on prominent special pages)
- Outcome 1 + (Outcome 1: Engineers can more easily scale, maintain and test Wikimedia projects due to improved architecture and modularization of the technology stack)
- Outcome 1 + (Outcome 1: Engineers have a clear understanding of our technology stack and the plan to better scale, maintain and test it)
- Outcome 2 + (Outcome 2: Engineers are able to access more functionality of the stack using well encapsulated components and well defined APIs)
- Outcome 2 + (Outcome 2: Users across all languages, accessibility and usability spectrums can access more of the functionality of Wikimedia projects across more interfaces, devices and form factors)
- Outcome 3 + (Outcome 3: Engineers are more effectively onboarded using new and improved documentation that is clear, complete, and cohesive)
- Outcome 3 + (Outcome 3: Engineers better understand our current architecture and coding standards and where to find them)
- Output 1.1 + (Output 1.1: Architecture Spec for the WMF technology stack)
- Output 1.2 + (Output 1.2: MediaWiki REST API Design)
- Output 1.3 + (Output 1.3: Parser Unification Plan)
- Output 2.1 + (Output 2.1: MediaWiki REST API Infrastructure)
- Output 2.2 + (Output 2.2: Modularized RESTBase)
- Output 2.3 + (Output 2.3: Session Management system)
- Output 2.4 + (Output 2.4: Personalized and non-personalized content can be assembled into a page outside of the MediaWiki application)
- Output 2.5 + (Output 2.5: Initiation of Parser Unification)
- Output 2.6 + (Output 2.6: TBD Refactoring Output (Scope pending architecture - potentially: Use Service Container throughout MediaWiki Core))
- Output 2.7 + (Output 2.7: Refactor presentation layer away from business logic code in MediaWiki)
- Output 2.8 + (Output 2.8: Improved OOUI Library)
- Output 3.1 + (Output 3.1: Wikimedia developer documentation portal)
- Output 3.2 + (Output 3.2: Architecture pages on developer portal)
- Output 3.3 + (Output 3.3: Coding standards pages on developer portal)
- Output 3.4 + (Output 3.4: Wikimedia Style Guide Version 2)
