VTK/Managing the Development Process: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
Line 59: Line 59:
| '''Java''' || /Wrapping/Java || Chris Harris, Sebastien Jourdain
| '''Java''' || /Wrapping/Java || Chris Harris, Sebastien Jourdain
| '''Web''' || /Web || Chris Harris, Sebastien Jourdain

Revision as of 14:22, 11 March 2014

The text on this page is preliminary.
It is subject to change.

The day-to-day, low-level software development process for VTK has been in place for many years, involving the usual development, dashboard testing, and bug fixing cycle provided by CMake/CTest/CDash. What VTK is missing is more structure around how larger functionality changes are incorporated into VTK. The following describes the process for the high-level (or project level) development of VTK. The goal is to better communicate code changes to the community as they happen, which encourages more community involvement, and document all major functionality changes in VTK.

A project in VTK refers to code changes that

  • involve several developers over a longer time frame (i.e. weeks or months), OR
  • involve the creation of one or more new non-trivial classes, OR
  • affect backwards compatibility, OR
  • otherwise add, remove, or change a significant piece of functionality to VTK.

Process Overview

  1. At the start of each project, groups and individuals with commit access to VTK must first submit development plans to the VTK developers list, giving the name of the project and an abstract of the work, along with a link to a publicly accessible development plan (e.g. VTK wiki page) describing the current system in more detail. This is where discussion of the initial idea may happen by the community, ideally before implementation begins.
  2. New projects are monitored by key individuals (VTK topic leads), who will be responsible for tracking various areas of VTK. When necessary, they will solicit the attention of the Architecture Review Board (ARB). Significant or heavily disputed changes may await ARB approval.
  3. As development continues, the development plan must transition into a document describing implemented functionality.
  4. Individuals who commit code but do not document their plans and implementations will be monitored by the topic leads. They will be warned, and if the behavior continues, their write access may be revoked.

VTK Topic Leads

A set of developers chosen by the ARB will act as topic leads for different sections of VTK. Topic leads are responsible for:

  • Tracking code changes in their topic to see that they use appropriate VTK architecture and are well tested.
  • Tracking new projects related to their topic, and ensuring that appropriate Kitware personnel and/or ARB members are notified of changes.
  • Before each ARB meeting, topic leads must provide a document to the ARB describing recent development in their area, as well as any plans for new development.
Topic Main Subdirectories Topic Lead(s)
Pipeline /Filtering Berk Geveci. Dave DeMarle
Base /Common Berk Geveci, Tim Shed
Rendering /Rendering, /VolumeRendering Marcus Hanwell, Lisa Avila
Generic Filtering /GenericFiltering Will Schroeder, Sebastien Jordain
Widgets /Widgets Will Schroeder
Infovis /Infovis, /Geovis Jeff Baumes, Aashish Chaudhry
Views /Views Jeff Baumes
Parallel /Parallel Ken Moreland, Berk Geveci
Build Process /Utilities, /Wrapping Brad King, David Cole, Marcus Hanwell, Robert Maynard
Visualization Algorithms /Graphics Will Schroeder, Andrew Maclean
Computational Geometry Algorithms /Graphics Andrew Maclean, Will Schroeder
Imaging Algorithms /Imaging Steve Pieper, Bill Lorensen, David Gobbi
Readers and Writers /IO Berk Geveci, Utkarsh Ayachit, Robert Maynard
Qt /GUISupport/Qt Jeff Baumes
Wrapping /Wrapping David Gobbi
Java /Wrapping/Java Chris Harris, Sebastien Jourdain
Web /Web Chris Harris, Sebastien Jourdain