15:04:30 <SotK> #startmeeting storyboard
15:04:31 <openstack> Meeting started Wed Jul  6 15:04:30 2016 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:04:32 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:04:35 <openstack> The meeting name has been set to 'storyboard'
15:04:48 <SotK> Apologies if I disappear at any point, my internet is misbehaving today
15:04:55 * anteaya nods
15:05:10 <SotK> #link https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda
15:05:46 <SotK> I don't think there is anything urgent or announcement-like
15:05:57 <anteaya> I can't think of anything
15:06:00 <SotK> #topic In Progress Work
15:06:40 <SotK> I sent a patch to make editing and deleting comments configurable and disabled by default
15:06:46 <anteaya> thank you
15:06:59 <SotK> #link https://review.openstack.org/#/c/338165/
15:07:24 <anteaya> fungi: ^^ if you could be so kind as to add that to your review queue
15:07:56 <SotK> I also updated the webclient patch which adds a UI for editing to cause it to be disabled by default too
15:08:05 <SotK> #link https://review.openstack.org/#/c/333418/
15:08:59 <ttx> o/
15:09:13 <anteaya> I guess in the api docs, I can just say these features are disabled by default: https://review.openstack.org/#/c/338165/3/storyboard/api/v1/timeline.py
15:09:22 <anteaya> and skip the examples for the docs
15:09:33 <anteaya> welcome ttx
15:10:09 * SotK is happy with that
15:10:14 <SotK> hi ttx
15:10:16 <anteaya> okay great, thank you
15:10:39 <anteaya> I'll add that to my current timeline api docs patch after the meeting
15:11:26 <SotK> I hope to update my "complex priorities" patch after the meeting at last
15:11:45 <anteaya> what is the description of complex priorities?
15:11:54 <SotK> #link https://review.openstack.org/#/c/312666/
15:11:56 <anteaya> sorry I haven't been following that feature
15:13:02 <anteaya> I guess the complex priorities feature would be of interest to folks who do realeases and such
15:13:11 <anteaya> ttx does the above patch suit your needs?
15:13:31 <anteaya> or the rationale for the change at the very least?
15:15:00 <SotK> that patch is intended to provide a way to see in the story view if (and how) relevant things in that story are to people who's priorities you care about
15:15:38 <anteaya> oh I missed this adds something to the story view
15:15:52 <anteaya> I have been enjoying how uncluttered the story view has been personally
15:16:08 <anteaya> and if I wanted clutter, I could look at worklists or boards
15:17:03 * SotK can't see how else such a thing can be achieved, without hiding priority behind a button click
15:17:40 <anteaya> I'm wondering what would happen if it could be seen in the subscription view
15:18:10 <anteaya> then if I am subscribed to a story I might get a window or pop up or expansion box with this information
15:18:20 <SotK> hm, but then you'd have to subscribe to a story in order to see its effective priority
15:18:26 <anteaya> yes
15:18:33 <anteaya> but isn't that the point?
15:18:36 <ttx> looking
15:19:03 <anteaya> if I want to see how important this story is to other people, shouldn't I say I want that by subscribing to the story?
15:19:44 <SotK> no, you subscribe to other people's worklists (their expression of priority/importance)
15:20:13 <SotK> essentially saying "tell me if I'm looking at something $person cares about"
15:20:19 <anteaya> oh so if I don't subscribe to other people's worklists I don't have to see this?
15:20:45 <anteaya> I thought that was the point of the worklist?
15:21:14 <anteaya> if I subscribe to someone else's work list then I can see what is on the worklist and the priority given to it in the worklist
15:21:20 <anteaya> can I not?
15:21:41 <anteaya> and I'm emailed of changes to that worklist, am I not?
15:22:37 <ttx> struggling to see the change in draft (400: GET https://storyboard-dev.openstack.org/api/v1/worklists: Unknown argument: "subscriber_id")
15:23:17 <SotK> ah yeah, it depends on https://review.openstack.org/#/c/335458/ now
15:23:40 <ttx> anteaya: basically this is saying that there is no single "priority" valid for everyone. We can use custom lists to express that
15:23:56 <ttx> and sort them to express local priority
15:24:02 <anteaya> ttx: is this helpful for you?
15:24:39 <ttx> anteaya: that was one of the design ideas around original StoryBoard. I wouldn't consider it a must-have personally, but it's hard to change down the line.
15:24:56 <anteaya> ttx if you want this then that's fine
15:25:26 <anteaya> I do note it will be difficult to share what you are looking at with others via a url, since you view is customized to you
15:25:30 <anteaya> or I believe it will
15:25:56 <anteaya> necessitating the need for screenshots to share what you are looking at if you question it
15:26:19 <anteaya> but if that would help the release team, then okay
15:26:47 <ttx> anteaya: like I said, that was part of the original design ideas. Since then I'm not the primary customer though
15:27:05 <ttx> so we may discover that most project teams are in love with flat priority
15:27:17 <anteaya> oh
15:27:24 <ttx> and would rather keep that one displayed as well
15:27:52 <anteaya> I haven't been soliciting opinions until after the api docs have examples
15:27:53 <ttx> I still think it's sound design... but not 100% sure that helps in the "must-have before OpenStack migration" front
15:28:12 <anteaya> since that is our biggest stumbling point via adoption for folks who use the api
15:28:30 <anteaya> yeah I don't know how to collect thoughts on this
15:29:03 <anteaya> as I am concerned finding a microcosim to discuss won't get any further than the api docs need expanding
15:29:27 <anteaya> hence my priority to expand the api docs and _then_ collect opinions
15:29:33 <anteaya> so I don't know what to say here
15:30:26 <SotK> it'll be easier to bring back flat priorities if people can't work without them, than to change to this model in future I believe
15:31:07 <anteaya> SotK: well as long as you are open to the idea that this feature may be requested to be reverted in future
15:31:51 <anteaya> until I can get the api docs finished so they are usable and get some feedback from folks, I simply don't know
15:32:38 <anteaya> on that note I am hoping to get 80% of the api doc examples in place by the end of the week
15:33:10 <anteaya> there are some commands I can't run as I am not admin, I'm grateful for admin help on those patches so I can include the correct commands
15:33:14 <anteaya> and thank you for reviews
15:33:28 <anteaya> https://review.openstack.org/#/q/topic:expand-api-docs
15:34:10 * SotK will look at the project commands today too
15:34:21 <anteaya> thanks so much
15:34:46 <anteaya> I'll respin the tasks patch after the meeting
15:35:33 <SotK> thanks :)
15:35:38 <anteaya> :)
15:36:06 <SotK> I think that's all the in progress stuff I'm sure of the status of
15:36:24 <SotK> #topic Open Discussion
15:36:26 <anteaya> that's all I had
15:36:57 <anteaya> from what little feedback I have been hearing I think folks that have been looking at storyboard recently are really happy
15:37:15 <anteaya> I think the gerrit integration really helps a lot, I think zaro is still away
15:37:40 <SotK> that is good news :)
15:37:54 <anteaya> I'll talk to him once he returns and see where we are, it is possible that a puppet run overwrote his manual configuration of the plugin on review-dev
15:38:02 <anteaya> thanks, yes I am encouraged
15:38:29 <anteaya> so right now gerrit integration on dev server might not be working, I haven't tested it myself though
15:39:04 <anteaya> that's all I have for open discussion
15:40:15 <SotK> hopefully when zaro returns we can get the puppetry for it merged
15:40:23 <anteaya> that also would be awesome
15:45:28 <SotK> anyone got anything else?
15:45:50 <anteaya> I have nothing else
15:47:07 <SotK> I shall end the meeting then, thanks for coming folks!
15:47:11 <SotK> #endmeeting