Project Retiring Process
Last Edited: March 21, 2010
Eventually, some OSGeo projects will reach their end-of-life. This is often a good thing as new approaches or technologies have developed which reduce the need for the project. When a project retires, it is best to clean up loose ends to make sure outstanding users still have access to the code, and the valuable project history is captured for future researchers.
The purpose of the Project Retiring Process provides guidelines for gracefully retiring OSGeo projects which have reached incubation or graduation status.
- Either the Project's Steering Committee, or OSGeo board (in absence of the former PSC) decide that the project is no longer viable.
- The Project Steering Committee recommends retirement to the OSGeo board, and the board accepts the proposal.
- Announce the project's retirement to relevant email lists and news sources. Here is an Example.
- Move the project's status to "retired". Update all the locations where the project is referenced, as per the Project Mentions page.
- If the domain name of your project has the potential of lapsing, hand over the ownership of your domain to OSGeo by raising a SAC ticket. Example.
- If project infrastructure (like svn and issue tracker) is in threat of lapsing, then move to OSGeo so that history can be retained for legacy support and future research.