SOURCEFORGE.NET UPDATE - 2006-02-24 EDITION (read all site news here)
Removal of Disused Projects: Autopurge service relaunched
(Note: the following is reprinted from the Sourceforge.net site newsletter of Feb. 24, 2006)
Over the past few years,
we've received a number of requests from site users to purge defunct projects -- as to reduce dilution of the site by projects that never produced software, and to free namespace consumed by these projects. In the
past, SourceForge.net had deployed a basic "Autopurge" system to clear out these defunct projects.
In early 2006, based on substantial effort to improve the maintainability of the purge code and
improve to the uptime of the statistics system, the Autopurge system has been relaunched.
How does Autopurge work?
Projects are considered for purge eligibility based on project age (the newest
projects on the site are given a chance to develop), project activity (the most active projects on the site are left in place to continue developing), and the presence of file releases in a project. Projects which
are determined to be "inactive" based on these criteria are placed in the Autopurge queue.
Once queued, project administrators are provided notice by email, on two occasions, of the impending purge
and are given the opportunity to opt-out. If the project is never opted-out of the purge, data is backed-up and archived for at least a six-month window before being fully removed.
Since relaunch earlier
this year, we have completed two test runs (against the production SourceForge.net site, closely monitored and controlled) of the Autopurge system to ensure proper operation. Over the next few months, we'll be
working through the entire project base to help improve the signal-to-noise ratio on the site and clear project namespace of defunct projects.
We appreciate the feedback that our users have provided in the
past -- cleanup of these defunct and disused projects has certainly been one of the most-requested features for the site.