15:00:14 <dwalt> #startmeeting airship 15:00:15 <openstack> Meeting started Tue Feb 4 15:00:14 2020 UTC and is due to finish in 60 minutes. The chair is dwalt. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:16 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:18 <openstack> The meeting name has been set to 'airship' 15:00:25 <dwalt> Hello all! 15:00:31 <mattmceuen> o/ GM/GE 15:00:42 <dwalt> Welcome. Agenda for today's meeting is here: https://etherpad.openstack.org/p/airship-meeting-2020-02-04 15:00:49 <srwilkers> o/ 15:00:52 <dwalt> Let's give it a few mins for other to join and add items 15:01:11 <michael-beaver> o/ 15:01:27 <roman_g> o/ 15:01:33 <ian-pittwood> o/ 15:02:18 <aaronsheffield> o/ 15:02:44 <alexanderhughes> o/ 15:02:58 <souradage> o/ 15:03:30 <dwalt> Let's go ahead and get started 15:03:33 <dwalt> #topic announcements 15:03:53 <dwalt> ICYMI: Our special elections for the vacant TC and WC seats are over 15:04:18 <dwalt> Joining the WC is ian-pittwood; joining the TC is Andrew Leasck 15:04:38 <dwalt> Thank you candidates and everyone for participating! 15:05:05 <mattmceuen> +1 15:05:09 <dwalt> #topic GitHub Issues: status & role-based access 15:05:14 <dwalt> mattmceuen: floor is yours 15:05:31 <mattmceuen> Hey thanks dwalt 15:05:46 <mattmceuen> just a small update on our migration to github issues for scope tracking 15:06:34 <mattmceuen> several folks (including dwalt0 have been doing some good initial work toward using ghissues, so first thing is I suggest folks start looking in there for work when there's interest/need 15:07:09 <alexanderhughes> link please? 15:07:09 <mattmceuen> next is, how are we going to manage elevated privileges to GitHub Issues 15:07:29 <dwalt> #link https://github.com/orgs/airshipit/projects/1 15:08:08 <mattmceuen> Things like, creating and assigning tags, deleting issues -- maybe closing issues too (I need to figure out the list) 15:08:36 <mattmceuen> I propose we simply take the aggregate of all airship core reviewers, and add them as "members" of the github airshipit organization 15:08:51 <mattmceuen> that will give them those rights across airship projects in GH Issues 15:09:11 <mattmceuen> I proposed this to the working committee last week, and they were good with it, so I wanted to broach with the wider community 15:09:38 <mattmceuen> The alternative would be to create specific groups in our github org, with membership specific to each individual project 15:09:54 <mattmceuen> But that sounds like a lot more work, for potential marginal benefit 15:10:12 <alexanderhughes> I think as an initial step all cores from all airship projects would be good, and refine later as needed 15:10:36 <mattmceuen> awesome, ++ to doing this incrementally 15:10:41 * mattmceuen made a great pun there 15:10:57 * alexanderhughes facepalms 15:11:03 <srwilkers> :D 15:11:20 * michael-beaver facepalms as well 15:11:24 <mattmceuen> lol it's dwalt's job to keep us on track, I absolve myself of that responsibility today 15:11:36 <dwalt> :) 15:11:41 <mattmceuen> anyway - that's all I had, please provide feedback on GH Issues as y'all get your feet wet 15:11:41 <alexanderhughes> so I was out last week on git migration, last I heard we were planning on abandoning what was in jira and just creating new stories - is that still the path forward? 15:11:53 <mattmceuen> yep that's exactly right alexanderhughes 15:12:02 <alexanderhughes> and we were leveraging flight plan meeting for those activities 15:12:06 <alexanderhughes> ok great ty 15:12:06 <mattmceuen> yep 15:12:12 <mattmceuen> welcome back :D 15:12:12 <dwalt> ++ 15:12:18 <alexanderhughes> thanks :) 15:12:35 <dwalt> Awesome. Anything else for the jira -> GH migration? 15:12:50 <dwalt> #topic roundtable 15:13:09 <dwalt> that's it for our planned agenda. Does anyone have anything else they'd like to bring before the larger team? 15:13:11 <alexanderhughes> just a quick note on jira-> GH, the flight plan meeting I mentioned (and others) are available on the airship wiki 15:13:13 <alexanderhughes> #link https://wiki.openstack.org/wiki/Airship 15:13:25 <dwalt> thanks alexanderhughes 15:13:35 <dwalt> we'll be meeting tomorrow :) 15:14:01 <jamesgu> @Matt, does a developer need to register for the Airship project (or org?) before assigning himself/herself a story? 15:14:41 <mattmceuen> jamesgu: I believe (let me know if I'm wrong, anyone) that anybody can create an issue, anyone can submit patches against an issue, anyone can comment on an issue 15:15:05 <jamesgu> thx for clarification. 15:15:07 <mattmceuen> being a member of the org lets you do additional things like, assign an issue, modify issue metadata (labels), and things like that 15:15:41 <jamesgu> wait, so needs to be a member to assign self an issue? 15:16:23 <mattmceuen> I believe so, although I think we want to look into whether that's configurable behavior 15:16:33 <mattmceuen> seems a little weird 15:16:38 <dwalt> That's correct. I haven't found a way to make that open to the public 15:17:05 <mattmceuen> dwalt is there a normal way for someone to "volunteer" for an issue? A comment saying "I volunteer for this issue"? 15:17:32 <mattmceuen> (where normal = github norms) 15:17:34 <dwalt> I think that's how most GitHub projects handle issues. I'd suggest we follow the same pattern 15:17:51 <mattmceuen> sounds like a place to start 15:17:53 <jamesgu> that'd be a little more difficult to find "my issues", but it can work 15:18:46 <dwalt> jamesgu: I think we'd still want to assign the issue out. Maybe a core could do that 15:18:51 <mattmceuen> yeah, agree 15:18:57 <alexanderhughes> sounds like an item to discuss at flight plan meeting -- maybe have one of the cores go through daily to assign issues based on the volunteer comments 15:19:39 <mattmceuen> yep, we'll need to add to our list of "core responsibilities". Andy S (not here I think) volunteered to work on some documentation for that kind of thing 15:19:56 <jamesgu> +1 15:19:57 <dwalt> That's great 15:20:03 <dwalt> Do you know if he will be attending tomorrow? 15:20:32 <mattmceuen> good question, let me encourage him to :D 15:20:49 <dwalt> :D 15:20:58 <dwalt> #topic Reviews 15:21:32 <dwalt> roman_g is looking for some eyes on this one: https://review.opendev.org/#/c/701025/ airship/treasuremap Update 'airship' tool default Pegleg password and salt 15:21:42 <openstackgerrit> Narla Sandeep Narla Saibaba proposed airship/shipyard master: Adding apparmor profile to airflow pods https://review.opendev.org/705138 15:21:55 <dwalt> roman_g: Did you have anything to add about your other change? 694776 15:22:07 <roman_g> Thanks dwalt 15:22:39 <roman_g> dwalt: no, nothing. I still do need help with it. 15:22:54 <roman_g> Screen sharing session or something like this 15:23:47 <dwalt> Did we ever get word from the infra team if a nested YAML key would be "extensible"? 15:24:04 <dwalt> such as a.b=value; add more keys to a when necessary 15:24:44 <openstackgerrit> Merged airship/treasuremap master: Update 'airship' tool default Pegleg password and salt https://review.opendev.org/701025 15:25:24 <roman_g> I've got only what is in that change. May be I have had a chat on IRC with them, but I don't remember. Too much time has passed. 15:27:18 <dwalt> I see. Is that a reasonable first step? Without a strict format to follow, I'd be worried about spending a lot of time on something that may not be what the infra team has in mind 15:28:41 <roman_g> Could be. 15:29:51 <dwalt> Great. If we have an answer tomorrow, we can proceed at the flightplan meeting 15:30:28 <dwalt> For anyone who hasn't been following this: Roman made a change to gitea that supports linking to additional "issue trackers" 15:30:35 <dwalt> #link https://review.opendev.org/694776 15:31:27 <roman_g> aaronsheffield: thank you for merging my PS. 15:32:03 <dwalt> Any final thoughts, team? I think we've covered everything on the agenda 15:32:20 <mattmceuen> nothing from me! 15:33:37 <dwalt> Sounds good. Thanks for joining all; have a great day! 15:33:40 <dwalt> #endmeeting