This site is no longer actively maintained. It exists for historical purposes as an example of Phabricator integration and Lua scripting.

Difference between revisions of "User:Ccicalese/Sandbox"

From cpt
No edit summary
No edit summary
Line 1: Line 1:
{{#ask:[[Project::Epic]]|?-Has subobject|?-Has subobject.CPT Kanban Column|mainlabel=-}}
{{#ask:[[Project::Epic]]|?-Has subobject|?-Has subobject.CPT Column|mainlabel=-}}

Revision as of 16:35, 14 June 2019

-Has subobject"-Has subobject" is a predefined property representing a container construct and is provided by Semantic MediaWiki.CPT Column
T100099: Meeting: Automatic deployment of backend services on beta cluster
T101046: [EPIC] Use MCS as parser for main content in mobile web
T102079: Metrics about the use of the Wikimedia web APIs
T107595: [RFC] Multi-Content Revisions
T108253: Make sure CentralAuth login tokens work with two datacenters
T109461: [EPIC]: Improvements to mobileview API
T111575: Make $wgSessionCacheType and $wgMainStash caches multi-DC ready
T113066: [GOAL] Make Wikipedia more accessible to 2G connections
T113916: Switch ResourceLoader file dependency tracking to MultiDC-friendly backend
T114194: MediaWiki should be able to support multiple parser engines
T114271: Audit *all* datastores to see how DR failover is handled
T114273: Cleanup active-DC based MW config code and make it more robust and easy to change
T114282: Red links via Parsoid
T11890: Reasonably efficient interwiki transclusion
T119641: Split-brain strategy for services that use config managed by etcd
T121470: Central Global Repository for Templates, Lua modules, and Gadgets
T122387: Log multi-DB transaction in MediaWiki
T123328: [GOAL] Lazy load references in mobile skin
T1238: Central Code Repository for code used on wikis (Templates, Lua modules, Gadgets)
T124390: [GOAL] Load images with care
T133523: Decide how to improve parsercache replication, sharding and HA
T135022: [EPIC] Improve print styles in desktop and mobile sites
T135027: MASTER_POS_WAIT() alternative that works cross-DC
T135963: Add support for Content-Security-Policy (CSP) headers in MediaWiki
T137291: Transition all use of EasyTimeline to the Graph extension and decommission it from Wikimedia's servers
T140664: Prepare MediaWiki for API-driven frontend
T145219: [EPIC] Cleanup MobileFormatter and MobileViewAPI where they overlap
T146032: Define and implement a common push notification architecture
T149847: RFC: Use content hash based image / thumb URLs
T150871: [EPIC] (Proposal) Replicate core OCG features and sunset OCG service
T152434: Add method to Revision to check if it was a Revert, and whether an edit was Reverted
T154964: [EPIC] Improve mobile print styles
T156408: Create interface between Skin and MobileFormatter
T157088: [EPIC] Develop a JobQueue backend based on EventBus
T159299: Deprecate and remove $wgUser
T161671: Compacting the revision table
T166010: The Great Namespaceization and Reorg
T166188: Architecture of new rendering backend for Extension:Collection
T166733: Deploy refactored comment storage
T167210: [EPIC] Adding PDF TOC with PDF page numbers to electron
T167246: Refactor "user" & "user_text" fields into "actor" reference table
T167713: [EPIC] MinervaNeue's starter modules should be grouped by page not feature
T169937: Services Q1 2017/18 goal: Begin migrating job queue processing to multi-DC enabled eventbus infrastructure.
T170296: End of July milestone: Begin migrating job queue processing to multi-DC enabled eventbus infrastructure.
T170319: End of August milestone: Begin migrating job queue processing to multi-DC enabled eventbus infrastructure.
T170453: FY2017/18 Program 6: Streamlined Service delivery
T170455: Extract the feed endpoints from PCS into a new wikifeeds service
T170456: FY2017/18 Program 6 - Outcome 2 - Objective 3: Integrated, container-based development environment
T170480: FY2017/18 Program 6 - Outcome 2: Developers are able to develop and test their applications through a unified pipeline towards production deployment.
T170481: FY2017/18 Program 6 - Outcome 2 - Objective 2: Set up a continuous integration and deployment pipeline
... further results