15:02:28 #startmeeting Modularity Team Meeting 15:02:28 Meeting started Tue Dec 10 15:02:28 2019 UTC. 15:02:28 This meeting is logged and archived in a public location. 15:02:28 The chair is langdon. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:28 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:02:28 The meeting name has been set to 'modularity_team_meeting' 15:02:35 #meetingname modularity 15:02:35 The meeting name has been set to 'modularity' 15:02:43 #topic Roll Call 15:02:49 #chair contyk sgallagh 15:02:49 Current chairs: contyk langdon sgallagh 15:03:06 .hello2 15:03:07 sgallagh: sgallagh 'Stephen Gallagher' 15:03:42 .hello2 15:03:43 langdon: langdon 'Langdon White' 15:05:29 anyone else around? merlinm, contyk? 15:05:35 sgallagh: is contyk afk today? 15:05:59 Not as far as I know 15:06:17 .hello2 15:06:20 merlinm: merlinm 'Merlin Mathesius' 15:06:41 .hello psabata 15:06:42 contyk: psabata 'Petr Ĺ abata' 15:06:57 ok.. let's move to agenda 15:07:02 #topic agenda setting 15:07:24 i assume we should go through tickets.. but does anyone have anything else? or a particular burning ticket? 15:08:18 langdon: Could you summarize the meeting about the alternate proposal from last week? 15:08:25 For those of us who were unable to attend 15:08:52 sgallagh: ohh shoot.. i forgot to send out the notes didn't i? 15:09:01 * sgallagh wants to know if we're scrapping this project or not :-/ 15:09:06 let's table it as a i have "actual" meeting notes 15:09:10 * contyk can find the link 15:09:13 i think it ended better than that 15:09:19 i have it 15:09:31 https://meetbot.fedoraproject.org/fedora-meeting-3/2019-12-05/modularity.2019-12-05-15.01.html 15:09:45 ill info it in a sec 15:09:46 sgallagh: I think we agreed to continue with what we have 15:09:57 improving gradually 15:10:12 i would propose we do #168 and the #169 and then see if we can get ot anything else 15:10:16 so... 15:10:17 ok 15:11:11 #topic Review of RFC Modularity Simplified meeting 15:11:24 #action langdon to send out the minutes 15:11:27 #link https://meetbot.fedoraproject.org/fedora-meeting-3/2019-12-05/modularity.2019-12-05-15.01.html provides a summary 15:11:36 #link https://meetbot.fedoraproject.org/fedora-meeting-3/2019-12-05/modularity.2019-12-05-15.01.html link to the minutes 15:11:40 ohh ha 15:11:57 let's revisit at "open floor" if we want to discuss. 15:12:04 then if anyone wants to skim now they can 15:12:25 #topic #168 some thoughts on modularity docs (https://pagure.io/modularity/issue/168) 15:12:38 whats the zodbot title trick? 15:12:58 It's just #topic 15:13:27 yeah.. i meant to get zodbot to detail the title from a pagure issue numebr.. but i suppose that doesn't help in the #topic 15:15:06 ok.. from my read, this is a punch list of docs comments/updates.. we should probably assign it and /or break it up in to different people's work 15:15:07 .modularity 168 15:15:08 sgallagh: Issue #168: some thoughts on modularity docs - modularity - Pagure.io - https://pagure.io/modularity/issue/168 15:15:12 ah ha 15:15:49 does anyone see anything invalid (like "wrong" not like "oh, that's doc'd over here") 15:16:52 I can take these on if it can wait until the new year. 15:16:54 or any other comments? 15:17:35 i may try and attack them before the new year.. so maybe ill break out a new ticket for each one i do? or something? 15:17:43 langdon++ 15:17:43 ill describe it in a comment when i start 15:17:56 ok.. should we move on? 15:18:45 * langdon continues to have fun with the bad ff that doesn't work with extensions 15:18:56 ok.. im switching topics 15:19:05 .modularity 169 15:19:07 langdon: Issue #169: Security vulnerabilities (CVEs) are not properly tracked in modular packages - modularity - Pagure.io - https://pagure.io/modularity/issue/169 15:19:14 #topic Issue #169: Security vulnerabilities (CVEs) are not properly tracked in modular packages - modularity - Pagure.io - https://pagure.io/modularity/issue/169 15:19:27 #undo 15:19:27 Removing item from minutes: 15:19:53 #action langdon to review ticket and start working on doc updates; sgallagh to contribute post jan 1 15:19:56 #topic Issue #169: Security vulnerabilities (CVEs) are not properly tracked in modular packages - modularity - Pagure.io - https://pagure.io/modularity/issue/169 15:20:57 this seems like something we should have a plan for or is this a bug? 15:21:27 I believe this is being tracked in a RHEL ticket 15:21:30 Let me see if I can find it 15:22:24 ok 15:23:18 Sorry, taking longer than expected. 15:23:22 Still looking 15:23:58 would jeopardy music help? 15:25:03 Sorry, I can't find anything except an internal email thread 15:25:09 weird 15:25:14 I thought there was an associated ticket, but it's not mentioned. 15:25:27 So probably we should create one, since it's definitely important for RHEL 15:25:41 you don't think so for fedora? 15:25:43 for both distros :) 15:25:48 ohh ok 15:25:57 * langdon was confused for a min 15:25:58 security procedures need to be updated 15:26:27 so.. is this sufficient for fedora? or do we need a "do this please" ticket? rather thna one pointing at the problem? 15:26:53 no, we need Fedora security to report and track these just like they track non-modular content 15:27:36 Right, I didn't mean "not important for Fedora", just that it's "very important for RHEL" (and therefore has a better chance of getting resourced) 15:27:51 contyk: yeah.. so do we need to "design" that and file a ticket for them to start doing it? or is it just "start doing it now, please" ticket? 15:29:29 maybe we need to open a discussion with f-security to start 15:29:36 any volunteers? 15:30:03 * sgallagh is actively avoiding putting anything new on his plate this week 15:30:23 ha.. ok 15:30:42 ill "file a ticket" and ask for a meeting post jan 1? 15:30:55 like start the discussion 15:31:00 If someone else wants to get to it, that's fine with me 15:31:20 * langdon feels like this is a conversation we already had.. but.. must be crazy 15:31:25 I've just only got three and a half working days left in 2019 and several things I need to sew up 15:32:02 sgallagh: pfft.. you have merlin taking one already! ;) 15:32:28 ok.. ill assign me the "do something with this" .. and we can revisit in a couple weeks 15:32:32 ack 15:32:46 contyk: do you have any comments/thoughts on this before i #action ^^ 15:33:03 I think it's a good plan 15:33:08 ok.. cool 15:33:10 file a ticket and let's talk with them in January 15:33:28 #action langdon to follow up with fedora security and ensure a discussion can start in early jan 15:33:40 we definitely talked about content visibility to teams such as security and how they can identify what packages are provided and by what 15:33:46 but that might be it 15:33:52 there's another ticket like that in our queue :) 15:34:06 contyk: sgallagh who will follow up with rhel? do you want me to "file that ticket" too? 15:34:12 contyk: lol' 15:34:28 langdon: Yes, please 15:34:34 sgallagh: ack 15:34:34 yes 15:34:42 * langdon adds to other to do list 15:35:25 ok.. 15:35:28 gonna move now 15:35:42 .modularity #167 15:35:42 langdon: Error: '#167' is not a valid integer. 15:35:45 .modularity 167 15:35:46 langdon: Issue #167: Publish drafts/module-tagging-service/format.md - modularity - Pagure.io - https://pagure.io/modularity/issue/167 15:36:00 #topic Issue #167: Publish drafts/module-tagging-service/format.md - modularity - Pagure.io - https://pagure.io/modularity/issue/167 15:36:25 thoughts? 15:38:25 i think we have to follow up with the "team formally known as factory-2" right? 15:39:16 or not.. i am not sure.. 15:40:44 oh, that's my doc 15:40:46 I think 15:42:08 contyk: what would you like to do? do you want me just to assign it to you? 15:44:51 langdon: I think so, assign it to me 15:45:07 ok 15:45:29 * langdon lost his winder 15:45:32 *windo 15:45:34 *window 15:46:34 #action assigned to contyk 15:46:47 .modularity 166 15:46:48 langdon: Issue #166: Everything reference repository definition - modularity - Pagure.io - https://pagure.io/modularity/issue/166 15:46:58 #topic Issue #166: Everything reference repository definition - modularity - Pagure.io - https://pagure.io/modularity/issue/166 15:47:26 this is the issue i made the other day.. i would just like contyk, sgallagh, merlinm to give it a read and see if you have anything to add 15:48:40 I don't have anything to add until a first draft is made 15:49:24 ok 15:49:39 Yup. That ticket is sufficiently vague. 15:50:00 i meant like any other "content that may not be easily available" that we would want in the "special repo" that we hadn't thought of yet :) 15:50:07 merlinm: you are welcome ;) 15:50:45 I can add some stuff as comments 15:50:50 like what it should include 15:51:24 yeah.. thats what i had in mind 15:51:29 i think i listed 2 things 15:51:44 ok.. 15:52:14 #action contyk to add some comments about any other content that should be included ("content that is not easily available") 15:53:02 ok.. skipping 165 15:53:13 .modularity 164 15:53:15 langdon: Issue #164: The orphan reporting needs to be adapted to cover modular cases - modularity - Pagure.io - https://pagure.io/modularity/issue/164 15:53:23 #topic Issue #164: The orphan reporting needs to be adapted to cover modular cases - modularity - Pagure.io - https://pagure.io/modularity/issue/164 15:54:33 this just looks likea chunk of work.. seems pretty straightforward.. do we have anything similar for rhel? should we? 15:55:10 "orphaned" isn't quite the right word for rhel.. but "wont be in the next release" might use a similar script 15:56:18 almost out of time.. sgallagh, contyk any thoughts? 15:56:42 langdon: Geez, if I start having thoughts that might be dangerous 15:57:07 sgallagh: lol.. especially this close to shutdown! 15:58:20 I had thoughts once 15:58:28 and look what happened? 15:59:01 exactly 15:59:23 ok.. well.. im gonna shut this thing down.. but I am curious if you think we need a rhel version of this ticket 16:00:28 #info no resolution at this point.. but seems like a legit ticket/issue 16:00:34 #endmeeting