15:00:24 #startmeeting airship 15:00:28 Meeting started Tue Jan 7 15:00:24 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:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:31 o/ 15:00:32 The meeting name has been set to 'airship' 15:00:37 o/ hello 15:00:39 Hey everyone! Welcome to the first meeting of the year! 15:00:40 o/ 15:00:54 o/ 15:01:04 Here is the running agenda https://etherpad.openstack.org/p/airship-meeting-2020-01-07 15:01:17 Feel free to add to it. We'll give it a few for everyone to join 15:04:04 It looks like we just have a few announcements, then I'll turn it over to roundtable 15:04:12 #topic Special elections 15:04:14 o/ 15:04:44 The WC and TC both have an empty seat right now, and we are holding special elections this month. The nomination period is open right now 15:04:56 o/ 15:05:04 o/ roman_g howell 15:05:07 o/ 15:05:29 We are looking forward to using this as an opportunity to bring some fresh ideas to the committee! 15:05:50 The official email announcement 15:05:52 #link http://lists.airshipit.org/pipermail/airship-discuss/2020-January/000829.html 15:06:08 The guidelines for self-nomination and the election process 15:06:14 #link https://airship-election.readthedocs.io/en/latest/#airship-elections 15:06:31 Does anyone have any questions about the elections or anything they would like to add? 15:07:03 #topic Next Committee Meetings 15:07:25 The next working committee meeting is Jan 13th, and the next technical committee meeting is Jan 9th 15:07:42 Remember, these meetings are open to the public and are also recorded 15:08:06 At the end of the WC meeting, we open the floor to questions and comments from the community 15:08:21 I think the TC does something similar? alexanderhughes 15:09:06 dwalt: that's correct - the agenda is published in advance, with the last portion of the meeting for open discussions from the community - that being said we welcome opinions and feedback on the agenda as it occurs 15:09:31 alexanderhughes: that's awesome, thanks 15:09:39 #link https://wiki.openstack.org/wiki/Airship/Airship-TC 15:09:46 #link https://wiki.openstack.org/wiki/Airship/Airship-WC 15:10:03 The wiki pages above have historical and current meeting information, as well as committee rosters 15:10:19 #topic roundtable 15:10:39 That's it for announcements and agenda. Would anyone like to discuss other items? 15:11:17 Need help with https://review.opendev.org/#/c/694817/ - some python skills are needed 15:11:19 there were patchsets in flight to add the committee election results to opendev but they were lingering for several months 15:11:36 Do you have the link for those handy? 15:12:00 while they're infrequent I do think it's a good time to think about the process to get those updates pushed/reviewed promptly 15:12:08 The election repository seems to have an outdated core list. mattmceuen is away right now, but I will ask him about updating the repo to the committee lists when he returns. 15:12:27 agreed 15:12:28 #link https://review.opendev.org/#/c/689245/ 15:12:39 I think we can solve that by updating the core list 15:13:30 agreed, just need more eyes and to remove Chris from the list since he no longer works on upstream dev 15:14:11 Thanks for the link. Since that one also belongs to mattmceuen, I'll add that to his stack of items for tomorrow :) 15:14:26 Alan Meadows alanmeadows is Elections core, he can add +2 15:14:39 I believe he is also out of office at the moment, roman_g 15:14:53 I've been bugging poor Rodolfo to merge my election changes 15:15:33 roman_g: Would you mind explaining the help you need on 694817? 15:16:43 wrong URL, sorry. This one https://review.opendev.org/#/c/694776/ 15:17:12 I have been asked to define an extensible format for the yaml, as a parameter 15:17:55 I'm not sure I would do it good, so I would appreciate someone to see over my shoulder what I would be suggesting 15:18:21 so that I wouldn't submit some completely wrong code 15:19:28 Does this change add support for linking to GitHub issues? 15:19:44 Partially yes. 15:19:55 This is one of a few patches. 15:22:05 That's it. Next topic? 15:22:10 I'm a little confused why adding a single key, like you did, wouldn't be enough 15:22:25 dwalt: they want to make it extensible. 15:22:51 I'll add myself as a reviewer and keep track of it 15:23:10 #topic reviews 15:23:24 A few review requests today: 15:23:30 #link https://review.opendev.org/701023 15:23:37 #link https://review.opendev.org/701025 15:23:44 #link https://review.opendev.org/#/q/status:open+project:airship/airshipctl+NOT+message:WIP 15:23:59 Please add these to your review queue! Anything else before we close? 15:24:21 Two requests for review above are mine and are quite small. 15:25:00 Indeed, thanks for the fixes roman_g 15:25:12 I would encourage everyone to review and give +1/+2 or other marks. 15:25:13 airshipctl development is ramping up, but work is lingering. any reviews that can be given are helpful and we are in need of more cores for airshipctl if you have an interest in being a core meaningful code reviews are the way to get there 15:25:48 ++ to both, thanks guys 15:26:10 I agree. Doesn't matter if you are core or not - do tests and the reviews, please. 15:26:20 Ahmad Mahmoudi proposed airship/drydock master: [NCEI-1685] - Used apt-get istead of apt https://review.opendev.org/701386 15:26:47 Yep. I think that's a wrap, thanks everyone! Have a good day. 15:26:50 #endmeeting