Output:5.1: Difference between revisions

From atwg
m (Ccicalese moved page Output:001 to Output 5.1 (ARCHIVED) without leaving a redirect)
No edit summary
 
Line 1: Line 1:
{{Output
{{Output
|Description=easy installation, update, and deployment of MediaWiki
|Description=easy installation, update, and deployment of MediaWiki
|Parent Outcome=Outcome:4
|Parent Outcome=Outcome:5
|Archived=Yes
|Archived=Yes
}}
}}

Latest revision as of 09:18, 20 February 2018

Output easy installation, update, and deployment of MediaWiki
Parent Outcome 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
Primary Team
Collaborating Teams
TaskDescriptionDepends On TasksTypeAssociated OutputsPrimary TeamCollaborating TeamsStart YearDurationRisksContingenciesBenefitsAssumptionsImplicationsNotes
Define the default MediaWiki installation (ARCHIVED)Research and define what a "default" 3rd party installation would be to support. This enables us to better define the work to make installations easier for all parties.ResearchOutput 5.1 (ARCHIVED)MediaWiki Platform03These goals need to better stress "increase commonality between WMF and 3rd party installs", rather than treating 3rd party installs as a separate configuration target
Improve installation of default MediaWiki for WMF development, testing and production environments as well as 3rd parties (ARCHIVED)Implement fixes needed to support the default installation on for environments based on the 3rd party and default MediaWiki research tasksResearch 3rd party installations, uses, and contributions (ARCHIVED)Define the default MediaWiki installation (ARCHIVED)DevelopmentOutput 5.1 (ARCHIVED)RelEngBryan Davis, MediaWiki Platform6I don't think we have full consensus on single-process LAMP vs node js helpers etc.