19:00:10 <zara_the_lemur__> #startmeeting storyboard
19:00:11 <openstack> Meeting started Wed Jun  7 19:00:10 2017 UTC and is due to finish in 60 minutes.  The chair is zara_the_lemur__. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:12 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:00:14 <openstack> The meeting name has been set to 'storyboard'
19:00:17 <zara_the_lemur__> #topic announcements
19:00:27 <zara_the_lemur__> NOTHING TO ANNOUNCE EXCEPT THAT WE ARE HAVING A VERY SHORT MEETING TODAY
19:00:35 <fungi> woo!
19:00:36 <zara_the_lemur__> #info this meeting will go straight to open discussion
19:00:40 <zara_the_lemur__> #topic open discussion
19:00:55 <zara_the_lemur__> okay if anyone wants to say stuff, go for it
19:01:00 <zara_the_lemur__> note your inprogress work, etc
19:01:03 <zara_the_lemur__> have a ball
19:01:18 <diablo_rojo> Party time!
19:01:23 <zara_the_lemur__> :D
19:01:31 <fungi> #link http://specs.openstack.org/openstack-infra/infra-specs/ OpenStack Project Infrastructure Design Specifications
19:01:40 <fungi> i'm trying to get the infra specs tidied
19:01:48 <diablo_rojo> https://review.openstack.org/#/c/471859/
19:01:56 <diablo_rojo> I did my part ^^
19:02:17 <fungi> diablo_rojo: mind adding yourself as the phase 1 assignee in the task tracker spec there and removing it from the help wanted section of the index?
19:02:43 <diablo_rojo> fungi,  did I not do it right? I thought that is what I did
19:03:00 <fungi> diablo_rojo: oh! i probably just haven't seen the change yet
19:03:24 <fungi> zara_the_lemur__: SotK: diablo_rojo: i'm wondering about some of the other storyboard specs we have listed there which might already be implemented or have become out of scope and should be abandoned
19:03:45 <fungi> for example, we have a spec for adding worklists and boards
19:04:05 <zara_the_lemur__> ah, yes, haha, I think SotK wrote that a couple of years ago
19:04:09 <fungi> i know we already have worklists and boards at this point
19:04:20 <fungi> so probably already implemented?
19:04:30 <SotK> I think everything in that spec is now implemented, I'll check later and move it into the place for done specs if so
19:04:44 <fungi> SotK: that would be a huge help!
19:05:05 <fungi> there are several unassigned ones in the help wanted section too (integration tests, story tags, subscriptions and events, branches)
19:05:14 <zara_the_lemur__> as for the others... I think Story Tags is partly implemented, and we have some stuff for Subscriptions and Events but I don't think I've ever looked at the spec for that
19:05:33 <zara_the_lemur__> (since both spec + functionality were before my time)
19:05:39 <fungi> diablo_rojo: aha, i see the link you added above is the thing i was asking for... thanks!
19:05:49 <diablo_rojo> fungi, no problem :)
19:06:09 <fungi> zara_the_lemur__: cool, any info you come up with will be appreciated. mostly just trying to clear out the cobwebs where we can
19:06:20 <SotK> iirc subscriptions and events is the old spec for a proper events stream and the ability for folk to subscribe to said stream
19:06:25 <SotK> I'll check on that later too
19:07:04 <zara_the_lemur__> I think the branches stuff is on hiatus indefinitely
19:07:08 <fungi> saying "this spec is for something completely different than what we ended up with" is fine too. i don't mind updating the spec before moving it into the implemented section, or just abandoning if we went a completely different direction
19:07:30 <zara_the_lemur__> (the spec says : "Implementation details should be left to the person that would do the implementation work. What follows is just a suggestion." )
19:07:42 <zara_the_lemur__> (and nobody has focused on doing that work yet)
19:07:47 <zara_the_lemur__> (so aiui details tbc)
19:08:33 <fungi> also fine to leave things which are not getting attention in the help wanted section as long as needed
19:09:02 <zara_the_lemur__> cool. :) (at a skim, I think the subscriptions stuff has been at least partially implemented since the other spec was written, since there's stuff about 'install rabbitmq on the storyboard server')
19:09:07 <fungi> i just wanted to do a better job of tracking what work was going on and knowing where to point people for specs that they can pick up and drive too
19:09:21 <zara_the_lemur__> np
19:09:37 <fungi> that's all i had
19:10:01 <zara_the_lemur__> we should try to get better at making specs really; there's a lot of stuff we just decide on irc.
19:10:59 <fungi> well, i don't mind specless development as long as there's documentation to point people at
19:11:28 <fungi> but specs can be useful if you're collaborating and need someone else to be able to easily pick up where you leave off and still know what your vision was for a feature
19:13:44 <zara_the_lemur__> yeah, storyboard itself can work okay for that, though things are harder to *find* there than in specs since there are more stories (I find it okay for things if I'm around to find the link, but people tend not to stumble across stories without a direct link)
19:16:52 <fungi> oh, watcher are discussing in their meeting (today?) whether to migrate to sb
19:17:04 <fungi> saw that on the ml a little while ago
19:17:37 <fungi> #link http://lists.openstack.org/pipermail/openstack-dev/2017-June/117963.html watcher migration to storyboard
19:17:39 <diablo_rojo> Yep I emailed them again :)
19:17:47 <diablo_rojo> Them, Tricircle, and Octavia
19:18:00 <fungi> cool, and thanks
19:18:05 <diablo_rojo> No problem.
19:18:36 <diablo_rojo> Tricircle was saying that sb isnt intuitive and that they would like to use soemthing else..Haven't responded to that email yet.
19:19:11 <zara_the_lemur__> heh
19:21:57 <diablo_rojo> Yeah crafting an email to respond today.
19:22:13 <diablo_rojo> In their meeting last night they chatted about it a bit and are looking at the links I sent them
19:22:25 <diablo_rojo> hopefully once they read the blog posts and play around a bit, things will get better.
19:24:56 <zara_the_lemur__> hopefully, and hey, if there are specific things they find confusing, there might be scope for someone to patch it
19:25:12 <diablo_rojo> Also true. I can mention that as well.
19:26:42 <fungi> that reminds me i still want to play around with maintaining a second rethemed and simplified webclient in parallel as a bug reporting interface
19:27:00 <fungi> depending on what they think is unintuitive that may be what they're looking for
19:27:20 <zara_the_lemur__> yeahhh, I'm also very curious to see what people make of that
19:28:32 <fungi> so for advanced task tracking use the main webclient interface, and for just submitting defects here's a url projects can include in their readme files which walks users through it using terminology they're used to/expecting
19:29:17 <fungi> we'll see how long it takes me to get around to working on that
19:29:20 <zara_the_lemur__> hahaha
19:29:38 <zara_the_lemur__> yeah part of me wants to go 'it should be simple enough so I'll try to take a look'
19:29:44 <zara_the_lemur__> but last week I meant to do a ton of reviews
19:29:46 <zara_the_lemur__> and did one review
19:29:58 <zara_the_lemur__> so I'm pacing myself.
19:30:28 <fungi> right, i too have had to learn to stop volunteering for things i'll never get around to
19:30:56 <fungi> so i can find time to do the rest
19:31:55 <diablo_rojo> zara_the_lemur__, one is better than none :)
19:32:59 <zara_the_lemur__> :) this week I'll aim for two
19:33:08 <zara_the_lemur__> okay, any more discussion or shall I end this meeting now?
19:33:20 <fungi> nothing else on my end!
19:35:22 <zara_the_lemur__> great! :)
19:35:24 <zara_the_lemur__> #endmeeting