Jump to content

Development process improvement: Difference between revisions

From mediawiki.org
Content deleted Content added
Project justification
Tag: Reverted
m Undid edits by 24.116.45.7 (talk) to last version by Baris6161TURK
 
Line 2: Line 2:
{{Wikimedia engineering project information
{{Wikimedia engineering project information
| name = Engineering processes improvement
| name = Engineering processes improvement
| group
| group =
| start = 2024
| start = 2010-06
| end = 2014-02
|
| description = Increase transparency and effectiveness of Wikimedia Foundation's engineering efforts
| description = Increase transparency and effectiveness of Wikimedia Foundation's engineering efforts
| lead
| lead =
| membersUser:RobLa|Rob Lanphier User:guillom|Guillaume PaumierUser:Eloquence|Erik Moeller,User:Alolitas|Alolita Sharma[[UserTfinc|Tomasz F Ct Woo
| members = [[User:RobLa|Rob Lanphier]], [[User:guillom|Guillaume Paumier]], [[User:Eloquence|Erik Moeller]], [[User:Alolitas|Alolita Sharma]], [[User:Tfinc|Tomasz Finc]], Ct Woo
previous
| previous =
next
| next =
}}




== Project justification ==

Heading text


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:
Line 23: Line 20:
* Appropriately resourced code review / deployment / release train for both MediaWiki core and extensions
* Appropriately resourced code review / deployment / release train for both MediaWiki core and extensions
* Effective work methodologies for all Wikimedia engineering teams
* Effective work methodologies for all Wikimedia engineering teams
* Selection of appropriate process support tools, idea
* Selection of appropriate process support tools, ideally open source
* Optimized internal and external request tracking and resource allocation

== Current priorities ==

''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 ==

* [[/Pages_organization|Organization of project pages]]
* [[/20% policy|20% policy]]

== Status updates ==

From [[{{FULLPAGENAME}}/status|Status updates]]:

<div style="margin-left:2em;margin-right:2em;">
{{:{{FULLPAGENAME}}/status}}
</div>

== 2014 ==

[[File:Wikimedia development and deployment flowchart.png|thumb]]

=== [[/2014-01-22|2014-01-22]] ===
* [[/2014-01-22/Notes|notes]]
* [[:commons:Category:Wikimedia_Foundation_software_development|photos]] (see those that start with "Dev Deploy Process...")

=== 2011-07-07 ===
* [[Development_process_improvement/7-8_July_2011_Meeting]]

== 2015 ==

* [[Community Engagement (Product)/Collaboration process/Draft]]
* [[Design and development principles]]
* [[WMF product development process]]

== Previous work ==

See [[/Archive]]

[[Category:WMF Projects 2011q2]]
[[Category:WMF Projects 2011q3]]
[[Category:MediaWiki development process]]

Latest revision as of 12:35, 28 September 2024


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).

  • notes
  • photos (see those that start with "Dev Deploy Process...")

2011-07-07

[edit | edit source]

Previous work

[edit | edit source]

See /Archive