16:31:52 #startmeeting fedora_atomic_wg 16:31:52 Meeting started Wed Jan 17 16:31:52 2018 UTC. The chair is dustymabe. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:31:52 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:31:52 The meeting name has been set to 'fedora_atomic_wg' 16:31:57 #topic roll call 16:32:01 .hello2 16:32:02 dustymabe: dustymabe 'Dusty Mabe' 16:32:18 .hello sayanchowdhury 16:32:21 sayan: sayanchowdhury 'Sayan Chowdhury' 16:32:25 .hello sinnykumari 16:32:26 ksinny: sinnykumari 'Sinny Kumari' 16:32:30 .hello2 sorta 16:32:31 puiterwijk: puiterwijk 'Patrick "マルタインアンドレアス" Uiterwijk' 16:32:31 .hello2 16:32:33 strigazi: strigazi 'Spyros Trigazis' 16:32:55 .hello jasonbrooks 16:32:57 .hello2 16:32:58 jbrooks: jasonbrooks 'Jason Brooks' 16:33:01 maxamillion: maxamillion 'Adam Miller' 16:33:05 .hello coremodule 16:33:06 coremodule: coremodule 'Geoffrey Marr' 16:33:33 .hello walters 16:33:36 Hi all! 16:33:36 walters: walters 'Colin Walters' 16:34:29 .hellomyname is kushal 16:34:42 * kushal will be in 3 meetings at the same time 16:34:45 #chair sayan ksinny puiterwijk strigazi jbrooks maxamillion coremodule sanja kushal walters 16:34:45 Current chairs: coremodule dustymabe jbrooks ksinny kushal maxamillion puiterwijk sanja sayan strigazi walters 16:34:49 kushal: fun 16:34:51 :) 16:34:57 #topic previous meeting action items 16:35:38 * ashcrow to create ticket for actually making a buildah container in 16:35:40 fedora that we can recommend people use to build OCI images 16:35:42 * sanja to take membership proposal AND voting proposal from 16:35:44 https://pagure.io/atomic-wg/issue/363 and add them to the wiki and 16:35:47 close ticket 16:35:48 * ashcrow to create issue to specifically discuss adding crio to atomic 16:35:50 host base image 16:36:02 looks like ashcrow is not present 16:36:15 pinged him in other channel, but I think he did create those issues 16:36:23 while I search.. sanja updates? 16:36:58 .hello smilner 16:37:00 ashcrow: smilner 'None' 16:37:15 Yes and no. 16:37:33 Or it depends - no direct updates, I'm working on an update to the website that is major. 16:38:00 hiya ashcrow 16:38:13 Talked to misc about it so I'll see when I have a prototype ready, was supposed to have first draft Tuesday as my own deadline set but didn't work out due to other things and somehow Tuesday turning into the most meeting-heavy day from having 0. 16:38:15 dustymabe: hey :-) 16:38:36 sanja: i was asking about your action item? 16:38:48 sanja to take membership proposal AND voting proposal from https://pagure.io/atomic-wg/issue/363 and add them to the wiki and close ticket 16:39:03 So fingers crossed for next week, then preps for 3 talks at DevConf && FOSDEM so... *runs around screaming* 16:39:05 oh yeah that's closed 16:39:10 nothing to report there 16:39:30 it's added to the wiki exactly as we voted for Josh' proposal 16:39:37 #info sanja closed membership proposal AND voting proposal. updated the wiki and closed ticket 16:39:54 ashcrow: these were your AIs: * ashcrow to create ticket for actually making a buildah container in fedora that we can recommend people use to build OCI images 16:40:06 * ashcrow to create issue to specifically discuss adding crio to atomic host base image 16:40:26 I did create both tickets. I'll grab the links now. 16:40:56 ashcrow: thanks! 16:40:58 Buildah Container issue 16:41:01 #link https://pagure.io/atomic-wg/issue/406 16:41:02 .hello jberkus 16:41:03 #chair ashcrow jberkus 16:41:03 Current chairs: ashcrow coremodule dustymabe jberkus jbrooks ksinny kushal maxamillion puiterwijk sanja sayan strigazi walters 16:41:03 jberkus: jberkus 'Josh Berkus' 16:41:24 cri-o in Atomic Host 16:41:36 #link https://pagure.io/atomic-wg/issue/407 16:42:03 ok moving on 16:42:06 both have started to get a bit of converstaion 16:42:32 #topic topics? 16:42:42 we don't have any issues tagged with meeting 16:43:10 anyone want to propose a topic or we can move to open floor 16:43:21 https://public.etherpad-mozilla.org/p/topics 16:43:26 feel free to propose topics there ^^ 16:43:55 added one 16:44:32 ok we'll start to run through them 16:44:40 #topic this week's FAH release 16:45:07 We realized late that there is a security related update for docker that we'd like to get into this week's release 16:45:28 there is a new compose running right now and we'll get some images out of that for us to do testing on and possibly do a release tomorrow 16:46:07 this compose will also contain the latest kernel with *some* updates for spectre, although those are slowly rolling out 16:46:31 I'll send out a candidate email later today 16:46:40 any thoughts/concerns? 16:46:52 dustymabe: Just a thanks for all your hard work :-) 16:46:59 thanks dustymabe 16:47:12 +1 for that 16:47:29 it takes a village to raise an atom.. or somethin like that 16:47:31 :) 16:47:49 * dustymabe moves to next topic 16:48:00 #topic meeting schedule due to devconf? 16:48:05 ashcrow: ? 16:48:32 Basically, many of us will be at devconf this coming week so will that require a postpone of the meeting, etc... 16:48:48 * maxamillion won't be at devconf this year :( 16:49:07 maxamillion: :-/ 16:49:18 but yes, I think it's wise to postpone the meeting because of devconf 16:49:35 anyone opposed? 16:49:50 jberkus: should this formally require a vote? 16:49:55 no 16:50:02 k 16:50:31 * dustymabe also notes that sanja sent out an email regarding the atomic community meeting 16:50:45 please respond to her with thoughts on cancelling that next week 16:51:18 #info we will not have our regularly scheduled atomic wg meeting next week due to devconf 16:51:42 #action ashcrow to send email to atomic-devel/announce to let people know 16:51:51 ashcrow: ^^ see what I did there :) 16:51:54 :-) 16:51:56 I do 16:52:15 hehehe 16:52:17 ok next topic 16:52:23 #topic meeting schedule at devconf 16:52:38 if everyone agrees here, I'll just cancel the community meeting (or let jberkus do it since it's his calendar item and I can't edit it) 16:53:02 since we will have a large number of atomic* related folks at devconf can we hammer down some sort of schedule to meet? 16:53:16 sanja: i'm +1 since I will be on plane 16:53:34 sanja: +1 16:54:07 +1 for schedule to meet at devconf for some structured get-together 16:55:28 does anyone know of any time that has already been set aside for this? 16:55:43 * dustymabe assumes that only jberkus would have done something like that 16:56:04 I am not aware of any specific time set for this 16:56:21 ok maybe we can try to get together and figure one out 16:56:22 scheduling > randomness for meeting :-) 16:56:36 that's all I had on that topic 16:56:44 nope 16:56:52 ok 16:56:55 dustymabe: orginally the atomic session was *supposed* to include BOF time 16:57:10 but they shortened it to 1/2 hour, something I didn't realize until Sanja pointed it out 16:57:13 we do have a BOF, right? 16:57:47 not really anymore 16:57:51 jberkus: well that is kinda garbage. maybe we can get that changed back or moved to the end of the day or something? 16:58:01 it's called BoF still on the schedule since Josh submitted it like that but it's now just a half hour quick style presentation of projeects 16:58:06 this keyboard... 16:58:15 sanja: fun 16:58:26 dustymabe: I'm not going to do that because I resigned the devconf committee 16:58:37 My knowledge of BOF doesn't seem to fit the conversation. What does it stand for in this context? 16:58:46 Birds of a Feather 16:58:48 (Base of fire) 16:58:49 ah 16:58:51 ok 16:59:05 since I was unwilling to deal with their train-wreck of scheduling software 16:59:10 someone else can take it up if they want 16:59:12 fun 16:59:16 ok let's move on 16:59:19 #topic open floor 16:59:20 ashcrow: I had to google it too when I first heard of it, then google some more. 16:59:31 sayan, any updates on fedimg? 16:59:35 (two different spreadsheets and a database, none of which have the same contents) 16:59:50 dustymabe: yes, the PR has been merged 16:59:58 jberkus: having the same content everywhere would be too useful! 17:00:06 dustymabe: I am working on the packaging 17:00:11 sayan: how are we looking on moving forward with that in prod? 17:00:35 dustymabe: the already updated the ansible scripts 17:00:50 they*? 17:01:11 oops, s/the/I 17:01:45 so, after the packaging, I will deploy to staging 17:01:46 sayan: ok and those changes are merged? 17:01:52 dustymabe: yes 17:02:11 ok so possibly next week we could put those in prod? will you be in brno? 17:02:22 dustymabe: yes, we can do that 17:02:29 sayan: awesome 17:02:32 dustymabe: I am not sure, still waiting on visa 17:02:38 anyone else with open floor items and/or news? 17:02:50 I saw ksinny has done some work to enable s390x 17:03:09 and pbrobinson is doing some work to enable aarch64 SBC (Rpi3 and Pine64) 17:03:25 dustymabe: nice 17:03:54 Reminder to please join the converstaion on the buildah and cri-o issues 17:03:55 we also had an upstream ostree and rpm-ostree release(s) 17:03:55 that's all from me 17:04:32 ashcrow: where is this conversation happening? you mean pagure? 17:04:40 #link https://github.com/ostreedev/ostree/releases/tag/v2018.1 17:04:58 #link https://github.com/projectatomic/rpm-ostree/releases/tag/v2018.1 17:05:11 jberkus: yes I think he means pagure 17:05:44 jberkus: pagure. Linked earlier in the meeting. 17:05:56 ok open floor is still open. i'll close it down in a few minutes if no one has anything else? 17:06:13 jberkus: https://pagure.io/atomic-wg/issue/406 and http://pagure.io/atomic-wg/issue/407 17:06:21 i posted https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/YLXTI6Q7OK37BPXOCNANKLNTW66O2ZBP/ too 17:07:38 thanks walters 17:08:38 ok going to go ahead and close it out 17:08:42 #endmeeting