15:01:12 <SotK> #startmeeting storyboard
15:01:12 <openstack> Meeting started Wed Sep 14 15:01:12 2016 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:16 <openstack> The meeting name has been set to 'storyboard'
15:01:34 <SotK> #link Agenda https://wiki.openstack.org/wiki/Meetings/StoryBoard#Agenda_for_next_meeting
15:01:40 <SotK> that appears to be out of date
15:01:56 <Zara> yeahhh, sorry
15:02:04 <Zara> I was thinking about the bugsquash and forgot about it
15:02:32 <SotK> there, fixed it (I think)
15:02:55 <Zara> nice
15:03:20 <SotK> #topic Announcements
15:03:45 <SotK> We merged the complex priorities UI for stories at long last
15:03:51 <Zara> \\\o///
15:03:59 <Zara> fiiiiiiiiiinally
15:04:09 <SotK> #info the complex priorities UI for stories was merged
15:04:12 <Zara> that patch series has been on my review dash for too long
15:04:36 <Zara> I'm happy to explain it to folks; going to send out an ML post once we've had a chance to catch any strange bugs
15:04:44 <Zara> that will inevitably pop up when more people use it
15:05:31 <fungi> oh, i also saw one merge about behavior for logged-out sessions? is that the fix i think it is?
15:05:45 <bkero> o/
15:05:58 <Zara> hm, I doubt it, since that was a bug we introduced that evening and fixed the same night
15:06:01 <fungi> (for the long-standing bug where you got several errors when returning to the webui after your session had timed out)
15:06:06 <fungi> oh, got it
15:06:08 <Zara> yeah, sorry, that's a different one
15:06:19 <fungi> ahh, eventually ;)
15:06:36 <Zara> the fix merged stopped some buttons from appearing when a user was logged out
15:06:37 <fungi> but excited for the prioritization feature
15:06:42 <Zara> since those were buttons for editing things and soforth
15:06:48 <Zara> and yay!
15:07:25 <Zara> (I really do want to fix that timeouts thing, argh)
15:07:45 <Zara> okay, shall I do the complex priorities explanation-in-progress in discussion in a bit?
15:08:04 <Zara> that way folks can ask questions
15:08:11 <fungi> sounds great
15:08:20 <SotK> indeed, sounds good to me
15:08:44 <SotK> there are no more announcements or urgent items, so lets move on
15:08:51 <SotK> #topic In Progress Work
15:09:16 <SotK> I'm working on being able to set permissions for teams in private stories instead of just for users
15:09:25 <SotK> this should make that feature somewhat more useful
15:09:34 <SotK> #link https://review.openstack.org/368917
15:10:15 <Zara> and I'm testing that atm
15:10:42 <Zara> so far I've managed to make sotk cry steadily all morning as I find bugs, so I'm counting this as a good day
15:11:47 <Zara> I've been mainly reviewing, and doing some misc documentation (I thought I'd already done some system config docs, but apparently hadn't)
15:12:02 <Zara> that is
15:12:06 <Zara> #link https://review.openstack.org/#/c/368797/
15:12:42 <Zara> other things have gone in; I plan to continue updating the docs for (and coverage of) the python client
15:12:59 <Zara> and misc ui fixes for the new tasks layout
15:13:26 <Zara> but teams review is my top priority right now.
15:13:48 <Zara> I think that's all I have
15:13:57 <fungi> i'm sorry i haven't had time to review/test the permissions stuff. i expect tristanC has also been busy as he moved recently
15:14:09 <fungi> i know he was planning to help test a lot of that
15:14:46 <Zara> yeah, atm it's all in the api so I think it'll be easier to ask around for reviews when we have a UI for it
15:15:23 * SotK is working on that bit :)
15:15:59 <Zara> (so so far I've been testing for, say, 'does this break search?' but not 'is this easy to use?')
15:16:23 <Zara> and thank you so much, SotK.
15:16:47 <fungi> sounds good
15:16:53 <fungi> thanks for working on all that
15:17:17 <fungi> i'm looking forward to being able to use it for embargoed vulnerability reports
15:19:33 <Zara> \o/
15:19:46 <SotK> Anything else in progress?
15:20:01 <Zara> I don't think so, although I just realised
15:20:25 <Zara> I don't think we announced that matthewbodkin had made tags reusable at the end of last week
15:20:48 <Zara> so yeah, StoryBoard should now suggest tags.
15:21:14 <Zara> that is, suggest existing tags, when you add a tag
15:21:19 <fungi> ooh, "suggest" how? like with some sort of ai based on content analysis?
15:22:07 <Zara> it does a browse on the string you're typing and matches it against tag titles
15:22:24 <Zara> #link https://storyboard-dev.openstack.org/#!/story/32
15:22:25 <fungi> got it. so when making a new tag name from scratch, it does (typeahead?) recommendation for already existing tag names
15:22:29 <Zara> yeah
15:22:35 <fungi> cool
15:22:40 <Zara> I was about to say 'try typing 'l' there and see what happens!'
15:22:57 <Zara> fairly standard but we were missing it before
15:22:58 <fungi> the "recommend tags for your story" ai did seem a but far-fetched ;)
15:23:08 <fungi> s/but/bit/
15:23:15 <Zara> yeah, hey, maybe one day! :D
15:23:15 <SotK> far-fetched, but would be great :)
15:23:27 <Zara> look at that sotk volunteering
15:23:33 <fungi> maybe some day, bauesian analysis plugin
15:23:38 <fungi> er, bayesian
15:23:51 <Zara> I want storyboard to make my coffee
15:23:57 <Zara> I don't even drink coffee but I want it to do that
15:24:17 * fungi upvotes storyboard dog-flosser feature
15:24:33 <Zara> yes! I thought we'd never get consensus on that!
15:24:41 <bkero> There's a standard for that. https://www.ietf.org/rfc/rfc2324.txt
15:24:48 <bkero> (the cofee pot, probably not dog-flossing)
15:24:53 <bkero> coffee*
15:24:55 <Zara> :D
15:25:14 * SotK senses it is safe to move on to discussion
15:25:20 <SotK> #topic Open Discussion
15:25:25 <fungi> error 418 was always my favorite
15:25:44 <pleia2> hehe
15:26:14 <Zara> so, I offered to give a quick explanation of the complex priorities implementation...
15:26:22 <fungi> please do
15:26:33 <Zara> okay!
15:26:40 <Zara> so, here is a story with plenty of tasks:
15:26:42 <Zara> #link https://storyboard-dev.openstack.org/#!/story/32
15:26:46 <Zara> and here is a worklist:
15:26:55 <Zara> #link https://storyboard-dev.openstack.org/#!/worklist/41
15:27:08 <Zara> if you subscribe to the worklist...
15:27:25 <Zara> when you browse to a story containing tasks from that worklist...
15:27:41 <Zara> those tasks, and their position in the worklist, will be listed in the top right
15:28:01 <fungi> ooh, yeah the "show items" drop-down there?
15:28:12 <Zara> so that you can see a) who cares about the task (based on which worklist it is) and b) how much they care (position in the worklist)
15:28:18 <Zara> yep
15:28:35 <fungi> it's not in the top-right for me, but it is near the top anyway
15:28:55 <Zara> huh, guessing it's a screen-size-variation thing
15:29:02 <pleia2> ah, neat
15:29:11 <Zara> (that's a reason we haven't documented the gui extensively, the other is that it often changes)
15:29:40 <Zara> so our thought is that this way, people can say how much a task matters to *them*, sidestepping the whole 'should this be high or medium or low' priority
15:29:45 <fungi> yeah, ui "documentation" is usually better as in-interface context help
15:29:50 <Zara> yep
15:30:00 <Zara> then people can decide whose priorities they care about
15:30:32 <Zara> and as fungi pointed out a few weeks ago, a nice side effect is that while a billion items can be 'high' priority, only one can be at the top of a list
15:30:40 <fungi> that's cool, and does i think go along with ttx's prioritization vision if memory serves
15:30:46 <Zara> which means that if someone wants to bump the priority of one task
15:30:55 <Zara> they immediately see how it affects the others
15:31:37 <fungi> ttx: if you're seeing this later, i expect you'll like/have input on this bit
15:32:04 <Zara> so, we've juggled some things around in the task list to make room for an 'add to worklist' button, in order to assign priority
15:32:17 <Zara> if you click the little arrows next to tasks
15:32:46 <Zara> those will give more options (and we now use projects to group tasks in stories)
15:33:23 <Zara> those buttons are very new and that's something I'm hoping to tidy
15:35:12 <Zara> anyone who's listed as a 'user' of a worklist can add/remove/move items in that worklist
15:37:29 <Zara> so, I'm very interested in folks trying it out and seeing what happens! you can turn on notifications for changes in worklists at the bottom of the 'profile' menu
15:37:48 <Zara> (we kept them separate to general email notifications so people who didn't want them wouldn't get spammed)
15:38:22 <pleia2> thanks Zara
15:38:39 <Zara> hopefully that made some amount of sense...
15:38:51 * SotK has nothing to add to it that immediately comes to mind :)
15:39:39 <Zara> I'll add that SotK is the one who has implemented it, and I've mainly just hovered around moaning and asking him to move buttons.
15:39:48 <pleia2> hehe
15:40:52 <Zara> I guess I've sometimes checked that it works.
15:41:31 <fungi> i can see this being extra useful to teams like nova which need to prioritize stuff going into release
15:42:09 <fungi> infra likely wouldn't use it quite as much since we tend to have a more scattered set of priorities and ongoing activities, but i'll keep an eye out for places where it would be useful for us
15:42:28 <Zara> I hope so; it's possible to add a task to any number of worklists so teams with different focuses can subscribe to different ones
15:42:51 <Zara> *teams on the same project with different focuses
15:42:58 <fungi> right, that seems super flexible, and i'm betting it will get leveraged in a number of ways we haven't thought of
15:43:09 <SotK> hopefully
15:43:16 <Zara> yeah, at this point I'm curious to see what happens with it.
15:43:28 <Zara> I think I need to do a bunch of explaining to make sure it's used at all
15:43:33 <Zara> but after that, it will be interesting
15:44:46 <Zara> and since it's possible to make a private worklist, it should be possible to integrate it with more sensitive things, though maybe we'll find some odd bugs around permissions.
15:44:55 <Zara> (that's always where the odd bugs turn up)
15:46:32 <Zara> that's all from me unless anyone has any questions etc?
15:47:02 <fungi> this would be a great time for people preparing to start the infra bugday to ask storyboard-specific questions
15:47:33 <fungi> (i'm useless and have none, but hopefully others are more on point than i am)
15:48:18 <pleia2> I don't have any either, but the last bug day was in April, any notable things we should keep an eye out for?
15:48:50 <Zara> I think the biggest thing is the change to the tasks UI.
15:49:14 * pleia2 nods
15:49:17 <Zara> though all the options should be the same (excepting priority), they've just moved around a bit.
15:49:34 <persia> Also, prioritisation: in the last bug day, some tasks were marked with priority, whereas now things to be done in a hurry should be added to a worklist (or a set of worklists, depending).
15:49:37 <pleia2> I'm also going to keep an eye on how good of a job we've been doing on actually using tasks... I haven't been using them much myself :\
15:49:39 * fungi observes that "any notable things we should keep an eye out for?" is actually one more question than he had
15:49:52 <pleia2> fungi: I thought about it halfway through writing my words!
15:49:59 <pleia2> I don't have questions actually here's one
15:50:06 <persia> Oh, and the gerrit integration landed, so folk fixing tasks might mark up commit messages to automatically update storyboard.
15:50:15 <pleia2> persia: oh yes, that's exciting
15:50:24 * persia blames zaro
15:50:30 <pleia2> yay zaro and Zara
15:50:42 <Zara> oh yeah, there's a page for worklists and boards now, so they're a bit easier to find
15:51:54 <Zara> aaaand I've just remembered I forgot to add subscriptions buttons on that page
15:52:04 <Zara> \o/
15:52:19 <fungi> great point. we should make sure to start using task numbers in our commit messages
15:53:25 <Zara> #link http://docs.openstack.org/infra/manual/developers.html#working-on-bugs
15:53:35 <Zara> ^ syntax for storyboard is now also documented there
15:53:53 * pleia2 adds to sprint etherpad
15:55:01 <SotK> 5 minutes left for any remaining questions
15:55:03 <clarkb> is it talking to production gerrit now too?
15:55:07 <SotK> it is
15:55:07 <Zara> yep!
15:55:17 <fungi> for anyone wanting to work on improving that section of the manual, it could still use a little additional explanation on the difference between tasks and stories
15:55:31 <fungi> and particularly the behavior difference between linking one or the other (or both?)
15:55:31 <Zara> oh yes, sorry, I think you did say in review
15:55:35 <pleia2> stories have tasks
15:55:57 <pleia2> so a patch could just be completing a task, but not the whole story
15:56:04 <fungi> right, more like explaining when you would want to link one vs the other
15:56:26 <Zara> yeah, linking the task changes the task status, and mentioning the story will mean there's a nice link to the story in gerrit
15:56:33 <pleia2> makes it a bit more grandular than just Partial-bug:
15:56:40 <Zara> *really* mentioning the task should also link to the story
15:56:58 <Zara> but it's tougher to do.
15:57:15 <Zara> (er, there I'm talking about ideal behaviour, not what it currently does)
15:57:21 <Zara> (I realised that was ambiguous, sorry)
15:57:39 <Zara> so for now I'd say it's best to note both
15:57:49 <pleia2> ah, noted
15:57:54 <fungi> a few sentences might make it clearer to readers coming from our lp conventions how to map their old workflows to storyboard
15:58:24 <Zara> yep
15:58:38 <Zara> I should get there sometime this week, prod me if I go quiet about it
15:59:01 <fungi> (and could also highlight where/how sb is more flexible and offers better granularity than the earlier method)
15:59:25 <fungi> looks like it's about sprint time
15:59:29 <SotK> yep
15:59:29 <Zara> hehe
15:59:34 * fungi goes and updates topics in places
15:59:34 <SotK> time is up!
15:59:39 <Zara> :)
15:59:45 <SotK> #endmeeting