19:00:33 <zara_the_lemur__> #startmeeting storyboard
19:00:34 <openstack> Meeting started Wed May 17 19:00:33 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:35 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:00:38 <openstack> The meeting name has been set to 'storyboard'
19:00:43 <zara_the_lemur__> #topic Announcements
19:00:50 <diablo_rojo> Hell o :)
19:00:53 <diablo_rojo> Hello
19:00:55 <zara_the_lemur__> hi!
19:01:01 <zara_the_lemur__> #info It was the summit last week, and we did a talk!
19:01:06 <zara_the_lemur__> standby while I retrieve a link
19:01:30 <zara_the_lemur__> #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/17632/storyboard-101-survival-guide-to-the-great-migration?BackURL=https%3A%2F%2Fwww.openstack.org%2Fsummit%2Fboston-2017%2Fsummit-schedule%2Fglobal-search%3Ft%3Dzara%2Bzaimeche%23eventid%3D17632
19:01:31 <SotK> we did!
19:01:40 <zara_the_lemur__> apparently that's the last way I found that link
19:01:45 <SotK> thanks for the question answering assistance fungi
19:02:01 <zara_the_lemur__> looks like I searched myself, how embarrassing...
19:02:03 <fungi> thanks for giving the talk--it was awesome!
19:02:19 <zara_the_lemur__> thanks to everyone involved! :D
19:02:51 <zara_the_lemur__> I very much appreciated SotK's videos, diablo_rojo's slideshow knowhow and fungi's Q&A
19:03:12 <diablo_rojo> Now we can send that out with the blog posts and hopefully people will stop asking the same questions :)
19:03:28 <SotK> we can hope
19:03:37 <zara_the_lemur__> + a big thank you to everyone who attended! :)
19:03:53 <fungi> there is no hope... people never stop asking questions
19:04:09 <diablo_rojo> fungi, I was only half serious :)
19:04:21 <fungi> but maybe they will ask fewer/different questions now!
19:04:24 <jpmaxman> :)
19:04:41 <zara_the_lemur__> (all talks were recorded, so there is a video at that link, in case anyone is unaware)
19:04:56 <zara_the_lemur__> (so all is not lost if you were unable to attend!)
19:05:03 <zara_the_lemur__> (weep not)
19:05:12 <zara_the_lemur__> okay, I don't think we have any other announcements
19:05:20 <zara_the_lemur__> #topic Urgent Items
19:05:22 <diablo_rojo> Except that you didnt get to see the greatness in person
19:05:32 <zara_the_lemur__> :D
19:05:46 <fungi> or come out to eat with the infra team at the salty pig
19:05:59 <fungi> you know, important stuff
19:06:34 <zara_the_lemur__> that was indeed extremely important
19:06:53 <zara_the_lemur__> so, I gather Craton and Cloudkitty are planning to migrate next Monday
19:07:02 <diablo_rojo> Correct
19:07:08 <diablo_rojo> yay for more migrations!
19:07:19 <zara_the_lemur__> yep! \o/ I intend to run a test migration between now and then just to check nothing has changed, since it was a little while ago that we tested.
19:07:23 <zara_the_lemur__> but that shouldn't block anything
19:07:47 <diablo_rojo> Sweet
19:07:58 <SotK> \o/
19:08:07 <diablo_rojo> How are other test migrations going? I know things got a little hairy with prepping for the summit
19:08:23 <zara_the_lemur__> hah, I haven't done anything since I last mentioned doing one
19:08:27 <zara_the_lemur__> I think the story should be up to date
19:08:32 <diablo_rojo> Fair enough :)
19:08:36 * SotK has been too busy catching up on sleep since summit to do much
19:08:39 * diablo_rojo goes to look
19:08:44 <fungi> oh, right. adding that migration to my reminders now just so i don't double-book myself in the interim ;)
19:09:53 * zara_the_lemur__ looks for a link to the relevant story
19:10:26 <zara_the_lemur__> #link https://storyboard.openstack.org/#!/story/2000876
19:10:43 <zara_the_lemur__> (maybe one day I'll prep all my links *before* a meeting; sorry)
19:10:58 <diablo_rojo> zara_the_lemur__, no worries
19:11:03 <diablo_rojo> you still found it faster than me
19:11:29 <zara_the_lemur__> okay, to me, that story looks suspiciously like I have noted my to-test-migrations list but not everything is on there
19:11:55 <zara_the_lemur__> I'm sure this isn't the first time we have tested craton and cloudkitty but I don't see them listed
19:12:33 <diablo_rojo> Yeah I didnt put them on there since we had already tested them once
19:12:38 <diablo_rojo> but we can make tasks for them
19:12:50 <zara_the_lemur__> ah, right, so we made that after, makes sense
19:13:14 * zara_the_lemur__ will make a coupla tasks now then
19:13:20 <diablo_rojo> Sounds good.
19:13:32 <diablo_rojo> If you need more projects to test I can get you more too :)
19:13:40 <zara_the_lemur__> \o/ I don't think we have anything else urgent, just a ton of in-progress stuff
19:13:43 <zara_the_lemur__> so...
19:13:45 <zara_the_lemur__> #topic In-Progress Work
19:14:08 <zara_the_lemur__> I have a massive review backlog and spent most of last week practicing speaking while drying my hair
19:14:20 <SotK> so I sent a patch that fixes/works around the 401 error
19:14:24 <SotK> we should merge that :)
19:14:29 <zara_the_lemur__> I'm glad you're more useful than me
19:14:35 <diablo_rojo> SotK, the one I reviewed yesterday?
19:14:46 <fungi> which 401 error? the one where you have to log out and back in when you've been idle for a while?
19:14:52 <diablo_rojo> fungi, yep
19:14:55 <diablo_rojo> I think lol
19:15:11 <SotK> diablo_rojo, fungi: yes to both
19:15:14 <zara_the_lemur__> yeah, we hid the actual 401 message but there's a leftover 400 message
19:15:27 <fungi> HUGE thanks! i think that's probably the #1 most visible bug in the webclient for a long time now
19:15:32 <zara_the_lemur__> yyyyyyep
19:15:44 <zara_the_lemur__> I will try to get to that tonight or tomorrow
19:15:52 <zara_the_lemur__> whine at me until I do it
19:16:11 <fungi> that bug alone was probably going a very long way toward making new users wonder whether the software was actually maintained/production-ready
19:16:20 <zara_the_lemur__> (I want to check it doesn't break anything else, but it'd have to be pretty interesting to make things *worse*)
19:16:25 <zara_the_lemur__> definitely agree there
19:16:35 * fungi is thrilled someone got to the bottom of it
19:16:55 <zara_the_lemur__> it's my most hated bug
19:17:00 <SotK> yeah, it was mentioned at summit so I thought I would do some investigating
19:17:12 <zara_the_lemur__> I don't go on about it because I looked into it and couldn't work out to fix it, so wasn't productive
19:17:21 <zara_the_lemur__> but there is a very long story about it
19:17:53 <SotK> the "fix" is just to refresh the page when the tokens are all expired, but I don't think there will be many neater ways to fix it without a large pile of work
19:18:05 <zara_the_lemur__> #link https://storyboard.openstack.org/#!/story/2000407
19:18:17 <diablo_rojo> Much appreciated either way
19:18:57 * zara_the_lemur__ is somewhat concerned that might reintroduce some of the original issues, but will test first
19:19:02 <SotK> s/the tokens are all expired/both access and refresh tokens are expired so we can't get a new access token without re-authenticating/
19:19:23 <zara_the_lemur__> I think a lot of sites do things that way
19:19:57 * SotK too
19:20:28 <SotK> the other option was a "you've been logged out" page, but that would be extremely annoying if you paste a link after not using it for a month
19:20:42 <zara_the_lemur__> one thing I do wonder with that-- if a user types a bunch of stuff, and their token expires midway through, before saving, what happens?
19:21:08 <zara_the_lemur__> I would assume the content is lost
19:22:12 <SotK> indeed, but that would be extremely unlikely if my understanding of things is correct
19:22:43 <SotK> (that is, the refresh token gets refreshed if it is nearly expired whilst you are actively using storyboard)
19:23:14 * zara_the_lemur__ isn't sure exactly what would be 'active' there
19:23:32 <zara_the_lemur__> ie: is typing in a text field enough for that, or does it require making api calls?
19:23:37 <SotK> doing anything that makes a request to the API I believe
19:23:43 <zara_the_lemur__> yeah
19:24:30 <zara_the_lemur__> so it's not a massive deal, I'm thinking that a surprise refresh might be sliiiiightly more prone to losing data than a 'I know I've left this alone for ages but can keep typing and just copy my text before sending because I know it'll log me out then'
19:24:59 <zara_the_lemur__> it's not a reason to block anything, just thinking, sorry
19:25:12 <zara_the_lemur__> other in-progress things?
19:25:14 <SotK> np, thinking is good :)
19:25:15 <zara_the_lemur__> there are boards patches
19:25:19 <zara_the_lemur__> oh so many boards patches
19:25:52 <SotK> and a search thing to support browsing for multiple tags in a way that isn't a lucky hack
19:25:55 <diablo_rojo> SotK, had questions for you about your comment on my patch
19:26:11 <diablo_rojo> More clarification
19:26:30 * SotK goes to look
19:26:40 <diablo_rojo> I am checking to see if 'branch' == project and if it does add master, otherwise..?
19:26:57 <diablo_rojo> #link https://review.openstack.org/#/c/437469/5/storyboard/migrate/launchpad/loader.py
19:28:06 <diablo_rojo> Also I should probably add pike to the list of releases..
19:28:31 <SotK> ah, so that will currently add a master branch for each thing that doesn't have a release defined, and if another project has a bugtask there then we'll add multiple branches named master doing that
19:29:12 <diablo_rojo> Okay so needs to be tweaked a bit.
19:29:13 <SotK> then it struck me that we need to make sure the project name in the url is the name of the project we are trying to add otherwise we will have a mess
19:29:23 <diablo_rojo> AH
19:29:25 <diablo_rojo> Okay
19:29:28 <diablo_rojo> that makes more sense now
19:30:04 <diablo_rojo> so I can do a check to see if the project in the url is project and if that is the case we will look to see if the branch exists already and if it doesnt add master
19:30:07 <diablo_rojo> Got it
19:30:08 <SotK> so you can probably just do something like `elif branch == project_name` instead of `else` there and fix everything (in the case where we want master the last thing in the url is the project name
19:30:36 <diablo_rojo> that works too
19:31:17 <diablo_rojo> I will push that change today
19:31:22 <SotK> thanks :)
19:31:24 * SotK notices that https://review.openstack.org/#/c/455025/ is also not merged yet, and mithers Zara for reviews :)
19:31:44 <zara_the_lemur__> haha, thaks for mithering
19:32:15 <zara_the_lemur__> I am slowly getting through them in the order they went up there, but emphasis on the slow
19:33:22 <SotK> thank you :)
19:33:41 <zara_the_lemur__> should have more time now there's no talk stuff in the immediate future
19:35:32 <zara_the_lemur__> I will prrrrobably prioritize that 401 one though, because the world hates that bug
19:35:42 <diablo_rojo> Sweet :) And I should have some more time to pitch in now that the Summit is done and that the PTG isnt till September
19:36:39 <zara_the_lemur__> any other in-progress work?
19:36:45 <SotK> yes definitely prioritise the 401 one :)
19:37:02 <jpmaxman> I had a question about possibly in progress work :)
19:37:15 <diablo_rojo> jpmaxman, whats up? :)
19:37:17 <jpmaxman> somebody mentioned permissions were being worked on?
19:37:26 <jpmaxman> at the summit meeting
19:37:34 <diablo_rojo> permissions...like private stories and bugs?
19:37:40 <jpmaxman> right
19:38:01 <diablo_rojo> https://storyboard.openstack.org/#!/story/2000568
19:38:14 <fungi> i think most of it's already there. you can make a story private and add people to it already
19:38:35 <zara_the_lemur__> *nod*
19:38:39 * fungi frowns at the pink 400 error
19:38:43 <zara_the_lemur__> haha
19:38:45 <fungi> soon to be fixed!
19:38:47 <jpmaxman> cool
19:38:54 <jpmaxman> what about entire projects private?
19:38:55 <SotK> yeah, the missing piece is adding the VMT to vulnerability things automatically
19:39:03 <SotK> entire projects private is not a thing
19:39:07 <jpmaxman> ok
19:39:26 <fungi> or at least hasn't been identified as an immediate goal
19:39:37 <jpmaxman> gotcha
19:39:53 <SotK> yeah, I mean "not a thing" as "not implemented or thought about" :)
19:39:58 <jpmaxman> ok private stories seems good for sure :)
19:40:29 <zara_the_lemur__> it has been discussed in the past (though not for openstack); the general thought is that it's more sensible to spin up one storyboard instance per project in cases where they need to be separated
19:40:34 <zara_the_lemur__> since it's desgined for cross-project work
19:40:39 <diablo_rojo> One thing that hasnt been done there yet is how to migrate existing private bugs
19:40:59 <fungi> i can imagine a fairly trivial feature where a specific project can default to new stories being created private instead of public
19:41:41 <fungi> but private boards and worklists would probably be a lot harder to cover?
19:41:47 <zara_the_lemur__> (so where you have a situation where there should be walls between projects, it doesn't make sense to put their issues in the same tracker, because it's harder to keep track of whom can see what)
19:42:24 <SotK> fungi: what do you mean by "cover" there?
19:42:33 <zara_the_lemur__> (and leads to situations where people put documents up that they think everyone can see, when only some subset of people can see them, and communication suffers as a result)
19:42:41 <jpmaxman> well the description seems to indicate that private stories are also not visible to those without permissions in the worklists/boards
19:42:51 <fungi> SotK: as in i don't think we have a notion of private worklists or private boards in sb presently, correct?
19:43:20 <zara_the_lemur__> we do, but I don't believe it overlaps with story permissions
19:43:44 <SotK> jpmaxman: correct
19:43:51 <fungi> ahh, right. i guess i haven't created a new worklist or board recently ;)
19:44:24 <SotK> its not quite as complete as for stories, you can't add teams yet
19:44:31 <zara_the_lemur__> yeah
19:44:31 <jpmaxman> well anyway if it was desired private projects seems the easiest of them all ;)
19:45:08 <SotK> what happens if a story has a task from a private project and a task from a public project?
19:45:12 <fungi> but anyway, as suggested i do agree that given sb is so lightweight to install and manage, projects that want entirely private defect/task tracking can have dedicated trackers pretty easily
19:45:25 <SotK> fungi: +1
19:46:10 <zara_the_lemur__> one can have a private worklist or board. one can also have a public worklist featuring private stories if one can see those stories, and those items in the worklist will only appear to others with permissions to see those stories.
19:46:37 <zara_the_lemur__> ^ just adding for completeness on the current soa
19:47:00 <fungi> cool, so there's a fair amount of flexibility
19:47:26 <jpmaxman> ok cool much thanks for the info - and yes seems very flixible
19:47:42 <zara_the_lemur__> (sotk wrote all boards and worklists things with no permissions originally, then ended up effectively rewriting the whole implementation, so we remember it well xD)
19:47:56 <diablo_rojo> jpmaxman, did you still want us to send some work items your way?
19:48:16 <jpmaxman> you're welcome too - would help to get familiar with it
19:48:31 <jpmaxman> right now we are working on some comps for possibly adding time tracking to story board
19:48:40 <jpmaxman> hopefully should have something to share next week
19:48:42 <diablo_rojo> SotK, zara_the_lemur__ anything off the top of your head you want help with?
19:48:50 <diablo_rojo> *heads
19:49:00 <fungi> down the road for vmt needs, i'm leaning toward adding a custom reporting form as a separate rethemed storyboard-webclient. that might allow us to simplify reporting of new potential vulnerabilities while reducing risks of reporting them incorrectly/unsafely
19:49:55 <zara_the_lemur__> makes sense
19:49:59 <fungi> actually getting teh feeling we'll end up with several storyboard-webclient instances sharing one api server eventually
19:50:10 <zara_the_lemur__> I would really like there to be multiple frontends
19:50:20 <diablo_rojo> Ten min left btw
19:50:36 <zara_the_lemur__> thanks
19:51:04 <zara_the_lemur__> I don't have anything specific; priorities for us are fixing migration scripts and merging patches currently in review
19:51:18 * SotK also has nothing specific off the top of his head
19:51:30 <zara_the_lemur__> I don't have a lot of bandwidth and can't take more on anyway
19:51:57 <diablo_rojo> Okay well I can look into open items and find some things
19:52:23 <zara_the_lemur__> (so if people send a ton of patches, they'll have to wait to get attention from me, so I'd feel weird soliciting them personally.)
19:53:03 <zara_the_lemur__> I'd like there to be more reviewer bandwidth and bugfixes in general
19:54:14 <fungi> hopefully as more people get involved proposing and reviewing changes, we'll find some you feel comfortable sharing core review responsibilities with
19:54:25 <SotK> indeed
19:54:27 <zara_the_lemur__> +1
19:55:54 <zara_the_lemur__> it's a project that takes a long time to ramp up on
19:56:00 <zara_the_lemur__> well, that's probably true for a lot of projects
19:56:04 <diablo_rojo> Agreed
19:56:17 <diablo_rojo> I feel like I dont know even a quarter of everything there is to know
19:56:41 <fungi> i feel like that about everything i work on, if that's any consolation
19:57:00 <zara_the_lemur__> :D
19:57:10 <diablo_rojo> fungi, if you only know a quarter of everything I have no hope of getting anywhere near you.
19:57:55 <fungi> the socratic paradox
19:58:27 * zara_the_lemur__ hopes it doesn't end in hemlock
19:58:30 <zara_the_lemur__> we're out of time
19:58:33 <zara_the_lemur__> well, 1 min
19:58:48 <diablo_rojo> Xenos paradox? If you are the halfway point between me and where I want to be and you you keep moving, I will never make it :)
19:59:01 <zara_the_lemur__> #endmeeting