14:33:27 #startmeeting Fedora DotNet (2018-09-06) 14:33:27 Meeting started Thu Sep 6 14:33:27 2018 UTC. 14:33:27 This meeting is logged and archived in a public location. 14:33:27 The chair is Rhea. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:33:27 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:33:27 The meeting name has been set to 'fedora_dotnet_(2018-09-06)' 14:33:33 #meetingname dotnet 14:33:33 The meeting name has been set to 'dotnet' 14:33:35 #nick dotnet 14:33:40 #chair aslice omajid 14:33:40 Current chairs: Rhea aslice omajid 14:33:47 .hello pcreech17 14:33:48 pcreech: pcreech17 'Patrick Creech' 14:33:50 #chair pcreech 14:33:50 Current chairs: Rhea aslice omajid pcreech 14:34:09 .hello aslice 14:34:10 aslice: aslice 'Andrew Slice' 14:34:13 Hi awesome people o.o 14:34:19 #topic Packaging progress / Open Floor discussion 14:34:22 .hello omajid 14:34:25 omajid: omajid 'Omair Majid' 14:34:33 So I have a bit of a question to open up with, about our workflow. 14:35:33 As it is right now kinda undefined, omajid submits a PR for the packages, I quickly go through it and merge it... Sometimes aslice pitches in, etc... 14:35:50 My question is, should I always wait with it for 3rd person to give a LGTM? 14:36:17 i.e. I could always ping for example you Andrew if you don't get notifications for those... 14:37:04 I think it would be good to have a 2nd person check off, but that could just as well be you radka (or any of us, really). 14:37:26 i think 1 okay is enough, unless it's a tricky patch or someone feels the need for additional feedback. 14:37:33 And I do get notifications when omajid makes PRs and issues. And I don't mind being the 'defacto' gatekeeper. ;) 14:37:41 Well I mean like, I do look at it, but I like if we need another person not just me 14:38:30 And that's fine, I was just saying that less complicated patches can have less scrutiny. 14:38:41 yup 14:39:16 Okay so I'll wait or poke for bigger changes and simply merge the small ones... 14:39:29 I usually look at it very soon after it's submitted... 14:40:01 Yeah, if you're willing to give a change a sign-off I don't mind you also merging it. So that sounds fine to me. 14:40:19 yup 14:41:27 Another kinda related question, I was playing with the idea of running the standard tests on copr, but didn't look into it... omajid is there an api where jenkins could always submit some test results in copr? And a trigger/webhook/whatever? Have you seen something like that before? 14:42:19 not of hte top of my head, but i can look at it 14:43:01 That's like low priority on my list what we could do for Fedora... 14:43:33 If it's not too much trouble, it would be nice to have. Otherwise I can just manually run the test every update. 14:44:03 (Just like rhel... we dont have it hooked up either) 14:46:44 Okay we'll get around to looking at that eventually :P 14:46:51 Anyone got anything they'd like to bring up? 14:48:04 not really 14:49:13 Okay then let's call it, thank you all :] 14:52:13 #endmeeting