This is not being worked on -- the launchpad's maintenance team has years or critical and high bugs to deal with first. Projects are public data in Launchpad, They are user by many communities . No user, even the one listed as the project maintainer has the right to prevent other people from using the project. Deleting a project will break everything that is tied to it, such as project it collaborates with. In short Projects are community things, not personal things.
That said, 55% of all projects registered in Launchpad fail to produce any code that can be used any community. Many users are create projects prematurely, before they have code or before they need to collaborate with other communities (Every user and team has it's own repository for personal branches and can create personal package archives so that arbitrary projects are not created.)
We would like project maintainers to be able to deactivate it if no other community is using it. The project can be reactivated if a user asks for it to be restored. We do not know the exact rules for this. If we did, we would also automatically deactivate inactive projects after 6 months or a year.
Criteria that prevent a project from being deactivated:
* The project provides packages for a distribution.
* The project's branches build into packages archives that non-project contributors subscribed to.
* The project has release files that were downloaded by non-project contributors.
* The project has proprietary data.
Criteria to just deactivate the project:
* The project is less that 30 days old (also a good reason to permit renaming it)
* The project has no branches.
Criteria to consider
* The project's bugs, branches, and blueprints are owned by the maintainer and drivers, there are no translations.
This is not being worked on -- the launchpad's maintenance team has years or critical and high bugs to deal with first. Projects are public data in Launchpad, They are user by many communities . No user, even the one listed as the project maintainer has the right to prevent other people from using the project. Deleting a project will break everything that is tied to it, such as project it collaborates with. In short Projects are community things, not personal things.
That said, 55% of all projects registered in Launchpad fail to produce any code that can be used any community. Many users are create projects prematurely, before they have code or before they need to collaborate with other communities (Every user and team has it's own repository for personal branches and can create personal package archives so that arbitrary projects are not created.)
We would like project maintainers to be able to deactivate it if no other community is using it. The project can be reactivated if a user asks for it to be restored. We do not know the exact rules for this. If we did, we would also automatically deactivate inactive projects after 6 months or a year.
Criteria that prevent a project from being deactivated:
* The project provides packages for a distribution.
* The project's branches build into packages archives that non-project contributors subscribed to.
* The project has release files that were downloaded by non-project contributors.
* The project has proprietary data.
Criteria to just deactivate the project:
* The project is less that 30 days old (also a good reason to permit renaming it)
* The project has no branches.
Criteria to consider
* The project's bugs, branches, and blueprints are owned by the maintainer and drivers, there are no translations.