15:00:31 <krotscheck> #startmeeting StoryBoard
15:00:32 <openstack> Meeting started Mon Oct  6 15:00:31 2014 UTC and is due to finish in 60 minutes.  The chair is krotscheck. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:33 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:35 <openstack> The meeting name has been set to 'storyboard'
15:00:38 <NikitaKonovalov> hi
15:00:39 <krotscheck> https://wiki.openstack.org/wiki/StoryBoard#Agenda
15:00:41 <krotscheck> Agenda: https://wiki.openstack.org/wiki/StoryBoard#Agenda
15:00:44 <krotscheck> ARGH
15:00:47 <krotscheck> #link https://wiki.openstack.org/wiki/StoryBoard#Agenda
15:00:50 <krotscheck> There we go
15:00:58 <krotscheck> Hey there, NikitaKonovalov!
15:01:02 <krotscheck> Anyone else here?
15:01:16 * fungi lurks
15:01:26 <fungi> jeblair is i believe still travelling this week
15:01:33 <krotscheck> Ok, let’s get started.
15:01:50 <ttx> o/
15:01:59 <krotscheck> #topic Urgent: CORS support
15:02:03 <krotscheck> It all landed!
15:02:21 <fungi> so storyboard is all CORSican now
15:02:24 <krotscheck> #link http://docs-draft.openstack.org/22/125222/1/check/gate-storyboard-webclient-js-draft/19d67a2/dist/#!/
15:02:47 <krotscheck> The docs draft build is now fully functional, meaning that ttx doesn’t have to download and run the build anymore to check out new UI things.
15:02:59 <ttx> krotscheck: so how do you use it ?
15:03:20 <fungi> browse to the docs-draft job result if it succeeded
15:03:22 <krotscheck> ttx: When you go to a code review, look for gate-storyboard-webclient-js-draft
15:03:23 <ttx> I tried a few shots in the dark but I assumed I may need that review I blocked
15:03:26 <krotscheck> Click on that.
15:03:47 <krotscheck> ttx: It builds off of that patch, so the one you blocked is the first one that actually works.
15:04:11 <ttx> ooooh
15:04:20 <ttx> shiny
15:04:30 <krotscheck> I thought you’d like that :)
15:04:41 <ttx> I don't even have to grunt anymore
15:04:46 <krotscheck> Oddly enough, in doing this we’ve also enabled iterative ui reviews for the UX people :)
15:04:59 <krotscheck> Yeah, leave the grunt-ing to the professionals.
15:04:59 <krotscheck> :D
15:05:09 <krotscheck> Any questions before we move on?
15:05:10 <ttx> really nice work
15:05:33 <ttx> removes all the friction, no excuse to not check out the effect anymore
15:05:42 <krotscheck> Eeexactly.
15:05:53 <krotscheck> Also, we’ll know very quickly whether the code breaks something.
15:06:15 <krotscheck> Mind you, it’ll cause a bit of a lag where the webclient can only show something if the APi supports it, but I’m ok with that.
15:06:22 <krotscheck> #topic Urgent: Subscription patches
15:06:37 <ttx> krotscheck: I'll review them now that I know how to do it.
15:06:40 <krotscheck> So, subscription’s been in a delay-oh-we-need-this-too loop for a while now.
15:06:51 <fungi> we should add a similar draft job for openstack-infra/publications
15:07:01 <ttx> probably tomorrow morning though
15:07:09 <krotscheck> The most recent item is nibalizer actually finding a bug in puppet-storyboard, which is fixed here: https://review.openstack.org/#/c/126072/
15:08:14 <krotscheck> As best as I can figure, the first two items listed in the agenda need to land in order. The two storyboard-webclient items already build on API’s that are there, but won’t do much until the other two land.
15:08:21 <krotscheck> #link https://wiki.openstack.org/wiki/StoryBoard#Agenda
15:09:00 <krotscheck> fungi: If possible, I’d like to grab you or clarkb this afternoon to keep an eye on https://review.openstack.org/#/c/124884/ wihle it lands.
15:09:08 <krotscheck> And that will wrap it for subscriptions.
15:09:47 <krotscheck> Any questions?
15:09:57 <fungi> krotscheck: happy to help... i'm open after lunch
15:09:58 <ttx> nope
15:10:09 <krotscheck> fungi: Ditto :). Let’s make a date!
15:10:50 <krotscheck> #topic Discussion: Story Types
15:10:54 <krotscheck> ttx: Take it away!
15:11:24 <ttx> well, hrm
15:11:41 <ttx> was a bit busy with all those RC1s last week
15:11:46 <ttx> so didn't draft anything
15:11:50 <krotscheck> Alrighey
15:11:59 <krotscheck> #topic Discussion: New topics?
15:11:59 <ttx> I hope, but I'm not sure, that this week will be less busy
15:12:02 <krotscheck> Anyone have anything new?
15:12:14 <NikitaKonovalov> I've updated my tags patch
15:12:41 <ttx> Merge avalanche with the unblocking of the head patch
15:12:44 <NikitaKonovalov> so it now is able to return tags in GET for stories
15:12:59 <krotscheck> NikitaKonovalov: Jenkins seems to not like that patch.
15:13:07 <NikitaKonovalov> I know
15:13:19 <NikitaKonovalov> will try to fix that
15:13:23 <krotscheck> Alrightey.
15:14:24 <krotscheck> Anything else?
15:14:38 * krotscheck will see if he can figure out why it’s failing.
15:15:08 <NikitaKonovalov> there is something wrong eith migration on tags
15:15:16 <NikitaKonovalov> with*
15:15:26 <krotscheck> Yeah, looks like.
15:16:26 <krotscheck> NikitaKonovalov: Maybe SQLAlchemy doesn’t like list-based associations when a story has no tags?
15:16:40 <NikitaKonovalov> krotscheck: probably
15:17:00 <NikitaKonovalov> one more question on tags, btw
15:17:04 <krotscheck> Go for it.
15:17:33 <NikitaKonovalov> given the list of tags, should we query using ALL or ANY of them
15:18:09 <NikitaKonovalov> that is what actually ttx is asking for in that CR also
15:19:14 <krotscheck> Hrm. Good question.
15:19:16 <fungi> sounds like an excuse for a search grammar
15:19:37 <NikitaKonovalov> we can have both queries actually
15:19:39 <fungi> (since there is in fact a third possible behavior besides the two you mention there)
15:20:03 <krotscheck> #topic Discussion: Tags
15:20:51 <krotscheck> fungi: What’s the third option?
15:21:10 <fungi> tags where (a and b) or c
15:21:19 <fungi> et cetera
15:21:35 <fungi> but as i said, you'd need a grammar
15:22:19 <fungi> not sure it's worth the effort to implement
15:22:54 <NikitaKonovalov> the query language makes sense if tags can be put into conditions along with other story fields
15:23:03 <krotscheck> Well, coming from the UI side of things I feel that we should try one, see if it works, try the other if it doesn’t work, and then if THAT doesn’t work, go for plan C.
15:24:08 <NikitaKonovalov> I prefer to filter with a kind of logical AND operation
15:24:23 <NikitaKonovalov> so more tags means narrow result set
15:25:11 <krotscheck> Makes sense.
15:25:20 <fungi> yeah, if there's already a syntax planned for logic operations, then reusing that with tags as search parameters seems reasonable
15:25:21 <krotscheck> Anyone disagree with trying that as plan A?
15:25:47 <fungi> sure, implicit exclusive and/intersection of results
15:26:09 <ttx> no that's fine
15:26:21 <krotscheck> Alright!
15:26:25 <krotscheck> Any more discussion topics?
15:27:01 <NikitaKonovalov> do we have anything StoryBoard relates at summit?
15:27:25 <krotscheck> #topic Discussion: StoryBoard
15:27:30 <krotscheck> Sorry
15:27:36 <krotscheck> #topic Discussion: Summit
15:28:02 <krotscheck> Right, so there’s an infra etherpad of all kinds of things that we might want to talk about at the summit.
15:28:30 * krotscheck is trying to find the link. Any help there, fungi?
15:28:54 <fungi> coming right up
15:29:02 <ttx> https://etherpad.openstack.org/p/kilo-infrastructure-summit-topics
15:29:05 <ttx> I win
15:29:15 <krotscheck> #link https://etherpad.openstack.org/p/kilo-infrastructure-summit-topics
15:29:20 <fungi> ttx: wins
15:29:21 <krotscheck> DOH
15:29:40 <krotscheck> From what I understand, infra only has 4 slots.
15:30:17 <krotscheck> Oh, that’s in the etherpad.
15:30:31 <krotscheck> Anyway, I’ve put StoryBoard up because it’s likely to start impacting other projects during the kilo cycle.
15:30:37 <krotscheck> And a lot of people will have questions.
15:30:52 <fungi> it seems like a reasonable one for the schedule, i agree
15:31:20 <krotscheck> Furthermore, I’m doing a 5 minute Lightning StoryBoard Walkthrough on monday at the HP Lightning Talks.
15:31:44 <krotscheck> And hopefully will again be able to do UX testing.
15:31:59 <krotscheck> Speaking of which: ttx - who do I talk to for space on that?
15:32:47 <ttx> krotscheck: you could ask claire@o.o -- but I wouldn't hold high hopes. ATL had plenty of spare space
15:33:03 <ttx> Paris, not so much
15:33:25 <ttx> I know there isn't spare space on the Design Summit area for example
15:33:40 <krotscheck> ttx: Will there be breakout space?
15:33:50 * krotscheck really only needs a power supply.
15:33:53 * fungi is reminded, should start an ml thread about key signing activity at the summit
15:33:54 <ttx> there is a developer lounge with corners in it
15:34:04 <krotscheck> That should do.
15:34:12 <ttx> ok, then you should be good
15:34:48 <krotscheck> One more thing. Is there anything trademarkish that would prevent me from printing up a t-shirt that says “Ask Me About StoryBoard”?
15:35:08 <fungi> no
15:35:21 <krotscheck> Cool.
15:35:29 <fungi> put "storyboard" on as many tee shirts as you like
15:35:58 <krotscheck> fungi: By what point will we know whether StoryBoard will be on the agenda so we can talk about what _actually_ to talk about?
15:36:09 * krotscheck loves having conversations about conversations.
15:36:39 <fungi> krotscheck: after jeblair returns... i'm not going to make those decisions while he's travelling, would rather he as ptl did so upon his return
15:37:03 <krotscheck> kk
15:37:35 <krotscheck> #topic MVP 1.1: Subscriptions
15:37:48 <krotscheck> So, subscriptions are (hopefully) three patches away from landing.
15:37:50 <krotscheck> woo!
15:38:09 <krotscheck> #topic MVP 1.1: Project Groups
15:38:49 <krotscheck> A bit of an update here. I got sick and tired of having to reboot the storyboard api server to work on API things, so I went in a refactored our functional tests to allow us to simulate an actual user via the Auth Header.
15:39:14 <krotscheck> That’s this patch: https://review.openstack.org/#/c/125816/
15:39:26 <krotscheck> And, well, while doing that I found a bug, which I also fixed in that.
15:40:12 <krotscheck> Now I’m building out functional tests for project groups, projects, stories, and tasks, so that we have coverage on discoverability across the API.
15:40:28 <krotscheck> As a side effect of that we’ll get the ability to search on project groups on all of those resources.
15:40:41 <krotscheck> But it’s going a bit slower than expected as a result.
15:40:42 <mordred> woot
15:40:52 <mordred> well, testing is good
15:41:22 <krotscheck> Right.
15:41:45 <krotscheck> My hope is to get projects and tasks done this week, but no guarantees on that.
15:42:11 <krotscheck> The goal is to have “Project Group: Foo” be one of the search tags.
15:42:26 <mordred> I believe I'd be likely to use that a lot
15:42:40 <krotscheck> Any questions?
15:43:30 <krotscheck> #topic MVP 1.1: Tags
15:43:40 <krotscheck> NikitaKonovalov: Anything new?
15:43:46 <krotscheck> (Other than what was discussed earlier?
15:45:42 <krotscheck> I’ll take that as a no.
15:45:52 <krotscheck> #topic MVP 1.1: Emails
15:45:55 <krotscheck> Progress!
15:46:31 <krotscheck> Last week I replaced the hard-coded deferred processors with a stevedore-run plugin system.
15:46:36 <krotscheck> Patch is here: https://review.openstack.org/#/c/125504/
15:46:49 <krotscheck> The intent here is that emails will also be a plugin.
15:47:13 <mordred> ooh
15:47:14 <krotscheck> So an event arrives, we process subscriptions, we figure out which email it goes into, and then we move on to the next one.
15:47:16 * mordred likely
15:47:18 <mordred> likey
15:47:35 * mordred goes to review stevedore patch
15:47:54 <krotscheck> And since it’s stevedore, I may have also just allowed infra to go write it’s own third party plugins to integrate with zuul, gerrit, yadda yadda yadda.
15:48:58 * mordred likes the "handle" method
15:49:10 <krotscheck> But I guess the real point here is that I’ve paved the way for emails.
15:49:38 <mordred> yah. like it. so each event gets passed to handle as a json blob?
15:50:09 <krotscheck> yep, that’s the idea.
15:50:15 <krotscheck> And then the plugin can figure out what it wants to do.
15:51:19 <krotscheck> The enable method is there so that plugins can trigger themselves based on their own configuration. Say you have an email plugin but no smtp server, etc.
15:52:05 <krotscheck> Anyway, taht’s the update on emails. Any questions?
15:53:22 <krotscheck> #topic Open Discussion
15:53:31 * krotscheck has already discussed everything.
15:54:10 <krotscheck> Anyone else?
15:55:14 <ttx> nope
15:55:26 <krotscheck> Alrightey, thanks everyone!
15:55:30 <krotscheck> #endmeeting