Plone project setup needs an overhaul

Over 18 months ago, I tried to register the Plone (http://plone.org) project with Rosetta to allow the Plone translators to translate the application using Rosetta.

There have been various bugs and missing features which ultimately prevented us from completing this setup. Now I would like to give this a second try with the new Launchpad Translations :)

In order to have a working setup it would be most helpful if the already registered project and products could be removed again, especially as those haven't been used in all those years. My goal is to start from a clean state, so we don't confuse anyone that tries to use the system later on.

From my perspective the following things would need to happen:

- Completely remove all of the following products / projects including all releases/pot/po files:

Plone (https://launchpad.net/plone)
Archetypes (https://launchpad.net/archetypes)
AT Content Types (https://launchpad.net/atcontenttypes)
AT Reference Browser Widget (https://launchpad.net/atreferencebrowserwidget)
Plone (https://launchpad.net/cmfplone)
Lingua Plone (https://launchpad.net/linguaplone)
Plone Language Tool (https://launchpad.net/plonelanguagetool)

- Setup a new product at https://launchpad.net/plone which is named Plone and make the Plone team (https://launchpad.net/~plone) the owner of the product.

- Make the Plone team the owner of the "The Plone translators" translation group, so we can add new members to it ourselves.

- Import the plonefrontpage pot file from http://svn.plone.org/svn/collective/PloneTranslations/trunk/locales/plonefrontpage.pot

After those things have happened I can import the po files for this template myself (at least if the permission model is still the same as it was one and a half years ago).

As we still use some non-standard Gettext techniques automatic import from SVN probably won't work as desired and I need to do some manual work before importing the po files (for example we still use 'no' as the language code for Norwegian Bokmal and not 'nb', and have our own way of using explicit message ids which is not compatible with the msgctxt syntax).

If this shouldn't be the right channel for this kind of questions, please point me to the right direction :)

Thx a lot for your wonderful software / community,

Hanno