Development process improvement
This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. |
Engineering processes improvement
Increase transparency and effectiveness of Wikimedia Foundation's engineering efforts
|
Project justification
editThe growth of the Wikimedia Foundation's engineering programs and the scale of our ambitions necessitates more systematic thinking about all aspects of engineering process and engineering management. This includes:
- Public documentation of projects, status updates, summary reports, and current resource allocation
- Appropriately resourced code review / deployment / release train for both MediaWiki core and extensions
- Effective work methodologies for all Wikimedia engineering teams
- Selection of appropriate process support tools, ideally open source
- Optimized internal and external request tracking and resource allocation
Current priorities
editDraft for discussion at 6/14 engineering management meeting
- (Lead: All) Allocate appropriate resources to code review / deployment / release process; develop related resource allocation policy
- (Lead: General Engineering) Continue (based on /Pages organization and related pages) standardization of public reporting / status pages, esp. public resource tracking
- (Lead: Features) Integrate Etherpad notetaking into public wiki pages to ensure visibility of progress
- (Lead: Features/Product) Develop documentation on WMF feature development process
- (Lead: General Engineering) Standardize testing frameworks, increase test coverage, and improve test integration into code review process
Working drafts
editStatus updates
editFrom Status updates:
2011-06-14
editAlolita, Erik, Rob, Sumana, Ct, Tomasz, Danese had an initial meeting with ThoughtWorks in which we discussed challenges related to the code review/deployment/release management process and engagement of the broader open source community, primarily to help evaluate a possible engagement on continued process improvements; Erik will follow-up.
2011-07-07 and 2011-07-08
edit"QuickStart" meeting with ThoughtWorks, see wikitech-l announcement. Meeting Notes (DRAFT).
2014
edit2011-07-07
edit2015
editPrevious work
editSee /Archive