Difference between revisions of "Project Retiring Process"
Jump to navigation
Jump to search
(New page: = Document Status = '''IncCom Document Number''': X '''Version''': 0.1 '''Status''': draft = Purpose = Eventually, some OSGeo projects will reach their end-of-life. This is often a go...) |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Document Status = | = Document Status = | ||
| − | ''' | + | '''Version''': 1.0 |
| − | ''' | + | '''Status''': Approved |
| − | ''' | + | '''Last Edited:''' March 21, 2010 |
= Purpose = | = Purpose = | ||
| Line 15: | Line 15: | ||
== Retiring Steps == | == Retiring Steps == | ||
| + | # 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 [http://communitymapbuilder.org/display/MAP/EndOfLife Example]. | # Announce the project's retirement to relevant email lists and news sources. Here is an [http://communitymapbuilder.org/display/MAP/EndOfLife Example]. | ||
| − | ## Announce on project's main web page. | + | ## Announce on project's main web page, ensuring it is obvious to future visitors that the project has retired. |
## Announce to project announcement, developer and user email lists. | ## Announce to project announcement, developer and user email lists. | ||
## Announce to [http://lists.mapserverfoundation.org/mailman/listinfo/discuss OSGeo Discuss]. | ## Announce to [http://lists.mapserverfoundation.org/mailman/listinfo/discuss OSGeo Discuss]. | ||
## Announce to [http://www.osgeo.org/content/news/submit_news.html OSGeo News]. | ## Announce to [http://www.osgeo.org/content/news/submit_news.html OSGeo News]. | ||
| − | # Move the project's status to "retired". | + | # 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. [http://trac.osgeo.org/osgeo/ticket/322 Example]. | # 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. [http://trac.osgeo.org/osgeo/ticket/322 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. | ||
[[Category:Incubation]] | [[Category:Incubation]] | ||
Latest revision as of 02:55, 8 October 2010
Document Status
Version: 1.0
Status: Approved
Last Edited: March 21, 2010
Purpose
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.
Retiring Steps
- 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.
- Announce on project's main web page, ensuring it is obvious to future visitors that the project has retired.
- Announce to project announcement, developer and user email lists.
- Announce to OSGeo Discuss.
- Announce to OSGeo News.
- 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.