My project is already registered. How do I take ownership?

Asked by Kern Sibbald

My project, Bacula, is already registered -- less than 30 mins before I was going to do it. I am the Bacula project manger and would like to have ownership of the main Bacula project on Launchpad, but I don't seem to be able to contact the current owner (MaWe22). I am sure his intent is to support the project, and he probably was not and is not aware of my interest in Launchpad, so would like to allow him to continue his contribution and do not want to upset him.

I leave it to you to decide the appropriate procedure, but if I had his email address or some other way to contact him, I will be happy to do it. Since I am totally new to Launchpad, I may be missing some obvious way to contact him.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Kern Sibbald
Solved:
Last query:
Last reply:
Revision history for this message
Tom Haddon (mthaddon) said :
#1

I've sent an email to MaWe22 confirming he's okay with the project being transferred. If we don't hear from him within the next few days, we'll go ahead with the transferral in any case, as it's clearly preferable to have the upstream author be in charge of a project.

Thanks, Tom

Revision history for this message
Kern Sibbald (kern) said :
#2

Thanks. If he has any questions or concerns, he should feel free to contact me
directly: kern at sibbald dot com

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

I've gone ahead and reassigned it; I am not sure why it was created referring to backports and would rather it was updated by Kern to reflect the actual project. I have also approved the SVN import which was pending and verified the links to it. Let me know if you have any further questions!

Revision history for this message
Kern Sibbald (kern) said :
#4

Thanks. Now the hard part begins:
1. Learning more about Launchpad
2. Figuring out how to migrate as much as possible of Bacula to Lanchpad in the smoothest way ...

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

Start at https://launchpad.net/+tour and https://help.launchpad.net/ and let me know of any questions you have after that. You've made a great choice!

Revision history for this message
Kern Sibbald (kern) said :
#6

>
> Christian Reis posted a new comment:
> Start at https://launchpad.net/+tour and https://help.launchpad.net/ and
> let me know of any questions you have after that. You've made a great
> choice!

Thanks for the pointers, I have already taken the tour and read the feature
highlights several days ago, and have been working through the help to refine
things. At this point, it seems that I do indeed need your help for two
things:

1. I would like to re-host my Bacula Mantis bug database on Launchpad. It is
at: bugs.bacula.org, which I believe requires you to import it. I would like
to see it in Launchpad before making the final decision, and must also
discuss it with the developer who is currently hosting it.

2. I would like to re-host my Bacula svn in Launchpad, but it appears from the
documentation that Bazaar can only import the trunk. The problem is that the
svn contains the whole history of Bacula, and I don't want to loose that.
There are quite a number of releases and branches, but I can reduce them down
to about 10 or 15 -- or I have to find some other way of keeping the
history :-( ...

Anyway, any help or pointers (howto documentation) would be appreciated.

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

On Sat, Aug 02, 2008 at 05:12:16PM -0000, Kern Sibbald wrote:
> 1. I would like to re-host my Bacula Mantis bug database on Launchpad. It is
> at: bugs.bacula.org, which I believe requires you to import it. I would like
> to see it in Launchpad before making the final decision, and must also
> discuss it with the developer who is currently hosting it.

Cool. The person to talk to for this topic is Graham, who I'm copying
here in this message. We can run a full import of your bugs and display
it on demo.launchpad.net -- once you are happy and have sign-off on the
migration, we can run it on production.

> 2. I would like to re-host my Bacula svn in Launchpad, but it appears from the
> documentation that Bazaar can only import the trunk. The problem is that the
> svn contains the whole history of Bacula, and I don't want to loose that.
> There are quite a number of releases and branches, but I can reduce them down
> to about 10 or 15 -- or I have to find some other way of keeping the
> history :-( ...

You can do one of three things:

    - Request imports of a few of your key branches. We can do imports
      for legacy branches, the main issue being that they are
      non-mergeable with your trunk branch. If you just want to make
      sure you don't lose history, and have no intention of merging
      between them, that's fine.

    - Do a one-time import of your branches using one of the strategies
      outlined in https://answers.launchpad.net/launchpad-bazaar/+faq/24
      This does imply however that you actually move over to Bazaar from
      that point onwards, since it won't be a continuous import.

    - You may be able to use bzr-svn to mitigate something of the last
      point. I don't know enough about the current status of bzr-svn to
      know if it would give you the semantics you want, but it's worth
      looking into it.

Thanks for the questions! I'm happy to help you (and will reply faster
now that I am back from all this travel..)
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125

Revision history for this message
Graham Ashton (gma) said :
#8

2008/8/11 Christian Robottom Reis <email address hidden>:
> On Sat, Aug 02, 2008 at 05:12:16PM -0000, Kern Sibbald wrote:
>> 1. I would like to re-host my Bacula Mantis bug database on Launchpad.
>
> Cool. The person to talk to for this topic is Graham, who I'm copying
> here in this message.

Hi guys. I think you may have got the wrong Graham there Kiko, unless
I'm an air head and have forgotten something. I've not been active on
Launchpad for quite some time...

Cheers,

Graham

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

On Mon, Aug 11, 2008 at 09:46:06PM +0100, Graham Ashton wrote:
> 2008/8/11 Christian Robottom Reis <email address hidden>:
> > On Sat, Aug 02, 2008 at 05:12:16PM -0000, Kern Sibbald wrote:
> >> 1. I would like to re-host my Bacula Mantis bug database on Launchpad.
> >
> > Cool. The person to talk to for this topic is Graham, who I'm copying
> > here in this message.
>
> Hi guys. I think you may have got the wrong Graham there Kiko, unless
> I'm an air head and have forgotten something. I've not been active on
> Launchpad for quite some time...

Yeah, you're right. :-) Sorry!
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125

Revision history for this message
Kern Sibbald (kern) said :
#10

On Monday 11 August 2008 20:57:21 Christian Reis wrote:
> Your question #40915 on Launchpad itself changed:
> https://answers.launchpad.net/launchpad/+question/40915
>
> Christian Reis posted a new comment:
>
> On Sat, Aug 02, 2008 at 05:12:16PM -0000, Kern Sibbald wrote:
> > 1. I would like to re-host my Bacula Mantis bug database on Launchpad. It
> > is at: bugs.bacula.org, which I believe requires you to import it. I
> > would like to see it in Launchpad before making the final decision, and
> > must also discuss it with the developer who is currently hosting it.
>
> Cool. The person to talk to for this topic is Graham, who I'm copying
> here in this message. We can run a full import of your bugs and display
> it on demo.launchpad.net -- once you are happy and have sign-off on the
> migration, we can run it on production.

Yes, I would like to try that.

>
> > 2. I would like to re-host my Bacula svn in Launchpad, but it appears
> > from the documentation that Bazaar can only import the trunk. The
> > problem is that the svn contains the whole history of Bacula, and I don't
> > want to loose that. There are quite a number of releases and branches,
> > but I can reduce them down to about 10 or 15 -- or I have to find some
> > other way of keeping the history :-( ...
>
> You can do one of three things:
>
> - Request imports of a few of your key branches. We can do imports
> for legacy branches, the main issue being that they are
> non-mergeable with your trunk branch. If you just want to make
> sure you don't lose history, and have no intention of merging
> between them, that's fine.
>
> - Do a one-time import of your branches using one of the strategies
> outlined in https://answers.launchpad.net/launchpad-bazaar/+faq/24
> This does imply however that you actually move over to Bazaar from
> that point onwards, since it won't be a continuous import.
>
> - You may be able to use bzr-svn to mitigate something of the last
> point. I don't know enough about the current status of bzr-svn to
> know if it would give you the semantics you want, but it's worth
> looking into it.

It appears that all your attempts over the last 11 days to import the Bacula
database have failed.

I tried importing it locally here and it failed for similar reasons to those
that I see on Launchpad for the Bacula imports you have initiated. I then
did successfully import it using svn2bzr from a svn dump of our svn. It took
a long time and appears to have worked on the surface, but the import is
rather useless. It is arranged like the following:

  bacula-repo
       branches
       tags
       trunk
          ...

that all looks fine, but when I try to checkout trunk/bacula, I get the
following error.
$ bzr checkout file:///bacula-repo/trunk/bacula bacula
bzr: ERROR: Not a branch: "/bacula-repo/trunk/bacula/".

well, Bacula is not a branch within the svn but it is a repository of the
bacula code. With svn, I can do:

  svn checkout .../trunk xxx
or
  svn checkout .../trunk/bacula xxx

because the trunk contains projects bacula, regress, docs, rescue, ...

So, either the way Bazaar handles things differently, or perhaps I don't
understand it.

===============
I would be quite willing to switch everything over to Launchpad, providing we
can work out the importing problems, and providing we can work out some
critical issues of control of the project, which for the moment are blockers.
I've brought these issues up in a separate Question.

>
> Thanks for the questions! I'm happy to help you (and will reply faster
> now that I am back from all this travel..)

Revision history for this message
Graham Binns (gmb) said :
#11

Hi Kern,

I'm the Graham that's responsible for doing imports of bugs into Launchpad.

The procedure for importing a project's bugs from SourceForge is pretty straightforward:

 1. We grab a copy of the bugs, etc. from Sourceforge.
 2. We do a test import on a development machine to make sure that everything is working correctly and that there are no data in the bug dump that might cause the import to fail.
 3. We do an import of the project on demo.launchpad.net. This is a non-production Launchpad instance, so doing the import there allows you to check that the bugs and users, etc., have been imported properly before we do the import onto a production version of Launchpad.
 4. Once you're happy that the demo import has worked correctly (and we'll repeat steps 1-3 as many times as necessary to get things right), we do the import to production.

I'll get the ball rolling on this within the next couple of days. If you've got any questions, feel free to contact me.

Revision history for this message
Graham Binns (gmb) said :
#12

So...

I've completely misunderstood things here and have, rather foolishly,
skipped over the bit where you said your bugtracker is Mantis. I'll
contact you directly to discuss this further. My apologies.

Revision history for this message
Kern Sibbald (kern) said :
#13

On Thursday 14 August 2008 18:28:15 Graham Binns wrote:
> Your question #40915 on Launchpad itself changed:
> https://answers.edge.launchpad.net/launchpad/+question/40915
>
> Graham Binns posted a new comment:
> So...
>
> I've completely misunderstood things here and have, rather foolishly,
> skipped over the bit where you said your bugtracker is Mantis. I'll
> contact you directly to discuss this further. My apologies.

Nothing to apologize about, but I was a bit surprised about how easy it seemed
from your first response. I assume you know that I am at: kern at
sibbald.com