Automatically warn about, then delete, unused projects

Bug #106501 reported by Matthew Paul Thomas
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug 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.

See also bug 75604.

description: updated
Changed in launchpad:
status: Unconfirmed → Confirmed
description: updated
Revision history for this message
David Allouche (ddaa) wrote :

I agree with Mark. Just to point out I do not always disagree.

Revision history for this message
Christian Reis (kiko) wrote :

Okay. To make progress here I'd like to see a study into what constitutes an "unused project". Does it only cover projects which were registered and then never touched again (so they'd have a product and a productseries and nothing else) or does it cover projects which were registered, had specs and bugs created, and then nothing else happened to them? The former picks up a large number of cases (maybe 60% of bogus projects) but it's often the case that somebody will create associated objects to test the project with -- and there you have something which isn't auto-deleted. Should we take care of this manually as we are doing today?

And, to be clear, are we saying DELETE projects, or just mark them as inactive?

Revision history for this message
Joey Stanford (joey) wrote :

Setting this to medium due to the manual nature of the cleanup work that is happening today and the fact that it's not the best use of the resources that have authority to do the cleaning. I could be convinced that this is really a high priority but definitely not a low one.

Changed in launchpad:
importance: Undecided → Medium
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

I think that if a project has artifacts (bug reports, translations, etc), it is less likely that a month's inactivity means it is abandoned for good. For artifact-less projects, we may end up with something like: friendly query after two weeks, warning after six weeks, deletion after two months. For projects with artifacts we may end up with something like: friendly query after six months, warning after 17 months, deletion after 18 months. But what the exact periods should be, and how similar they should be, I think we can learn only by slowly ratcheting down as I described in the original report.

As for deletion vs. deactivation, part (though not all) of the point of doing this at all would be to free up the project IDs for more worthy projects. We could rename such projects to projectid-deleted, or we could actually delete them.

Revision history for this message
Weldon Whipple (weldon) wrote :

I would be in favor of adding a delete command to allow owners of projects to delete them themselves. Earlier this week I created a junk project (which can stay around find), followed by 5 (!!!) other projects, as I kept vascillating about what to call them/it. Now I have 5 "real" projects that are really junk projects. I'm not quite sure how to get rid of them. AFAICT, no one has tried to get a branch from them.

When I search on how to delete projects, all I see lots of posts of someone asking someone else how to delete projects, with a response a bit later from some administrator who has deleted the project.

I realize that sometimes projects might be deleted maliciously (by a disgruntled team member). Maybe you could have something akin to CVS's attic directory where no longer needed projects are kept.

I would also like a way to delete individual files from projects. (Maybe that already exists??)

description: updated
Curtis Hovey (sinzui)
affects: launchpad-foundations → launchpad-registry
Changed in launchpad-registry:
importance: Medium → Low
Curtis Hovey (sinzui)
tags: added: projects
Curtis Hovey (sinzui)
tags: added: chr
Revision history for this message
GAUTAM (gautamkumarvashisht) wrote :

Please delete my project "Coditor". I accidently made it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.