Reset/Purge project

Asked by Alex

Morning,

Would it be possible to Reset/Purge the project TangoCMS? By this I mean remove all bugs, blueprints, translations etc etc, back to how it would have been if I just created it (though keeping the description etc).

Reason being is that we no longer use Launchpad to manage our project, however would love to use it purely for Translations.

Regards,

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
Christian Reis Edit question
Solved by:
Alex
Solved:
Last query:
Last reply:
Revision history for this message
Curtis Hovey (sinzui) said :
#1

No it is not possible to do this. As Launchpad is community site, the community may still want to track your project in relation to other projects.

I recommend that you update the project to state it does not use launchpad for bugs and blueprints (which I think is done).

If your new bug tracker is public, consider it at https://bugs.launchpad.net/bugs/bugtrackers so that user can import your bug statues. Also not that launchpad can also send bugs and comments to some bugtrackers, so you use the tools of your choice, while remaining connected to the Launchpad community.

Registering your code repo will also let developers track your project and submit their branches to you.

Revision history for this message
Alex (alexc-lp-deactivatedaccount) said :
#2

Ok, well is it possible to remove as much of what has been added as possible? Such as release series, announcements, translations, code?

Revision history for this message
Curtis Hovey (sinzui) said :
#3

We do not have tools to remove these. Again the assumption is that the community may want to track you upstream project, or use launchpad to make translations to submit to your project.

The project can me transfered to the Registry Admins which will make no one the maintainer, and that will prevent users, including yourself, from using the series, milestones, and releases.

Revision history for this message
Alex (alexc-lp-deactivatedaccount) said :
#4

Curtis, thanks for the response. However, the community wouldn't be able to track anything - we don't use Launchpad any more to keep our project management, so anyone looking at tracking what bugs or series are available may as well watch paint dry, as there will be nothing new for them to track.

"or use launchpad to make translations to submit to your project."

This is what we purely now want to use Launchpad for, just to translate our project due to its great feature set and usability.

I find it hard to understand/believe that such a big project (Launchpad) lacks to tools to delete simple things such as bugs (they exist for deleting translations, as I've had them removed before). Sure I can understand the reasoning for not deleting bugs if there are many dependencies between multiple projects and many people watching, though that simply isn't the case with our project.

Keeping it how it is now, and just using the translations part will give false information to users that stumble across our Launchpad project, thinking that the current Blueprints are what is going to be implemented, and the bugs that are there are current (at first glance) and no releases for a fair few months. I don't want to give this dead, false information to our users.

Regards,

Revision history for this message
Curtis Hovey (sinzui) said :
#5

I understand the situation. I agree no-one should be think Launchpad still hosts the project. The Launchpad community tracks many upstream projects so that they can share bugs for example, so it is not common to delete or remove items. Launchpad generally avoids deleting of artifacts because that creates a revisionist history of the activity.

I will assign you request to the launchpad-translation's team. Maybe they can address the situation.

Revision history for this message
Alex (alexc-lp-deactivatedaccount) said :
#6

Thanks for helping out, lets see what the translations team say =).

Revision history for this message
Jeroen T. Vermeulen (jtv) said :
#7

Thankfully Launchpad was designed not just to host projects, but also just to present a unified view of them much like freshmeat and ohloh do. So just the fact that the project is registered in Launchpad shouldn't imply to people that the project is hosted in Launchpad. For Code it's quite normal to have the upstream repository mirrored in Launchpad (free backups :) and as Curtis mentioned Bugs has some mirroring capabilities.

I don't know off the top of my head whether disabling Blueprints and Answers hides the existing entries; if it does, it shouldn't be hard to draw a static-HTML copy using wget and host that on your new site for historic purposes. You could also consider things like setting the status for each blueprint to Obsolete.

As far as translations is concerned:

1. It's all organised by release series, so you'll need at least one series—and depending on your release model you may want to keep all of them. Each release series is a separate world as far as translation is concerned (although translations made in one series will of course show up as suggestions for other series).

2. If for some series you don't want any translation at all, we can disable the templates for those series and they will simply not show up as translatable.

3. If you want to delete translations and start from scratch, we can simply rename and disable each of the old templates, after which you re-upload their latest versions. The old translations will still be in the system and show up as suggestions, but they won't otherwise clutter your UI anymore. If some of the translations were good, you can export those first and re-import them to the new templates.

A final, very radical solution would be to disable and rename the entire project, and start from scratch. Again you can export and re-import any translations you want to keep (including the whole thing as one big tarball) and again, translations from the old project will show up as suggestions for the new one. But this again amounts to revising history, so let's avoid it if we can.

A final tip for Bugs: IIRC there is also an option to provide text that should be shown on the bug-report form. It's meant for specific bug-reporting guidelines, but it could also be used to say "don't file this here!"

Revision history for this message
Alex (alexc-lp-deactivatedaccount) said :
#8

Jeroen,

Thanks for the reply, though I don't think we are getting anywhere with this. I understand that we'll need release series, the issue is with deleting the existing (old and obsolete) series, bug reports and blueprints.

I see no technical reason that things such as Blueprints, Announcements and possibly bugs (bugs I have more of an understanding for) to not be removed.

Is it possible to talk with someone 'higher up' regarding this issue? The only thing I can think of, is de-associating the 'tangocms-project' project, and using that instead of 'tangocms', however we then have duplicate projects (which IMO is even worse and something you'd try to avoid).

Could we also set this back to 'Launchpad its self' instead of for rosetta?

Kind Regards,

Revision history for this message
Alex (alexc-lp-deactivatedaccount) said :
#9

Btw, I've just see the 'whiteboard' at the top mention:

"The user wants the translations removed because the project no longer uses launchpad."

Just to be clear, it is not just translations removed. We'd like all Bug Reports, Blueprints and Series removed, so that we can start again and *just* use Launchpad for Translations.

Revision history for this message
Alex (alexc-lp-deactivatedaccount) said :
#10

Morning,

Is there an update on this?

Regards,

Revision history for this message
Alex (alexc-lp-deactivatedaccount) said :
#11

I guess we'll just have to use this project as is, and clean it up as much as I can.

Thanks anyway,