2020-11-17T03:52:05 *** okurz_ is now known as okurz 2020-11-17T12:35:08 cboltz: hey, would it be possible to give myself and lcp maintainer privs for salt repo in GitLab? 2020-11-17T12:35:22 so that we can accept merge requests? 2020-11-17T12:35:48 that makes sense, no objections 2020-11-17T12:35:59 let me check if I have enough permissions to do that 2020-11-17T12:40:05 cboltz: you should be able to update our permissions in the infra group 2020-11-17T12:40:10 you have "maintainer" level privileges 2020-11-17T12:42:10 the only option I see in the infra group is a "Leave" button, which I won't try ;-) 2020-11-17T12:42:30 but I should be able to give you maintainer permissions in the salt repo 2020-11-17T12:42:53 (actually it will be an invitation, but that's a technical detail) 2020-11-17T12:44:11 looks like that worked :-) - lcp and you are now maintainers in the salt repo 2020-11-17T12:54:34 woot 2020-11-17T12:57:16 LCP: I've merged all outstanding MRs for pagure :) 2020-11-17T12:58:07 this brings the salt repo for pagure into the same state as the production machine, basically 2020-11-17T12:58:49 One of my siplemost webservices so far: http://myip.zq1.de 2020-11-17T12:59:13 haha 2020-11-17T13:00:16 cboltz: so now there's a manually managed mirror of the salt repo here: https://code.opensuse.org/heroes/salt 2020-11-17T13:00:33 you'll need to log into code.opensuse.org so that I can grant you membership in the heroes group to see it 2020-11-17T13:00:37 since it's still private for now 2020-11-17T13:01:25 login done 2020-11-17T13:01:49 added you to the heroes group 2020-11-17T13:01:52 you should now be able to see it 2020-11-17T13:02:12 yes, thanks 2020-11-17T13:03:00 is there a reason we want to keep this repo private? 2020-11-17T13:03:11 I looked through it and didn't see any unencrypted secrets in it 2020-11-17T13:04:22 we even have a doc that says we should treat this repo as public, and secrets should be managed accordingly 2020-11-17T13:05:07 I think we had this discussion before ;-) 2020-11-17T13:05:33 personally I don't see a problem with making it public, but I also remember a few different opinions 2020-11-17T13:05:37 I had to duck out last meeting so I don't know if it was discussed again 2020-11-17T13:06:00 IIRC not in the last meeting 2020-11-17T13:06:06 ah okay 2020-11-17T13:06:58 do we know how ci.opensuse.org is governed and managed? 2020-11-17T13:07:43 the next step is porting over the CI to ci.opensuse.org 2020-11-17T13:07:53 I don't, but jdsn and/or bmwiedemann should know 2020-11-17T13:08:44 I have to leave, see you later! 2020-11-17T13:10:27 cboltz: bye 2020-11-17T13:15:06 Eighth_Doctor: I mostly keep ci.o.o updated. We probably keep it on the SUSE side, because there are some product-related workflows going on that we just want publicly visible 2020-11-17T13:15:25 bmwiedemann1: that's perfectly fine 2020-11-17T13:15:44 I just want to be able to connect ci.opensuse.org with code.opensuse.org :) 2020-11-17T13:16:01 unless someone thinks we need another jenkins instance... 2020-11-17T13:21:31 good question. I guess, we can trigger remote workers from ci.o.o 2020-11-17T17:02:07 *** ldevulder_ is now known as ldevulder 2020-11-17T21:25:48 lcp: a reason to keep FF and friends https://nitter.net/nsatragno/status/1328803698227650560 2020-11-17T21:29:07 I'm not saying you can run it for yourself, I don't actually think anybody lives in the nbg datacenter though? 2020-11-17T21:29:45 but we heat the garage!