Development process improvement: Difference between revisions
Content deleted Content added
→Project justification: Italic text Tags: Reverted Visual edit: Switched |
ToadetteEdit (talk | contribs) m Undid edits by 24.116.45.7 (talk) to last version by Baris6161TURK Tags: Undo SWViewer [1.6] |
||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{ |
{{Historical}} |
||
{{Wikimedia engineering project information |
{{Wikimedia engineering project information |
||
| name = Engineering processes improvement |
| name = Engineering processes improvement |
||
| Line 13: | Line 13: | ||
== Project justification == |
|||
The 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: |
The 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: |
||
Latest revision as of 12:35, 28 September 2024
 | 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
[edit | edit source]The 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
[edit | edit source]Draft 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
[edit | edit source]Status updates
[edit | edit source]From Status updates:
2011-06-14
[edit | edit source]Alolita, 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 | edit source]"QuickStart" meeting with ThoughtWorks, see wikitech-l announcement. Meeting Notes (DRAFT).
2014
[edit | edit source]
2011-07-07
[edit | edit source]2015
[edit | edit source]- Community Engagement (Product)/Collaboration process/Draft
- Design and development principles
- WMF product development process
Previous work
[edit | edit source]See /Archive