[cloudkitty] Joining the "CloudKitty Drivers" Launchpad team
Hello, While CloudKitty has moved to Storyboard to track its bugs [1], there is still a lot of content under the Launchpad project [2], including years of bug reports, blueprints, etc. As PTL, I would like to be able to administer the CloudKitty Launchpad project. I have requested access to the "CloudKitty Drivers" Launchpad team [3], but haven't heard back. I see some people have been on the waiting list for years [4]. Since the "OpenStack Administrators" team [5] is the owner "CloudKitty Drivers", would one of its members be able to grant me access? Many thanks, Pierre Riteau (priteau) [1] https://storyboard.openstack.org/#!/project/890 [2] https://launchpad.net/cloudkitty [3] https://launchpad.net/~cloudkitty-drivers [4] https://launchpad.net/~cloudkitty-drivers/+members#proposed [5] https://launchpad.net/~openstack-admins
Hello,
While CloudKitty has moved to Storyboard to track its bugs [1], there is still a lot of content under the Launchpad project [2], including years of bug reports, blueprints, etc.
As PTL, I would like to be able to administer the CloudKitty Launchpad project. I have requested access to the "CloudKitty Drivers" Launchpad team [3], but haven't heard back. I see some people have been on the waiting list for years [4].
Since the "OpenStack Administrators" team [5] is the owner "CloudKitty Drivers", would one of its members be able to grant me access?
Many thanks, Pierre Riteau (priteau)
I know nothing about it, but just curious - wasn't the Launchpad content imported in to Storyboard when making that switch? Sean
On 2020-10-01 15:47:56 -0500 (-0500), Sean McGinnis wrote: [...]
I know nothing about it, but just curious - wasn't the Launchpad content imported in to Storyboard when making that switch?
It was, for example this bug: https://launchpad.net/bugs/1550177 https://storyboard.openstack.org/#!/story/1550177 Unfortunately the recommendations for locking bug reporting in LP were never followed, so people have been opening bugs in both places since the migration. -- Jeremy Stanley
I know nothing about it, but just curious - wasn't the Launchpad content imported in to Storyboard when making that switch? It was, for example this bug:
https://launchpad.net/bugs/1550177 https://storyboard.openstack.org/#!/story/1550177
Unfortunately the recommendations for locking bug reporting in LP were never followed, so people have been opening bugs in both places since the migration. Doh!
On 2020-10-01 22:14:48 +0200 (+0200), Pierre Riteau wrote:
While CloudKitty has moved to Storyboard to track its bugs [1], there is still a lot of content under the Launchpad project [2], including years of bug reports, blueprints, etc.
As PTL, I would like to be able to administer the CloudKitty Launchpad project. I have requested access to the "CloudKitty Drivers" Launchpad team [3], but haven't heard back. I see some people have been on the waiting list for years [4].
Since the "OpenStack Administrators" team [5] is the owner "CloudKitty Drivers", would one of its members be able to grant me access?
Yes, I've taken care of this now, you should be a member (and administrator) of the drivers team as of a few minutes ago. Please go ahead and follow the post-migration steps documented here, since it appears nobody ever did: https://docs.openstack.org/infra/storyboard/migration.html#recently-migrated -- Jeremy Stanley
On Thu, 1 Oct 2020 at 23:08, Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2020-10-01 22:14:48 +0200 (+0200), Pierre Riteau wrote:
While CloudKitty has moved to Storyboard to track its bugs [1], there is still a lot of content under the Launchpad project [2], including years of bug reports, blueprints, etc.
As PTL, I would like to be able to administer the CloudKitty Launchpad project. I have requested access to the "CloudKitty Drivers" Launchpad team [3], but haven't heard back. I see some people have been on the waiting list for years [4].
Since the "OpenStack Administrators" team [5] is the owner "CloudKitty Drivers", would one of its members be able to grant me access?
Yes, I've taken care of this now, you should be a member (and administrator) of the drivers team as of a few minutes ago.
Please go ahead and follow the post-migration steps documented here, since it appears nobody ever did:
https://docs.openstack.org/infra/storyboard/migration.html#recently-migrated
Thank you Jeremy! What would be the process to import into Storyboard all Launchpad bugs that have been opened since the initial migration? Will the import script handle it fine or should we identify and tag all new bugs?
On 2020-10-02 11:29:48 +0200 (+0200), Pierre Riteau wrote: [...]
What would be the process to import into Storyboard all Launchpad bugs that have been opened since the initial migration? Will the import script handle it fine or should we identify and tag all new bugs?
We can rerun the import and it will add any new bugs it finds, or new comments which were left on old bugs after the previous import. It will not, however, update task statuses. If a bug was imported previously but then closed in Launchpad and left active in StoryBoard, the import will only pick up the additional comments from Launchpad for that bug, but not automatically resolve the existing task in StoryBoard for you. This is probably the behavior you'd want anyway, I'm just pointing it out for clarity. -- Jeremy Stanley
On Fri, 2 Oct 2020 at 17:12, Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2020-10-02 11:29:48 +0200 (+0200), Pierre Riteau wrote: [...]
What would be the process to import into Storyboard all Launchpad bugs that have been opened since the initial migration? Will the import script handle it fine or should we identify and tag all new bugs?
We can rerun the import and it will add any new bugs it finds, or new comments which were left on old bugs after the previous import.
It will not, however, update task statuses. If a bug was imported previously but then closed in Launchpad and left active in StoryBoard, the import will only pick up the additional comments from Launchpad for that bug, but not automatically resolve the existing task in StoryBoard for you. This is probably the behavior you'd want anyway, I'm just pointing it out for clarity.
Then could you rerun the import please? That would be great! After that I can lock down Launchpad bugs.
On 2020-10-02 17:21:27 +0200 (+0200), Pierre Riteau wrote: [...]
Then could you rerun the import please? That would be great! After that I can lock down Launchpad bugs.
I've completed an import update from the cloudkitty project on Launchpad to the openstack/cloudkitty project in StoryBoard. Please double-check that did what you expect and then feel free to proceed locking down bug reporting in LP. -- Jeremy Stanley
Thanks a lot Jeremy, it looks great! I've now locked down access to Launchpad bugs. On Fri, 2 Oct 2020 at 20:18, Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2020-10-02 17:21:27 +0200 (+0200), Pierre Riteau wrote: [...]
Then could you rerun the import please? That would be great! After that I can lock down Launchpad bugs.
I've completed an import update from the cloudkitty project on Launchpad to the openstack/cloudkitty project in StoryBoard. Please double-check that did what you expect and then feel free to proceed locking down bug reporting in LP. -- Jeremy Stanley
participants (3)
-
Jeremy Stanley
-
Pierre Riteau
-
Sean McGinnis