[Starlingx-discuss] LaunchPad vs Storyboard for bug tracking

[Eslimi, Dariush]

Thanks for response, but as is today not all that is mentioned in the blog is addressed by Storyboard:

* We will depend on UbuntuOne regardless of Launchpad, as we need it for gerrit.
* The limit of after 10 task per bug and performance, have this been discussed and raised with Launchpad team? Storyboard is not very speedy today, and this would not be an issue for StarlingX, limit of 10 is workable.
* API-first : Storybard suffers from same issue, rich API, UI not representation of API and backend.

So for short term, I suggest we use for Launchpad until Storyboard catches up and becomes a viable option for bug tracking.

Thanks,
Dariush

-----Original Message-----
From: Dean Troyer [mailto:dtroyer at gmail.com] 
Sent: August-09-18 1:06 PM
To: Eslimi, Dariush
Cc: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] LaunchPad vs Storyboard for bug tracking

On Thu, Aug 9, 2018 at 9:31 AM, Eslimi, Dariush <Dariush.Eslimi at windriver.com> wrote:
> So my question is for people who know the history and have more experience using it, Why Openstack is trying to replace this and move to Storyboard? What are the shortcomings for day to day use?

OpenStack's reasons for leaving LP include:
* needing to get to a single authentication authority (LP requires Ubuntu One accounts) to allow using a DCO rather than ICLA
* limitations on task tracking across projects
* persistent issues with API response and performance

Thierry Carrez's post with more details is at https://storyboard-blog.io/why-storyboard-for-openstack.html

dt

-- 

Dean Troyer
dtroyer at gmail.com