Launchpad itself

Requesting deletion of team/project I do not own

Asked by dann frazier

I recently got pinged about this decade old project that was created by members of my team at Canonical at the time:
  https://launchpad.net/server-workload-testing

The ping was because it *sounds like* a useful project, when in fact it never got to that point, and time has made the existing content very much obsolete. Today it just serves to waste (human) browsers' time.

This project is owned by https://launchpad.net/~server-workload-testing-team. I asked the admin of that team, Al Stone, if he would be able to delete it - but he no longer has access to his launchpad account. I asked Robie, a non-admin member of that team as well, but he confirmed he doesn't have privs to kill it.

Is there a process by which we can delete that project? And perhaps maybe the team while we're at it? Obviously not a huge priority, just some cleanup that should happen "at some point" :)

Question information

Language:
English Edit question
Status:
Expired
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Jürgen Gmach (jugmac00) said : 		#1

Hey Dann,

While I have not encountered this constellation before, I think the best way forward would be for me to get a quick confirmation by Al, then make Robie the admin of the project/group, and then he can delete the related repositories, and finally I can delete the project and Robie the group.

Can you tell me how you contacted Al? Any of the email addresses on his old Launchpad account?

Thanks,
Jürgen

Revision history for this message
Robie Basak (racb) said : 		#2

I can answer for dann before he wakes up. I have the address he used, but as they're not listed publicly I'll send it to you privately.

Revision history for this message
Jürgen Gmach (jugmac00) said : 		#3

Thank you - I wrote an email to Al.

Revision history for this message
Jürgen Gmach (jugmac00) said : 		#4

Al agreed to make Robie admin.

I contacted IS to perform that step:
https://portal.admin.canonical.com/C136159/

Revision history for this message
Jürgen Gmach (jugmac00) said : 		#5

Robie, you are now admin.

Could you please delete the repositories in https://launchpad.net/server-workload-testing ?

I then will delete the project.

Then you can delete the team https://launchpad.net/~server-workload-testing-team and we are done :-)

Revision history for this message
Robie Basak (racb) said : 		#6

https://code.launchpad.net/~server-workload-testing-team/server-workload-testing/trunk/+delete gives me: " This branch cannot be deleted as it has 2 branches sharing revisions."

I got that down from 4 to 2, but don't see what else I can delete. Any advice on finding the shared branch please?

Revision history for this message
dann frazier (dannf) said : 		#7

Thanks for your help @jugmac00 & @racb!

If shared revisions turns out to be an insurmountable issue, I suppose one option might be to just push a commit that deletes all the files and adds a PROJECT-IS-OBSOLETE file at the top or similar.

Revision history for this message
Robie Basak (racb) said : 		#8

Maybe I can just use my new admin powers and add dannf as an admin. Would that be improper? Any objections?

Revision history for this message
Colin Watson (cjwatson) said : 		#9

https://code.launchpad.net/~server-workload-testing-team/server-workload-testing/plugin-allocators and https://code.launchpad.net/~george-kraft/server-workload-testing/openmpi are the stacked branches that still exist. TBH it might be better to just not bother deleting branches in this case; we do that to avoid having storage lying around forever for branches that are no longer accessible, but it isn't worth spending a lot of time on it.

Revision history for this message
Launchpad Janitor (janitor) said : 		#10

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.