Launchpad itself

Project group request: Helioviewer

Asked by Keith Hughitt

Hello,

Would it be possible to create a "Helioviewer" project group? Currently, we have several related projects clumped together at http://edge.launchpad.net/helioviewer. Because the projects are very different from one another, however, we would benefit greatly by creating a Project Group page, and several sub-project pages.

An ideal layout would be:

Project group: http://launchpad.net/helioviewer

With the following sub-project pages:

http://launchpad.net/helioviewer.org (or launchpad.net/helioviewer-web if ".org" is not allowed in URL)
http://launchpad.net/jhelioviewer
http://launchpad.net/esajpip
http://launchpad.net/hyperion
http://launchpad.net/firefoxjpeg2000
http://launchpad.net/jp2gen

The team owner already exists and is also named "Helioviewer" (https://edge.launchpad.net/~helioviewer)

All of the projects will initially be licensed under MPL 1.1.

Also, could you please tell me if it would be possible to migrate existing code branches and/or bug-reports to different sub-project pages, once they are created?

Thank you very much for you help!

Sincerely,
V. Keith Hughitt

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
Christian Reis Edit question
Solved by:
Christian Reis
Solved:
Last query:
Last reply:
Whiteboard:
re-assigning to kiko for group request. spm 13-aug.
Revision history for this message
Keith Hughitt (keith-hughitt) said : 		#1

Update:

Could you please include one additional sub-project? The name is "dynamo".

Thank you!
Keith

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

I've created the project group and renamed the existing helioviewer project:

  https://edge.launchpad.net/helioviewer
  https://edge.launchpad.net/helioviewer.org

You can now register the other projects and set them as being part of the helioviewer PG; let me know once that's done!

Revision history for this message
Keith Hughitt (keith-hughitt) said : 		#3

Thanks Christian!

I've created the individual project pages as described above. Is it possible to transfer branches / bug-reports from the http://edge.launchpad.net/helioviewer.org to their respective project pages? Ideally, the branches would be redistributed as:

JHelioviewer:

lp:helioviewer.org/jhv-2.0
lp:helioviewer.org/jhv-1.0
lp:helioviewer.org/jhv-trunk
lp:~andreas-hoelzl-23/helioviewer.org/JHViewerHoelzlA
lp:~aa5/helioviewer.org/JHV
lp:~ludwigschmidt2/helioviewer.org/jhv-ludwig
lp:~picardom/helioviewer.org/jhv-michelle
lp:~b-wamsler/helioviewer.org/jhv-benjamin
lp:~b-wamsler/helioviewer.org/jhv
lp:~ludwigschmidt2/helioviewer.org/jhv
lp:~damadigwe/helioviewer.org/JHV

ESAJPIP:

lp:~jp-garcia-ortiz/helioviewer.org/esa_server

JP2Gen:

lp:helioviewer.org/iproc
lp:~jack-ireland/helioviewer.org/jp2-gen

Hyperion:

lp:~helioviewer/helioviewer.org/hyperion
lp:~helioviewer/helioviewer.org/hyperion-tomcat

FirefoxJPEG2000:

lp:~eschew/helioviewer.org/nphvj

Thanks for all of your help!

Take care,
Keith

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

So for the bug reports it is an easy transfer: visit each bug and just update the project they are registered against. This can also be done via an API script if there are too many to do manually.

For the branches, a recent change in Code has made this impossible to do through the UI (I'll find a bug number for it) but you can just push up new branches and delete the old ones as a workaround for now -- no information will be lost.

Revision history for this message
Keith Hughitt (keith-hughitt) said : 		#5

Thanks Christian Reis, that solved my question.