19:00:27 <SotK> #startmeeting storyboard
19:00:27 <openstack> Meeting started Wed Mar 14 19:00:27 2018 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:28 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:00:30 <openstack> The meeting name has been set to 'storyboard'
19:00:39 <SotK> #link https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda
19:00:51 <diablo_rojo> I was just excited for the meeting I wanted to start an hour earlier.
19:01:03 <fungi> heh
19:01:05 <thingee> o/
19:01:45 <SotK> I don't think we have any announcements today
19:01:50 <SotK> #topic In Progress Work
19:01:55 <diablo_rojo> Release Management migrated?
19:02:51 <fungi> yup
19:03:28 <diablo_rojo> I have the migration script change to handle suspended users in LP up for review.
19:03:34 <fungi> #link https://storyboard.openstack.org/#!/project_group/73 release management team project group
19:03:57 <diablo_rojo> Yay!
19:04:01 <SotK> \o/
19:04:13 <SotK> I'm glad the migrations seem to be building up a head of steam
19:04:23 <diablo_rojo> Indeed :)
19:04:34 <diablo_rojo> Getting attention
19:04:53 <persia> I think the more that migrate, the more people get frustrated with not using Storyboard.
19:05:28 <SotK> we just need to get that frustration to outweigh the frustration of having to change tools :)
19:05:31 <diablo_rojo> Either way, I am happy we are making more and more progress.
19:05:43 <SotK> me too
19:06:07 <diablo_rojo> So in progress work? I have the migration script change and one small webclient change to make VMT/ Security things more verbose
19:06:14 <diablo_rojo> Would love some reviews :)
19:06:50 <SotK> I sent a big wall of patches at PTG, most of which are making the UI feel nicer to me in various ways, but some of which address actual issues other people have raised
19:07:28 <SotK> diablo_rojo: I'll try to find some time to review things soon, I've been busy with various things since PTG so far
19:07:33 <persia> The name vs. number and new lines in markdown issues came up in the cinder meeting.  Both have patches needing reviews.
19:07:35 <diablo_rojo> SotK, I think I have reviewed basically all of them, but will double check. I know there are a lot of things sitting in storyboard with one +2 on them.
19:07:43 <diablo_rojo> SotK, no worries.
19:08:40 <SotK> persia: I noticed that discussion, that also made me think that I should send a similar name vs number patch for project groups
19:08:47 <diablo_rojo> I will go through storyboard + webclient today and make sure everything I havent already looked at gets some attention before I go do anything else.
19:08:57 <persia> SotK: good idea
19:09:23 <fungi> when creating a new project group it prompts for a "url stub" but it's not entirely apprent to me what that gets used for
19:10:18 <SotK> fungi: off the top of my head I also have no memory of what that is used for
19:10:45 <persia> I think that might have been an incomplete feature to do project group overviews, mostly abandoned before the last DtoryBoard meeting in Vancouver.
19:11:16 <diablo_rojo> So something we could remove then?
19:11:36 <persia> I think if StoryBoard is part of a bigger thing (like OpenStack Infra or Software Factory), it could be removed.
19:12:35 <persia> I have not heard of anyone trying to build a do-everything system with StoryBoard as central in several years, so I think so.
19:12:55 <persia> If someone is doing that, they should be more visible :)
19:13:36 <SotK> if that is the case I agree we should remove it
19:13:58 <SotK> if anyone is secretly vehemently opposed to that they can complain
19:14:09 <diablo_rojo> *crickets*
19:14:27 <diablo_rojo> Other ongoing things, fungi how is the investigation about why gerrit stopped posting links on stories?
19:14:53 <fungi> i just didn't know whether the url stub it was an incomplete solution to human-readable project group names
19:15:47 <persia> I could misremember.  We should check the code before removing:)
19:16:04 <fungi> diablo_rojo: best hope at the moment is that the reason its-storyboard stopped commenting on stories is related to changes we may have made to the commentlinks settings in gerrit around the time we upgraded to 2.13, or that the its-base framework changed what it expects out of those commentlinks/gerrit configuration in general
19:16:14 <fungi> i haven't had time to test that hypothesis yet
19:16:47 <diablo_rojo> No worries :) Just wondered if there were updates.
19:17:10 <fungi> worse reasons may include regressions in gerrit or its-base between 2.11 and 2.13
19:17:27 <fungi> which is likely going to require deeper grokking of java than i can manage
19:17:46 <diablo_rojo> *fingers crossed its not that*
19:17:53 <fungi> yeah, tell me about it
19:18:15 <fungi> i also haven't had time to do the utf8mb4 table conversions on storyboard-dev yet
19:18:30 <diablo_rojo> I suppose we will cross that bridge if we get to it.
19:18:37 <fungi> to make sure i have the process down for subsequently doing the same on production
19:18:57 <diablo_rojo> fungi, its okay- the main reason for that is a few projects have users with emojis in their names
19:19:01 <fungi> i'd like to couple those with moves to newer mysql versions for the trove instances we're using
19:19:08 <SotK> yep, I'm sure we can find a Java fan somewhere if we have to
19:19:13 <diablo_rojo> so we need to support it to migrate them or handle them some other way
19:19:39 <diablo_rojo> But we have plenty of other projects to handle migrating right now :)
19:19:52 <SotK> indeed
19:19:59 <SotK> I think that brings us nicely to the next topic
19:20:14 <SotK> #topic Migration Updates
19:20:45 <diablo_rojo> Ironic has been test migrated.
19:21:01 <diablo_rojo> Migration will be announced at their meeting Monday for the following week I think.
19:21:18 <diablo_rojo> I am so excited to migrate them I can hardly stand it :)
19:21:54 <diablo_rojo> Manila also just finished migrating locally without issue so I will let tbarron know and he can decide how/when they want to proceed as well.
19:21:55 <SotK> yeah, it is very exciting
19:22:27 <SotK> I guess we probably want to get the "click this box for security bugs too" patch merged before then?
19:22:48 <fungi> i've already +2'd it
19:22:53 <diablo_rojo> Yeah that would be great
19:23:00 <diablo_rojo> Cause then Glance would be onboard to go too
19:23:38 <SotK> assuming they are happy trusting that people can follow clear instructions rather than the team automatically being added I guess
19:23:49 <fungi> on a related note, i'm working on drafting the zuul team's vulnerability management process, from which the storyboard specifics will likely inform the openstack vmt's support of projects using sb for their task tracking as well
19:24:31 <fungi> and we'll have some nice boilerplate prose explaining to users how to properly report suspected security vulnerbailities
19:24:48 <diablo_rojo> SotK, talked to the ex-PTL yesterday and he seemed to think it should be fine- will verify with the current PTL though
19:24:58 <diablo_rojo> fungi, that will be SUPER handy
19:25:29 <SotK> fungi: that sounds good :)
19:25:36 <SotK> diablo_rojo: oh, nice
19:26:03 <persia> Probably still worth being able to configure per-project-group security teams, but maybe at lower priority.
19:26:07 <diablo_rojo> I was in like 10 channels talking storyboard over the last two days
19:26:29 <diablo_rojo> persia, yeah each team will want to set up their own $project coresec group
19:26:30 <fungi> yeah, i mean we _can_ configure per-project-group security teams now
19:26:42 <fungi> it just requires them to get a storyboard admin to do that for them
19:26:50 <SotK> persia: yep, I definitely agree
19:27:07 <SotK> but "good enough" is a good place to start
19:27:15 <diablo_rojo> fungi, you were talking yesterday about that being something we could maybe define in project config and get imported into storyboard that way?
19:27:17 <fungi> which is not entirely ideal, but we have time to come up with some sort of automation for that before our sb admins are overrun with sb team change requests
19:27:19 <persia> Oh, I missed that.  Is it just the UI integration that is missing?
19:27:21 <diablo_rojo> So it doesn't have to be done by admins
19:28:20 <fungi> yeah, i was thinking just a piece of automation using an administrative-privilege account which queries the api for groups, compares them to a set of files in a git repo, and then adjusts the groups in sb to match
19:28:53 <fungi> er, s/groups/teams/
19:29:19 <diablo_rojo> That would be super awesome. Easy way for teams to control changes to the groups without needing us to make changes.
19:29:24 <persia> Oh, interesting.  I was thinking a config option that would be a default for a security checkbox.
19:29:55 <fungi> oh, gotcha. different needs there right
19:30:12 <SotK> persia: me too, I think being able to control team membership is one half of the issue, being able to mark a team as "coresec for $project" is the other half
19:30:14 <fungi> so making teh default security team choice a per-project-group setting would probably not work
19:30:19 <fungi> would need to be per-project i think
19:30:23 <persia> Why?
19:30:28 <fungi> because a single project can be in multiple groups
19:31:02 <fungi> so it may get confusing if your project belongs to groups with different default securit settings (unless we just merge the default and add them all?)
19:31:50 <fungi> i suppose that's a reasonable alternative as long as everyone (or at least the sb admins) understands how that works
19:33:03 <SotK> is there a good reason for going per-group rather than per-project?
19:33:14 <fungi> as an alternative to maintaining group membership in revision control and writing some sort of sync-up automation, i wonder if we could add a setting to a team which allowed anyone who is a member of that team to be able to see and modify its membership? that's basically how we treat self-managed teams in gerrit today for access control
19:33:52 <fungi> and probably easier than having team owner accounts which gets into more explicit role-based access control
19:34:21 <SotK> yeah I think that makes sense to have
19:34:43 <diablo_rojo> +1
19:34:51 <SotK> and certainly would be part of any "anyone can make a team and add folk to it" implementation in future anyway
19:36:07 <fungi> from a burden-to-the-admins perspective, i think being able to rely on admins to create groups and add an initial member to them is acceptable for now (again, we're doing that with gerrit anyway)
19:36:32 <fungi> er, s/groups/teams/
19:36:42 <fungi> gerrit calls them groups, so i keep confusing the terms
19:36:45 <SotK> I will make a story for this stuff after the meeting then
19:37:49 <fungi> for setting the default subscriber team for a project, i think we can probably manage that through revision control in the same place we put other project settings now (openstack-infra/project-config gerrit/projects.yaml) and just modify our manage-projects script to set that through the sb api (once such a setting exists)
19:39:35 <SotK> that seems sensible to me
19:39:37 <diablo_rojo> That sounds like a good approach to me
19:40:47 <fungi> we already use that today to say what project groups a project should belong to
19:41:41 <SotK> diablo_rojo: do we know when sahara and tripleo intend to begin migrating yet ooi?
19:42:35 <diablo_rojo> SotK, not currently. Reaching out to them to start doing that was on my todo list now that the script change has merged.
19:44:29 <SotK> cool, I'm looking forward to it happening
19:44:34 <diablo_rojo> Me too.
19:44:38 <diablo_rojo> So many migrations!
19:45:18 <SotK> anything else on the migration front?
19:45:28 <diablo_rojo> Don't think so
19:45:48 <SotK> #topic Outreachy intern?
19:46:00 <diablo_rojo> Yeah, so I know there is a call out for intern proposals
19:46:13 <diablo_rojo> And I know we have a lot of work to be done and most of it is small projects.
19:46:43 <diablo_rojo> I thought proposing some of the work- unit tests maybe would be a good idea for an internship?
19:46:58 <diablo_rojo> The only issue is that we need to commit like 5 hours of mentorship a week.
19:47:06 <diablo_rojo> Which is a lot for any one of us to handle.
19:48:14 <SotK> indeed, I certainly wouldn't want to commit to having 5 hours available myself for mentoring atm
19:48:23 <diablo_rojo> Me neither.
19:48:39 <diablo_rojo> But we could REAALLY use the extra hands on work.
19:49:01 <SotK> yeah...
19:49:14 <diablo_rojo> There is info about doing like co-mentorship
19:49:23 <diablo_rojo> like multiple people mentoring the same person
19:49:26 <SotK> that sounds more possible
19:49:36 <SotK> though most of my free time is at the weekends
19:49:57 <diablo_rojo> SotK, yeah and we have no way of knowing what tz the intern would be in
19:50:11 <diablo_rojo> weekends might not be an issue
19:50:15 <diablo_rojo> vkmc, around?
19:50:28 <diablo_rojo> (she is organizing outreachy the intern program)
19:50:36 <vkmc> o/
19:50:42 <diablo_rojo> Hey :)
19:50:46 <vkmc> hey :)
19:50:55 <diablo_rojo> Talking about a possible proposal for outreachy internship
19:51:01 <vkmc> that's great!
19:51:04 <diablo_rojo> So co-mentoring..
19:51:06 <diablo_rojo> thats cool?
19:51:30 <vkmc> main organizers put a deadline on internship ideas proposals
19:51:37 <vkmc> so... unless the idea is proposed today
19:51:44 <vkmc> I'm afraid we will need to wait til next round
19:51:48 <diablo_rojo> Cause we have like twoish + people that could all lend a little time, but no specific one that could dedicate 5 hours
19:51:50 <vkmc> I can help convincing them
19:52:02 <diablo_rojo> I miiiight be able to get something together- depending on the details needed.
19:52:05 <vkmc> is there people interested on working on the idea?
19:52:17 <diablo_rojo> Like mentees?
19:52:20 <diablo_rojo> or mentors?
19:52:36 <vkmc> like mentees
19:52:43 <vkmc> I'm understanding you have an internship idea and mentors
19:52:56 <vkmc> and that you would like to propose the idea
19:53:00 <diablo_rojo> Ah yeah no prospective mentees currently that I know of
19:53:07 <vkmc> but maybe you have people interested already
19:53:08 <vkmc> oh ok
19:53:10 <SotK> none that I am aware of either
19:53:15 <vkmc> so... we can try to get the idea accepted
19:53:27 <vkmc> deadline for applications is 29th March
19:53:44 <vkmc> (extended one, the real one is the 22nd March)
19:53:50 <vkmc> so we have time for people to apply
19:53:58 <diablo_rojo> Okay so need a prospective intern for it by then?
19:54:50 <fungi> go bang on empty kegs near the local university campuses and see who comes running
19:55:04 <diablo_rojo> Ha ha ha ha
19:55:50 <diablo_rojo> Thanks for the info vkmc :)
19:56:11 <diablo_rojo> So based on all of that...do we want to go for it? or wait till next round and maybe try then?
19:56:15 <vkmc> no need... we can spread the word and cross fingers to get mentees
19:56:18 <vkmc> thanks to you!
19:56:22 <vkmc> let me know if I can be of any help
19:56:47 <diablo_rojo> vkmc, I will let you know in a bit if I am throwing together a proposal today :)
19:56:53 <diablo_rojo> Will do!
19:57:18 <SotK> diablo_rojo: feel free to ping me if you decide to try and need any input :)
19:57:20 <fungi> the up side is any proposal you write up for this round will probably still be mostly viable for the next round too if we don't manage to get one now
19:58:01 <fungi> so not necessarily wasted effort even if we're turned down or can't find a suitable victim^H^H^H^H^H^Hmentee
19:58:43 <diablo_rojo> So sounds like I should try..?
19:59:01 <diablo_rojo> Would you two have an hour or two to donate to comentoriship with me?
19:59:07 <SotK> if you have time I think it would be good to try
19:59:12 <SotK> I can find an hour or two, yeah
19:59:20 <diablo_rojo> Okay cool.
19:59:45 <SotK> right we are about out of time
19:59:54 <diablo_rojo> Today turns into a writing day. I already had a super user post I had to write, but I will do this one first :)
20:00:11 <SotK> if anyone has anything else to chat about, come to #storyboard
20:00:14 <SotK> diablo_rojo: thanks!
20:00:15 <diablo_rojo> Let me start an etherpad and start throwing stuff in- if you both want to help that would be super awesome
20:00:25 <SotK> #endmeeting storyboard