Launchpad itself

Request to create group (super) projects and deletions

Asked by Balazs Ree

"kss" and "kissbooth" are part of an open source development project for making AJAX work without
javascript. http://kssproject.org. Kss is also part of the Plone content
management system http://plone.org. Kss core's code is currently hosted
in codespeak (svn). "kss" is meant for the core development and "kissbooth" targets
addon components and access by a wider community.

We will have lots of python packages (eggs) released separately, therefore we find that project groups would
be appropriate in both case of "kss" and "kissbooth".

Therefore we would like to ask for the following changes:

1). Please make "kss" project to a project group (super project), or delete and recreate.

    It is owned by Godefroid Chapelle (gotcha), please keep him as owner. The rest
    of the objects are owned by myself.
    There are blueprints in this project but I have them backed up so I can recreate them
    without a problem.

2). Please make "kissbooth" project a super project as well.

3) The "~kss" people group is currently registered by someone. Is it in use? If it can be retired, could we reclaim it?
    Only in case if it is possible and not a problem.

1) Please delete project "ksscore", I created it by mistake.

2) Please delete project "kissground", I created it by a mistake

Thanks for your help in advance.
Finally, thanks for providing this excellent web service.

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Christian Reis (kiko) said : 		#1

The best way to do this would be to:

  a) transmute kss and kissbooth to be projects that you will be creating under the project groups
  b) rename them and create the relevant project groups

Can you give some examples of projects that would be registered under each project group?

Revision history for this message
Balazs Ree (ree) said : 		#2

I agree. They should be renamed something like kss-old and kissbooth-old, then
groups created as "kss" and "kissbooth".
Then "-old" groups can be deleted at a later point after resources reassigned to the
newly created groups.

Project names should, imo, follow the python package (egg) names.

Examples for projects in "kss" would be:

kss.core
kss.base
kss.zope
kss.pylons
kss.django
...

Examples for projects in "kissbooth" are:

kss.plugin.sdnd
kss.plugin.livesearch
kss.eventpush
kss.httpwizard

and so on.

Revision history for this message
Balazs Ree (ree) said : 		#3

Hi Christian,

in case you need more information from me, or if I could take any action myself, please let me know.

I suppose there is nothing of the transformation that I could do myself, and super group creation is admin only, is this correct?

Thanks in advance!

Revision history for this message
Christian Reis (kiko) said : 		#4

Sorry, I've been busy at UDS this week. Let me do this now. Okay, for now I have:

  https://edge.launchpad.net/kss-old
  https://edge.launchpad.net/kissbooth-old

and

  https://edge.launchpad.net/kss/

I was about to create the kissbooth project group, but caught myself thinking that it might be confusing when searching -- and perhaps cause some division of your community traffic and Google rank -- if we had two project groups. Perhaps the single project group could be used for both. If you think that's not an issue I'll go ahead and create it as well.

Revision history for this message
Balazs Ree (ree) said : 		#5

Please do go ahead and create it.

I'd add that at one point if we are totally converted to launchpad and bazaar, you would be right. But still people at the moment think in the svn management terms, so the separation of the project to a "core" and a "wider collective" is useful for us.

Thanks a lot for your help.

Revision history for this message
Christian Reis (kiko) said : 		#6

Done.

Can you help with this problem?

Provide an answer of your own, or ask Balazs Ree for more information if necessary.

To post a message you must log in.