1. Summary
  2. Files
  3. Support
  4. Report Spam
  5. Create account
  6. Log in

Changes between Version 4 and Version 5 of Removing a project

01/27/09 18:07:00 (5 years ago)
moorman (IP:



  • Removing a project

    v4 v5  
    33= Removing a Project = 
    4 Upon request by project administrator, !SourceForge.net staff will make several considerations before removing a project from the site. 
    5      * If a project has not yet produced file releases, and no other project materials seem to hold value for the Open Source community, the project will be removed. 
    6      * If a project has produced file releases or other important material, removal will be considered by !SourceForge.net staff based on the following criteria:   
    7           * Legal: Legal justification, such as DMCA violation, trademark infringement or Terms of Service abuse. 
    8           * Merge: Project has merged with another Open Source project on !SourceForge.net and all project materials (CVS, mailing list archives, file releases) have been transferred to that new project. 
    9           * Source Availability: Lack of source code availability or other license term problems with existing file releases. 
     5At [wiki:"What is SourceForge.net?" SourceForge.net], we feel a commitment to ensuring the long-term availability of the Open Source code released by the projects we host.  We will weigh requests for project removal against the community value of leaving the project intact. 
     7When we receive a [wiki:"Contact us" request for project removal], we consider the following: 
     8 * Has the project released files? If not, we will honor the removal request. 
     9 * Does the request include legal justification, such as mention of a DMCA violation, trademark infringement or Terms of Service abuse problem related to the project?  If it does, we consider this on a case-by-case basis. 
     10 * Has the project merged with another project on !SourceForge.net?  If the project has been merged and all project materials ([wiki:"What is Source Code Management?" CVS/Subversion] repository data, mailing lists, file releases) have been moved to the new project, we'll honor the removal request. 
     11 * Projects which have moved to another hosting provider are typically retained at !SourceForge.net (though you can make a note on the project web site and project summary page directing users to the new home) for sake of retaining materials of historical value. 
    1113= Alternatives to Project Removal = 
    1215Orphaning and relocation are two ways to leave the data intact on a !SourceForge.net project while gaining some of the benefits of project removal. Our goal is to generally leave projects intact on !SourceForge.net even if the original development team no longer wishes to continue development or support. Options are available to project administrators to tag the project as inactive (Orphaning the project) or to provide notification of a new development location (Relocating the project). These options are listed on the "Removal" section of the Project Admin pages. 
    1619Takeover of existing, inactive projects will be considered by !SourceForge.net staff. To submit a Takeover Request, follow the [http://sourceforge.net/register/ project registration] process and specify a UNIX name matching that of the project you wish to take over. These requests are considered carefully; we are careful to provide prior notice to the project administrator before processing takeover requests. Requests for project takeover are typically completed within two-to-three weeks from time of submission. 
     21= Getting Help = 
     23 * [wiki:"Support"] 
     24 * [wiki:"Request an enhancement"] 
     27''Initial draft finished 2009-01-27''