2007-04-14 09:53:07 |
Matthew Paul Thomas |
bug |
|
|
added bug |
2007-04-14 09:55:49 |
Matthew Paul Thomas |
description |
Because a small but persistent proportion of newly-registered projects are junk, Launchpad should have an automated mechanism for deleting projects that aren't being used. This would keep the project namespace clean, and improve project search results.
<sabdfl> mpt, kiko: i think we should have a process which checks to see if a product is *used* (bugs, blueprints, packages, branches etc) and if not, mails the registrant saying we will delete in 7 days etc |
Because a small but persistent proportion of newly-registered projects are junk, Launchpad should have an automated mechanism for deleting projects that aren't being used. This would keep the project namespace clean, and improve project search results.
<sabdfl> mpt, kiko: i think we should have a process which checks to see if a product is *used* (bugs, blueprints, packages, branches etc) and if not, mails the registrant saying we will delete in 7 days etc
...
<sabdfl> it should NOT delete ones that are marked reviewed
...
<sabdfl> that way we can scan a list of "will be deleted" and just review-and-approve ones which may be unused but still have nice data
<sabdfl> for example, a decent title and summary, and imagery |
|
2007-04-18 19:35:25 |
Diogo Matsubara |
launchpad: status |
Unconfirmed |
Confirmed |
|
2007-04-18 19:35:25 |
Diogo Matsubara |
launchpad: statusexplanation |
|
|
|
2007-04-23 02:36:10 |
Matthew Paul Thomas |
description |
Because a small but persistent proportion of newly-registered projects are junk, Launchpad should have an automated mechanism for deleting projects that aren't being used. This would keep the project namespace clean, and improve project search results.
<sabdfl> mpt, kiko: i think we should have a process which checks to see if a product is *used* (bugs, blueprints, packages, branches etc) and if not, mails the registrant saying we will delete in 7 days etc
...
<sabdfl> it should NOT delete ones that are marked reviewed
...
<sabdfl> that way we can scan a list of "will be deleted" and just review-and-approve ones which may be unused but still have nice data
<sabdfl> for example, a decent title and summary, and imagery |
Because a small but persistent proportion of newly-registered projects are junk, Launchpad should have an automated mechanism for deleting projects that aren't being used. This would keep the project namespace clean, and improve project search results.
<sabdfl> mpt, kiko: i think we should have a process which checks to see if a product is *used* (bugs, blueprints, packages, branches etc) and if not, mails the registrant saying we will delete in 7 days etc
...
<sabdfl> it should NOT delete ones that are marked reviewed
...
<sabdfl> that way we can scan a list of "will be deleted" and just review-and-approve ones which may be unused but still have nice data
<sabdfl> for example, a decent title and summary, and imagery
When this feature is introduced, it may be wise to begin slowly in case there are unforeseen problems with the process. For example, it could begin by contacting maintainers of unused projects more than 18 months old, then gradually ratchet down to unused projects more than (say) 1 month old. |
|
2007-08-28 14:40:07 |
Joey Stanford |
launchpad: importance |
Undecided |
Medium |
|
2009-03-03 13:46:28 |
Matthew Paul Thomas |
description |
Because a small but persistent proportion of newly-registered projects are junk, Launchpad should have an automated mechanism for deleting projects that aren't being used. This would keep the project namespace clean, and improve project search results.
<sabdfl> mpt, kiko: i think we should have a process which checks to see if a product is *used* (bugs, blueprints, packages, branches etc) and if not, mails the registrant saying we will delete in 7 days etc
...
<sabdfl> it should NOT delete ones that are marked reviewed
...
<sabdfl> that way we can scan a list of "will be deleted" and just review-and-approve ones which may be unused but still have nice data
<sabdfl> for example, a decent title and summary, and imagery
When this feature is introduced, it may be wise to begin slowly in case there are unforeseen problems with the process. For example, it could begin by contacting maintainers of unused projects more than 18 months old, then gradually ratchet down to unused projects more than (say) 1 month old. |
Because a small but persistent proportion of newly-registered projects are junk, Launchpad should have an automated mechanism for deleting projects that aren't being used. This would keep the project namespace clean, and improve project search results.
<sabdfl> mpt, kiko: i think we should have a process which checks to see if a product is *used* (bugs, blueprints, packages, branches etc) and if not, mails the registrant saying we will delete in 7 days etc
...
<sabdfl> it should NOT delete ones that are marked reviewed
...
<sabdfl> that way we can scan a list of "will be deleted" and just review-and-approve ones which may be unused but still have nice data
<sabdfl> for example, a decent title and summary, and imagery
When this feature is introduced, it may be wise to begin slowly in case there are unforeseen problems with the process. For example, it could begin by contacting maintainers of unused projects more than 18 months old, then gradually ratchet down to unused projects more than (say) 1 month old.
See also bug 75604. |
|
2009-10-21 04:36:11 |
Curtis Hovey |
affects |
launchpad-foundations |
launchpad-registry |
|
2009-10-21 04:36:11 |
Curtis Hovey |
launchpad-registry: importance |
Medium |
Low |
|
2010-12-03 05:47:29 |
Curtis Hovey |
tags |
|
projects |
|
2011-02-18 18:36:24 |
Curtis Hovey |
tags |
lp-registry projects |
chr lp-registry projects |
|