Development process improvement: Difference between revisions

Start:	2010-06
End:	2014-02
Team members:	Rob Lanphier, Guillaume Paumier, Erik Moeller, Alolita Sharma, Tomasz Finc, Ct Woo

Browse history interactively

← Older edit

Content deleted Content added

VisualWikitext

Inline

Latest revision as of 12:35, 28 September 2024

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:

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

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

Status updates

From Status updates:

2011-06-14

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

"QuickStart" meeting with ThoughtWorks, see wikitech-l announcement. Meeting Notes (DRAFT).

2014

2014-01-22

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

2011-07-07

Development_process_improvement/7-8_July_2011_Meeting

2015

Previous work

See /Archive

@@ Line 1: / Line 1: @@
+{{Historical}}
-{{ProjectInfobox
+{{Wikimedia engineering project information
-| name=
+| name = Engineering processes improvement
-| summary=
+| group =
-| members=[[User:RobLa|Rob Lanphier]], [[User:Guillom|Guillaume Paumier]], [[User:Alolitas|Alolita Sharma]], [[user:pdhanda|Priyanka Dhanda]]
+| start = 2010-06
+| end = 2014-02
+| description = Increase transparency and effectiveness of Wikimedia Foundation's engineering efforts
+| lead =
+| members = [[User:RobLa|Rob Lanphier]], [[User:guillom|Guillaume Paumier]], [[User:Eloquence|Erik Moeller]], [[User:Alolitas|Alolita Sharma]], [[User:Tfinc|Tomasz Finc]], Ct Woo
+| previous =
+| next =
 }}
 == 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:
-With the Wikimedia Foundation Tech department growing at the pace that it is, we need to figure out ways of communication with each other and the rest of the world about what we're doing, and how we're doing it. The communication mechanisms we come up with should be appropriate for the scale of organization that we are, and facilitate collaboration with community volunteers to both increase the impact of Wikimedia Foundation employees, as well as ensure focus on issues that matter to the community.
+* 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 ==
+''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]]
-== Project deliverables ==
+=== [[/2014-01-22|2014-01-22]] ===
-* Document summarizing the current situation, detailing the requirements, offering recommendations and outlining an implementation plan.
+* [[/2014-01-22/Notes|notes]]
+* [[:commons:Category:Wikimedia_Foundation_software_development|photos]] (see those that start with "Dev Deploy Process...")
-== User requirements ==
+=== 2011-07-07 ===
+* [[Development_process_improvement/7-8_July_2011_Meeting]]
-There are several audiences:
-*  Community - needs to understand what the Wikimedia Foundation is investing in, needs the ability to provide input into ongoing initiatives, and needs the opportunity to identify and volunteer in areas where they are likely to have the greatest impact and assistance from the Wikimedia Foundation.
-*  Wikimedia Foundation employees and management - needs the ability to see the quick summary of how things are going; when intervention is needed and when things are sailing along smoothly.
-== Specifications ==
+== 2015 ==
-== Software design document ==
-== Test plan ==
-== Documentation plan ==
-== User interface design docs ==
-== Schedule ==
+* [[Community Engagement (Product)/Collaboration process/Draft]]
-A couple of different people have been thinking about this over the past few months. There was a formal evaluation process done by Rob Lanphier in May-June 2010.
+* [[Design and development principles]]
+* [[WMF product development process]]
+== Previous work ==
-This was a relatively short process that started back in May, and is nearly complete.  We're currently working on implementing the communication improvements now.
+See [[/Archive]]
-== Task management ==
-(e.g. link to relevant Bugzilla queries)
-== Release management plan ==
-== Community management plan ==
-== Status updates and notes ==
-* [https://wiki.mozilla.org/Bugzilla:Project_Management_with_Bugzilla Summary of discussions] with people at Bugzilla about using Bugzilla for Project Mnagement
-* [[Project:Process_improvement/Notes_08_09_2010|Meeting Notes: August 09, 2010]]
-* [https://bugzilla.wikimedia.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&component=Bugzilla&resolution=LATER&resolution=---&product=Wikimedia Bug list]
-[[Category:WMF Projects 2010q3]]
+[[Category:WMF Projects 2011q2]]
+[[Category:WMF Projects 2011q3]]
+[[Category:MediaWiki development process]]

ToadetteEdit (talk | contribs)