Re: [openstack-dev] [tripleo] storyboard evaluation

2018-03-23 Thread Emilien Macchi
On Thu, Mar 22, 2018 at 12:11 PM, Kendall Nelson wrote: > Sounds like we have fungi set to run the migration of tripleO bugs with > the 'ui' tag for tomorrow after he gets done with the ironic migration. So > excited to have you guys start moving over! > Cool, please let

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-03-22 Thread Kendall Nelson
Sounds like we have fungi set to run the migration of tripleO bugs with the 'ui' tag for tomorrow after he gets done with the ironic migration. So excited to have you guys start moving over! Any idea what squad will want to go next/when they might want to go? No rush, I'm curious more than

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-03-17 Thread Emilien Macchi
On Fri, Mar 16, 2018 at 11:15 PM, Jason E. Rist wrote: > > I just tried this but I think I might be doing something wrong... > > http://storyboard.macchi.pro:9000/ Sorry I removed the VM a few weeks ago (I needed to clear up some resources for my dev env). > This URL

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-03-16 Thread Jason E. Rist
On 03/02/2018 02:24 AM, Emilien Macchi wrote: > A quick update: > > - Discussed with Jiri Tomasek from TripleO UI squad and he agreed that his > squad would start to use Storyboard, and experiment it. > - I told him I would take care of making sure all UI bugs created in > Launchpad would be

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-03-02 Thread David Moreau Simard
I have nothing to add but I wanted to mention that it seems like a great exercise to have UI/UX minded folks test our Storyboard implementation. Storyboard will be what we make of it based on the feedback and contributions it gets. It's an interesting opportunity. I'd actually like to encourage

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-03-02 Thread Emilien Macchi
A quick update: - Discussed with Jiri Tomasek from TripleO UI squad and he agreed that his squad would start to use Storyboard, and experiment it. - I told him I would take care of making sure all UI bugs created in Launchpad would be moved to Storyboard. - Talked with Kendall and we agreed that

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-01-17 Thread Thierry Carrez
Clint Byrum wrote: > [...] > That particular example board was built from tasks semi-automatically, > using a tag, by this script running on a cron job somewhere: > > https://git.openstack.org/cgit/openstack-infra/zuul/tree/tools/update-storyboard.py?h=feature/zuulv3 > > We did this so that we

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-01-17 Thread Clint Byrum
Excerpts from Thierry Carrez's message of 2018-01-17 11:51:52 +0100: > Emilien Macchi wrote: > > On Tue, Jan 16, 2018 at 8:29 AM, Jeremy Stanley wrote: > >>> - how do we deal milestones in stories and also how can we have a > >>> dashboard with an overview per milestone (useful

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-01-17 Thread Thierry Carrez
Emilien Macchi wrote: > On Tue, Jan 16, 2018 at 8:29 AM, Jeremy Stanley wrote: >>> - how do we deal milestones in stories and also how can we have a >>> dashboard with an overview per milestone (useful for PTL + TripleO >>> release managers). >> >> So far, the general

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-01-16 Thread Emilien Macchi
On Tue, Jan 16, 2018 at 9:01 AM, James E. Blair wrote: [...] > We're currently using tags like "zuulv3.0" and "zuulv3.1" to make this > automatic board: > > https://storyboard.openstack.org/#!/board/53 Yeah I guess using worklists & tags would probably be our best bet now.

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-01-16 Thread Emilien Macchi
On Tue, Jan 16, 2018 at 8:29 AM, Jeremy Stanley wrote: > On 2018-01-16 06:55:03 -0800 (-0800), Emilien Macchi wrote: > [...] >> I created a dev instance of storyboard and imported all bugs from >> TripleO so we could have a look at how it would be if we were using >> the tool:

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-01-16 Thread James E. Blair
Emmet Hikory writes: > Emilien Macchi wrote: > >> What we need to investigate: >> - how do we deal milestones in stories and also how can we have a >> dashboard with an overview per milestone (useful for PTL + TripleO >> release managers). > >     While the storyboard API

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-01-16 Thread Doug Hellmann
Excerpts from Jeremy Stanley's message of 2018-01-16 16:29:32 +: > On 2018-01-16 06:55:03 -0800 (-0800), Emilien Macchi wrote: > [...] > > I created a dev instance of storyboard and imported all bugs from > > TripleO so we could have a look at how it would be if we were using > > the tool: >

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-01-16 Thread Jeremy Stanley
On 2018-01-16 16:29:32 + (+), Jeremy Stanley wrote: [...] > Thankfully, SB was designed from the very beginning in an API-first > manner with the WebUI merely one possible API client (there are also > other clients like the boartty console client and a . [...] Oops, to complete my thought

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-01-16 Thread Jeremy Stanley
On 2018-01-16 06:55:03 -0800 (-0800), Emilien Macchi wrote: [...] > I created a dev instance of storyboard and imported all bugs from > TripleO so we could have a look at how it would be if we were using > the tool: [...] Awesome! We do also have a https://storyboard-dev.openstack.org/ deployment

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-01-16 Thread Ben Nemec
On 01/16/2018 08:55 AM, Emilien Macchi wrote: Hey folks, Alex and I spent a bit of time to look at Storyboard, as it seems that some OpenStack projects are migrating from Launchpad to Storyboard. I created a dev instance of storyboard and imported all bugs from TripleO so we could have a look

Re: [openstack-dev] [tripleo] storyboard evaluation

2018-01-16 Thread Emmet Hikory
Emilien Macchi wrote: > What we need to investigate: > - how do we deal milestones in stories and also how can we have a > dashboard with an overview per milestone (useful for PTL + TripleO > release managers).     While the storyboard API supports milestones, they don’t work very similarly to