19:02:26 <SotK> #startmeeting storyboard
19:02:27 <openstack> Meeting started Wed Apr 18 19:02:26 2018 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:02:28 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:02:31 <openstack> The meeting name has been set to 'storyboard'
19:02:56 <SotK> #link https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda
19:03:03 <SotK> #topic Announcements
19:03:34 * diablo_rojo was too slow updating the agenda so... winging it?
19:04:11 <SotK> that is my usual approach to such situations
19:04:45 <diablo_rojo> I'll do better next time!
19:04:52 <fungi> i got teh gerrit service on review.openstack.org leaving comments on stories in storyboard.openstack.org as of saturday
19:04:58 <SotK> \o/
19:05:03 <SotK> thanks for fixing that
19:05:05 <diablo_rojo> I saw its working already which is awesome!
19:05:14 <diablo_rojo> I will give Senlin the heads up that its not an issue anymore
19:05:16 <fungi> turned out to just need configuration updated for gerrit 2.13/newer its-storyboard plugin
19:05:22 <diablo_rojo> or whichever project that was
19:05:34 <diablo_rojo> Easy fix.
19:05:37 <fungi> #link https://review.openstack.org/561342 Comment on linked stories for review state changes
19:05:50 <fungi> that was the patch which ultimately did it
19:06:58 <SotK> nice
19:07:04 <SotK> we also had some more migrations right?
19:07:22 <diablo_rojo> Not only will it unblock a project- it also removes one of the things on our 'blocking migration' tag list
19:07:27 <diablo_rojo> SotK, yes we did!
19:07:41 <diablo_rojo> OpenStackSDK OpenStackClient (thanks fungi again)
19:09:07 <SotK> \o/
19:09:07 <diablo_rojo> And I think TripleO- validations squad?
19:09:15 <fungi> yes
19:10:12 <SotK> #topic Migration Updates
19:10:18 <SotK> speaking of migrations...
19:10:37 <SotK> do we have more lined up?
19:10:46 <diablo_rojo> I started rerunning test migrations that had previously failed for the lack of utf8mb4 support and so far they are all passing
19:10:57 <SotK> that is good news
19:11:13 <diablo_rojo> SotK, as of right now for this week I don't think so (aside from maybe another TripleO squad if we can figure that out)
19:11:28 <diablo_rojo> I need to circle back to a few that said they were basically ready to go- Barbican comes to mind
19:11:41 <diablo_rojo> I just need to go door knocking again.
19:13:20 <diablo_rojo> Progress can still be followed here:
19:13:23 <diablo_rojo> #link https://storyboard.openstack.org/#!/board/45
19:13:41 <diablo_rojo> Also, was thinking it might be time to dust off the release goal and propose it for Stein soon?
19:14:24 <SotK> I think that could make sense, I feel like we have some momentum now at least
19:15:18 <diablo_rojo> Much more than we did last round at least.
19:15:25 <SotK> yep
19:15:41 <diablo_rojo> I don't think there is a ton to update other than the individual project stuff.
19:16:43 <SotK> #topic In Progress Work
19:17:36 <diablo_rojo> There are a lot of patches out there waiting for another +2 :)
19:18:18 <diablo_rojo> Went ahead and updated the project creator to stop telling new projects to use launchpad too
19:18:21 <diablo_rojo> #link https://review.openstack.org/#/c/561753/
19:18:53 <fungi> now that i'm done figuring out the story commenting i was going to work on getting stories indexed in web search engines, but mordred pointed out that the angularjs migration once complete will allow us to make use of their "universal" server-side rendering
19:19:00 <fungi> #link https://universal.angular.io/ Angular Universal
19:19:15 <SotK> heh, I will do my best to provide some +2s at some point
19:19:58 <diablo_rojo> fungi, thats convenient- lessens the workload for us right?
19:20:16 <fungi> in theory, but only if we get through the angular refactor
19:21:17 <diablo_rojo> SotK, no worries, should be a bunch of easy things if you get some spare time :)
19:21:35 <SotK> yeah, universal will be nice I think if we can somehow find time to convert to modern angular and verify that nothing broke
19:22:54 <diablo_rojo> Heh
19:23:06 <fungi> or at least that nothing _new_ broke ;)
19:23:15 <diablo_rojo> Good point :)
19:23:19 <SotK> heh, true
19:23:32 <SotK> I plan to actually do some useful things this week, such as fix the project selection bug that practically everyone hits
19:23:46 <diablo_rojo> SotK, +1
19:23:49 <fungi> SotK: oh that will be awesome if you get to it. thanks!!!
19:24:02 <SotK> and also look at fixing the board issues that were encountered the other day
19:24:29 <fungi> people who are using sb regularly get used to the project selection quirk once they know about it, but new users reporting bugs on projects they're using won't really be likely to figure it out
19:25:15 <SotK> yeah, it seems like the kind of thing that's really frustrating for new folk and leaves a bad first impression
19:25:40 <diablo_rojo> +2 for fixing things that leave bad impressions
19:26:34 <SotK> the boards issues were less "bad first impression" bugs and more "this makes boards really annoying" issues
19:27:08 <fungi> so anyway, aside from lifting the robots.txt and seeing if google manages to index stories (because unlike most other search engines they apparently have javascript savvy crawling implemented) i'll probably start looking next at the testing issues which are blocking fixing the private story e-mail notifications
19:27:56 <diablo_rojo> Sounds like a good plan to me.
19:28:00 <fungi> not that i have any expectation i'll be able to figure them out, but they seem important
19:28:34 <diablo_rojo> Our intern should get notification they were selected the end of the week so hopefully will have a few more hands helping out
19:28:42 <SotK> also sounds like a good plan to me
19:29:10 <diablo_rojo> fungi, investigation helps even if you can't figure out how to fix it yet
19:29:46 <fungi> right, at least i might suss out a little more and we can give someone additional context
19:30:12 <diablo_rojo> SotK,  if you can get that one patch that just explains the private tag in the webclient merged I can reach out to glance and we could migrate them Friday probably
19:30:45 <SotK> sure, I'll look at that tonight
19:31:43 <SotK> (I'm aware I've said similar for about a month but I actually have my test instance on my lap now)
19:32:39 <diablo_rojo> Ha ha ha no worries. We know you don't do this for your dayjob anymore.
19:32:58 <SotK> :)
19:34:02 <SotK> anything else in progress?
19:34:02 <diablo_rojo> What else we got going?
19:34:08 <diablo_rojo> Don't think so.
19:34:39 <fungi> i noticed that its-storyboard doesn't have a feature to assugn/unassign tasks on change state transitions
19:35:05 <fungi> probably a high-ish priority but will require someone with some java smarts
19:35:23 <fungi> #link https://gerrit.googlesource.com/plugins/its-storyboard/ Plugin to integrate with the Storyboard Issue Tracking System
19:35:56 <fungi> sounds like the necessary account query filter by openid might already be implemented in the storyboard api
19:35:58 <diablo_rojo> fungi, ah yes :) That would be good. Also good work containing your excitement
19:37:03 <fungi> so we'd just need something which could use the openid gerrit has on hand for the committer id to figure out to whom it needs to assign a corresponding sb task on active states, and unassign on a transition to abandon state
19:38:07 <diablo_rojo> Seems pretty simple...but I also would have to look back through my java text books lol
19:39:37 <SotK> yeah, sounds pretty doable, it just needs us to find someone enthused about writing java
19:39:55 <fungi> there are a number of other its-.* plugins hosted in the same place, but i didn't spot any of them doing bug assignment or somilar so this may be breaking new ground as far as a plugin getting access to the account_external_ids table in gerrit
19:40:45 <fungi> hopefully that isn't somehow disallowed by gerrit's plugin interface, otherwise the rest should be straightforward i expect
19:44:03 <diablo_rojo> Makes sense.
19:44:11 <SotK> yep
19:44:14 <diablo_rojo> Hypothetically simple until you dig in :)
19:44:15 <SotK> hopefully it is possible
19:44:24 <SotK> anything else in progress?
19:44:49 <fungi> we can probably also lean on zaro__ with questions if we get stuck on that since he wrote the original plugin
19:45:52 <fungi> he's been really helpful answering my questions so far, anyway (thanks!!!)
19:46:51 <diablo_rojo> Noted :)
19:46:59 <diablo_rojo> Don't think so
19:47:54 <SotK> #topic Blocking Migration Stories
19:48:14 <diablo_rojo> Crossed one or two off the list this last week
19:48:35 <SotK> yep, nice work folk :)
19:49:26 <diablo_rojo> Can't remember what we have left to knock out- I remember a lot of them being sort of opinion-y
19:51:13 <SotK> I think most of the remaining ones are opinion-y or already in review
19:51:28 <diablo_rojo> Progress then!
19:51:49 <diablo_rojo> The irc bot would be cool- hopefully we can get an intern on that one
19:51:53 <fungi> search engine indexing and task assigning have the potential to turn into blockers depending on whether teams who are considering migration didn't know about them and didn't think to check
19:53:05 <SotK> hopefully we can get them addressed before that happens :)
19:53:48 <diablo_rojo> +1!
19:53:50 <fungi> here's hoping, yes
19:54:13 <diablo_rojo> Little do they all know they can see our public logs for these meetings :)
19:54:31 <SotK> :)
19:54:55 <SotK> #topic Open Discussion
19:55:12 <diablo_rojo> SotK, coming to vancouver? :)
19:55:16 <diablo_rojo> Please please please!
19:56:04 <fungi> in my opinion, any teams who are following the sb meetings are totally welcome to help us prioritize things
19:56:16 <diablo_rojo> Agreed.
19:56:27 <diablo_rojo> And welcome to help too if something is bothering them that badly :)
19:56:30 <fungi> maybe someone who likes to hack in java in their spare time will read it ;)
19:56:43 <SotK> fungi: +1
19:56:54 <SotK> diablo_rojo: idk yet, but most likely not I think
19:57:09 <diablo_rojo> SotK, someday
19:59:14 <fungi> it _is_ a really long trip from the uk
19:59:27 <diablo_rojo> Its true
19:59:31 <diablo_rojo> But still.
20:00:38 <SotK> yeah, it is really far :)
20:00:53 <SotK> anything else will need to be in #storyboard
20:00:56 <SotK> #endmeeting