15:04:30 #startmeeting storyboard 15:04:31 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 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:04:35 The meeting name has been set to 'storyboard' 15:04:48 Apologies if I disappear at any point, my internet is misbehaving today 15:04:55 * anteaya nods 15:05:10 #link https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda 15:05:46 I don't think there is anything urgent or announcement-like 15:05:57 I can't think of anything 15:06:00 #topic In Progress Work 15:06:40 I sent a patch to make editing and deleting comments configurable and disabled by default 15:06:46 thank you 15:06:59 #link https://review.openstack.org/#/c/338165/ 15:07:24 fungi: ^^ if you could be so kind as to add that to your review queue 15:07:56 I also updated the webclient patch which adds a UI for editing to cause it to be disabled by default too 15:08:05 #link https://review.openstack.org/#/c/333418/ 15:08:59 o/ 15:09:13 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 and skip the examples for the docs 15:09:33 welcome ttx 15:10:09 * SotK is happy with that 15:10:14 hi ttx 15:10:16 okay great, thank you 15:10:39 I'll add that to my current timeline api docs patch after the meeting 15:11:26 I hope to update my "complex priorities" patch after the meeting at last 15:11:45 what is the description of complex priorities? 15:11:54 #link https://review.openstack.org/#/c/312666/ 15:11:56 sorry I haven't been following that feature 15:13:02 I guess the complex priorities feature would be of interest to folks who do realeases and such 15:13:11 ttx does the above patch suit your needs? 15:13:31 or the rationale for the change at the very least? 15:15:00 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 oh I missed this adds something to the story view 15:15:52 I have been enjoying how uncluttered the story view has been personally 15:16:08 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 I'm wondering what would happen if it could be seen in the subscription view 15:18:10 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 hm, but then you'd have to subscribe to a story in order to see its effective priority 15:18:26 yes 15:18:33 but isn't that the point? 15:18:36 looking 15:19:03 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 no, you subscribe to other people's worklists (their expression of priority/importance) 15:20:13 essentially saying "tell me if I'm looking at something $person cares about" 15:20:19 oh so if I don't subscribe to other people's worklists I don't have to see this? 15:20:45 I thought that was the point of the worklist? 15:21:14 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 can I not? 15:21:41 and I'm emailed of changes to that worklist, am I not? 15:22:37 struggling to see the change in draft (400: GET https://storyboard-dev.openstack.org/api/v1/worklists: Unknown argument: "subscriber_id") 15:23:17 ah yeah, it depends on https://review.openstack.org/#/c/335458/ now 15:23:40 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 and sort them to express local priority 15:24:02 ttx: is this helpful for you? 15:24:39 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 ttx if you want this then that's fine 15:25:26 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 or I believe it will 15:25:56 necessitating the need for screenshots to share what you are looking at if you question it 15:26:19 but if that would help the release team, then okay 15:26:47 anteaya: like I said, that was part of the original design ideas. Since then I'm not the primary customer though 15:27:05 so we may discover that most project teams are in love with flat priority 15:27:17 oh 15:27:24 and would rather keep that one displayed as well 15:27:52 I haven't been soliciting opinions until after the api docs have examples 15:27:53 I still think it's sound design... but not 100% sure that helps in the "must-have before OpenStack migration" front 15:28:12 since that is our biggest stumbling point via adoption for folks who use the api 15:28:30 yeah I don't know how to collect thoughts on this 15:29:03 as I am concerned finding a microcosim to discuss won't get any further than the api docs need expanding 15:29:27 hence my priority to expand the api docs and _then_ collect opinions 15:29:33 so I don't know what to say here 15:30:26 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 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 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 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 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 and thank you for reviews 15:33:28 https://review.openstack.org/#/q/topic:expand-api-docs 15:34:10 * SotK will look at the project commands today too 15:34:21 thanks so much 15:34:46 I'll respin the tasks patch after the meeting 15:35:33 thanks :) 15:35:38 :) 15:36:06 I think that's all the in progress stuff I'm sure of the status of 15:36:24 #topic Open Discussion 15:36:26 that's all I had 15:36:57 from what little feedback I have been hearing I think folks that have been looking at storyboard recently are really happy 15:37:15 I think the gerrit integration really helps a lot, I think zaro is still away 15:37:40 that is good news :) 15:37:54 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 thanks, yes I am encouraged 15:38:29 so right now gerrit integration on dev server might not be working, I haven't tested it myself though 15:39:04 that's all I have for open discussion 15:40:15 hopefully when zaro returns we can get the puppetry for it merged 15:40:23 that also would be awesome 15:45:28 anyone got anything else? 15:45:50 I have nothing else 15:47:07 I shall end the meeting then, thanks for coming folks! 15:47:11 #endmeeting