13:00:44 #startmeeting Container SIG 13:00:44 Meeting started Mon Oct 8 13:00:44 2018 UTC. 13:00:44 This meeting is logged and archived in a public location. 13:00:44 The chair is cverna. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:44 Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:00:44 The meeting name has been set to 'container_sig' 13:00:59 #topic Roll Call 13:01:55 .hello2 13:01:56 lorbus: lorbus 'Christian Glombek' 13:02:50 heya 13:03:19 o/ 13:03:21 #chair jlanda lorbus 13:03:21 Current chairs: cverna jlanda lorbus 13:03:29 o/ 13:03:46 let's wait another minute or two 13:05:34 ok moving on 13:05:54 is here 13:06:05 hi jcajka ;) 13:06:30 #topic Action items from the last meeting 13:06:35 #topic Action items from the last meeting 13:06:37 :) 13:06:43 #chair jcajka 13:06:43 Current chairs: cverna jcajka jlanda lorbus 13:07:17 So from last meeting I was supposed to play with container.yaml in order to control the tags created by OSBS 13:07:26 for https://pagure.io/ContainerSIG/container-sig/issue/2 13:08:16 did not look at it yet, so this is still to be done 13:09:20 I was going to investigate around the fedora-toolbox container 13:09:24 this morning I looked at the format of container.yaml and it will look like that https://paste.fedoraproject.org/paste/4ST8WVGwf3ogj~NwGTIThw 13:09:35 jlanda: go on 13:09:36 i closed the issue since team silverblue 13:09:53 team silverblue is actively working on it 13:10:06 and we were just tracking their work ;) 13:10:34 and silverblue users are the main usertarget for the container 13:11:01 yeah I think that was a good call, the fedora-toolbox container seems a bit tricky to used tho but yeah it maybe makes sense in silverblue 13:11:28 they're working on some scripts to build and run the container 13:11:34 it'll be easy to use ;) 13:12:35 you jest need to know that there are some script to use with it :) 13:12:51 anything else on the last meeting updates ? 13:13:11 yeah, but once they have a working environment we can just document the usage way ;) 13:13:40 sounds good 13:13:44 #topic Tickets 13:14:03 #link https://pagure.io/ContainerSIG/container-sig/issues?status=Open&tags=meeting 13:14:35 # Ticket Remove the $FGC from the container name https://pagure.io/ContainerSIG/container-sig/issue/2 13:15:03 so we discussed this one last time not much to add to it, are we ok to remove the meeting tag ? 13:16:18 I take that as a yes :) 13:16:34 yeah 13:16:39 yup 13:16:56 # Ticket https://pagure.io/ContainerSIG/container-sig/issue/10 13:17:46 Same here, I would be tempted to just close this ticket for now and open a new one once there is a solid proposal to make this happen 13:18:00 last week we reach the quay.io pushing thing starting from there 13:18:11 agreed 13:18:14 ack 13:18:26 +1 13:19:06 jlanda: yes, I think the quay.io push was still not tested unfortunately 13:19:23 jlanda: I ll check with releng to see if that can happen :) 13:19:25 ok, np ;) 13:20:42 # Ticket https://pagure.io/ContainerSIG/container-sig/issue/13 Resolve github.com/container-images 13:21:34 I don't remember looking at this once last meeting, we can try to look at it and add questions if needed in the ticket 13:21:54 we pass all the ttomecek's issues since he was out 13:22:10 dunno if he is back ;) 13:22:55 no I think he is still on PTO 13:22:55 I'd be interested in some of those, e.g. postfix and dovecot 13:23:17 and I think the template one would be good to have, if it adheres to our guidelines 13:23:38 So I think there are 2 aspect of this, the first one is to move https://github.com/container-images/container-image-template 13:23:54 under the SIG group in pagure.io if I understand it correctly 13:24:12 I think that the template one can be a good sig project, the rest... would need individual maintainers 13:24:21 that'd be great, yes 13:24:21 then there is the case for the other repos 13:24:47 anybody wants to look at creating the repo in pagure ? 13:25:20 I can clone the github one to pagure later 13:25:30 there are just 7 issues, 6 closed on gh 13:25:35 maybe ttomecek should do it. I think he said he wanted to keep maintaining the template anyway? 13:25:57 but sure, moving it shouldnt be a problem 13:26:06 we can wait to him ;), as you want 13:26:25 I think we can create the clone in pagure.io and then sync with ttomecek when he comes back 13:26:34 cverna +1 13:27:10 I think all the group member should be able to create new repos under https://pagure.io/group/ContainerSIG 13:27:28 let me know if that's not the case, I ll try to find the good settings 13:28:27 ok, I'll clone the repo from gh tonight if no one clones it before 13:29:02 thanks 13:29:15 jlanda++ 13:29:16 lorbus: Karma for jlanda changed to 5 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 13:29:29 lorbus: then for the images you are interested with I think it is best to sync with ttomecek 13:29:51 ok, will do that once he's back then 13:30:27 lorbus: I think they have a bot that does the sync between github and dist-git automatically so maybe keeping the image in github and deploying the bot in fedora-infra would be something nice to do 13:31:14 cverna: so not dissolving the gh org? 13:31:43 I am not sure, we need ttomecek to clarify that 13:31:54 :) 13:32:00 ok :) 13:32:08 anybody know when he'll be back? 13:32:23 dissolving will lost the linking. I read somewhere to ttomecek about marking them as deprecated and pointing to pagure 13:32:33 I think that will be the best solution 13:32:53 jlanda that sounds sensible to me 13:32:56 I think he had 3 weeks of PTO 13:33:11 this mtg is bi-weekly, right? 13:33:12 so I guess he should be back next week 13:33:16 yes 13:33:26 ok, perfect. just added it to my calendar :) 13:33:32 A little off topic: I joined RH last week as an intern on the FCOS Community & Tools team in Berlin =) 13:33:35 ok next 13:34:02 # ticket https://pagure.io/ContainerSIG/container-sig/issue/14 DevConf.cz 2019 planning 13:34:38 So I saw that Tomas submitted this session for DevConf.cz, I think we can just add ideas to the ticket 13:35:09 if any of you will be attending devconf.cz please add you name in the ticket we can present it together 13:35:42 you are a cospeaker cverna :P 13:35:48 FIY :P 13:35:54 ^^ 13:36:16 yes I saw an email :) 13:36:45 that's why if anybody wants to join I can add you as cospeaker :) 13:36:45 I'll try to be there, too. Will ask mgmt and let you know :) 13:37:31 sure, let's use the ticket to coordinate :) 13:37:34 cz is a bit far from here, but I'll ping you if I'm going to be there ;) 13:37:37 for sure I will be there, count me in :) 13:37:47 * jcajka will comment in ticket 13:38:34 * cverna does not know if there is some financial help for travel etc available 13:39:18 I ll try to ask around and put some details in the ticket 13:40:09 ok moving to Open Floor 13:40:12 #topic Open Floor 13:41:15 m, we have a dead link to container.fp.org on #fedora-containers 13:41:31 is someone working on it, or would be better to change and put a link to the wiki/pagure ? 13:41:47 I know sanja told me for this year's DevConf there would be some financial help available to community members too. probably best to ask her about this 13:42:50 hm maybe put the wiki AND pagure links in there? 13:43:14 I think they are moving from fedora-infra to use github pages 13:43:39 so maybe it is temporarily down 13:44:04 * cverna looks for the tickets 13:44:10 I never seeing it working, but it could be ;) 13:45:07 I think the ticket was about coreos.fp.o and not containers 13:45:29 so yes it might be that containers.fp.o never worked 13:45:58 we need to ask sanja, she is behind this url :) 13:46:23 I can add an question in https://discussion.fedoraproject.org/ 13:46:51 it's not important either, I clicked the url today by error :D 13:47:24 we need a channel ops in #fedora-containers 13:47:45 I am not sure how to do that :P, I think we need to ask the freenode people 13:48:15 the ircops sig may know it :P 13:48:29 good point :) 13:49:08 ok anything else ? 13:50:13 I will end the meeting in 1 min then 13:50:28 thanks for hosting, cverna! 13:50:41 thanks all for coming :) 13:52:22 #endmeeting