CMake:Module Maintainers
From KitwarePublic
Introduction
If you want to add a new module to CMake, then you must volunteer to maintain it, or find someone that will. See the Call for maintainers announcement on the mailing list. This page contains a list of Module maintainer volunteers, and instructions on how to become a maintainer.
Please DO NOT ADD a Bug Tracker entry for a new Module request. Instead, volunteer to become a module maintainer. Module maintainers get direct push access to CMake's next branch in Git.
New Maintainer
Please follow these steps to become a module maintainer:
- Read the Modules/readme.txt file documenting module conventions
- Create a Mantis account on our issue tracker. Use a meaningful name rather than a handle or alias. We need to be able to assign issues to you when they are related to your module.
- Create a CDash account and subscribe to the CMake project to receive notification when your changes may have broken something.
- Subscribe to the CMake Developers Mailing List and introduce yourself and the module
- Read the Git Workflow instructions. See the Publishing section to get Git push access. See the Topic Stage section for a workflow summary.
- Update the list below to advertise yourself as a contributor.
Compatibility
If you are taking over maintenance of an existing module, please ensure that all changes maintain compatibility:
- The set of documented output variables such as XXX_INCLUDE_DIRS must be maintained. If you add new output variables that supersede existing ones please document the old names as for compatibility only but still provide them.
- The set of (un)documented input variables such as XXX_INCLUDE_DIR must be maintained. These variables typically appear as the first argument to commands like find_path which save them in the cache and allow the user to set them on the command line or interactively. Build scripts may set them to convince find modules to pick up the desired location for a package. If you change the way a package is found such that a cache variable is no longer needed, check whether the value is set and use it as a hint for the new approach.
Third-Party Modules
- Here is a list of "repositories" of 3rd party CMake modules, so maintainers can check for already existing modules etc.
- KDE4: http://websvn.kde.org/trunk/KDE/kdelibs/cmake/modules/
- PlPlot: http://plplot.svn.sourceforge.net/viewvc/plplot/trunk/cmake/modules/
- http://cmake-modules.googlecode.com/svn/trunk/Modules/
- OpenSceneGraph http://www.openscenegraph.org/svn/osg/OpenSceneGraph/trunk/CMakeModules/
- OpenSync http://svn.opensync.org/branches/3rd-party-cmake-modules/modules/
- http://github.com/jedbrown/cmake-modules
- http://github.com/mloskot/cmake-modules
List
- NOBODY!!! Please volunteer if you are able and willing. Need new maintainers for these modules:
- Any Find*.cmake module distributed with CMake that is not already listed under a maintainer below.
- Dave Partyka, dave dot partyka at kitware dot com
- Miguel A. Figueroa Villanueva, miguelf at ieee dot org
- Alan W. Irwin, irwin at beluga dot phys dot uvic dot ca
- Ada
- Alexey Ozeritsky, aozeritsky at gmail dot com
- Tim Burrell (tim dot burrell at gmail dot com) (http://www.dsource.org/projects/cmaked)
- D support
- Philip Lowman, philip at yhbt dot com
- Eric Wing ; in the commercial domain at gmail, ewing . public
- Marcel Loose, loose at astron dot nl
- Matt Leotta, matt.leotta at gmail dot com
- Mathieu Malaterre , Mathieu.Malaterre at gmail dot com
- Clinton Stimpson clinton at elemtech dot com
- Petr Gotthard, petr dot gotthard at honeywell dot com
- Will Dicharry, wdicharry at stellarscience dot com
- Kovarththanan Rajaratnam, kovarththanan.rajaratnam at gmail dot com
- James Bigler, nvidia.com - jbigler or jamesbigler - gmail dot com
