< Architecture Summit 2014

We have created the straw poll based on the clustering as of 04:56, January 1, 2014‎ -- Please do not change the clustering without consulting either Robla or Diederik

The idea with this grouping is that we want it to be granular enough to consider batches of RFCs on this type of 90 minute agenda:

  • 5 minutes – lightning talk 1
  • 5 minutes – short Q&A 1 (clarifications only)
  • 5 minutes – lightning talk 2
  • 5 minutes – short Q&A 2 (clarifications only)
  • 5 minutes – lightning talk 3
  • 5 minutes – short Q&A 3 (clarifications only)
  • 60 minutes – general discussion

The idea is that a cluster contains RFCs that belong to each other. This means if we discuss RFC A and therefore RFC B needs to be discussed as well then those two RFCs should be in the same cluster. Clusters should also be small, probably not more than 3 or 4 RFCs per cluster.

Backend internals

This category is for clusters that are completely about the server code.

Configuration

Proposals that involve moving away from global variables as the standard way of configuring core and extensions

Debugging

Storage services

Linking

Media backend

Parsing architecture

Proposals that involve big changes to how we think about parsing and wikitext

Parser changes

Smaller changes to parsing

Performance

Refactoring

SQL abstraction

APIs/Interfaces/Protocols

This overall category is for concerns that cut across front-end and backend, and how they interact with each other. This area typically haves an Ops heavy component, because things in this area muck with things like caching infrastructure and load balancers.

CentralNotice

HTML templating

Proposals that involve adding an abstraction layer for server-side and/or client-side HTML skin/user interface generation

Metadata

Interacts with: #Wikidata.

Mobile

Parsed output access

Service-oriented architecture

Thumbnail handling

URLs

Wikidata

Interacts with: #Metadata.

Frontend

Multimedia frontend

  • More general frontend uploading tools (talk)

UI/UX: styling

Software management

This is for proposals that involve code for managing MediaWiki

Backend code modularity frameworks

Proposals that involve organizing our backend code to be more modular

Installation

MediaWiki management

Release process

Software for/from third parties

Functionality

These have end-to-end implications, but are typically more about functionality than architecture.

Crosswiki

Topic cluster, not really for implementation most likely.

General MediaWiki functionality

Page protection and deletion

Security

UI/UX: usability and discoverability

User customization/filterability

Wiki tasks management

This article is issued from Mediawiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.