16:30:25 #startmeeting fedora_atomic_wg 16:30:25 Meeting started Wed Feb 21 16:30:25 2018 UTC. The chair is miabbott. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:30:25 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:30:25 The meeting name has been set to 'fedora_atomic_wg' 16:30:39 .hello2 16:30:40 lorbus: lorbus 'Christian Glombek' 16:30:45 .hello2 16:30:46 dustymabe: dustymabe 'Dusty Mabe' 16:30:48 .hello gscrivano 16:30:49 giuseppe: gscrivano 'Giuseppe Scrivano' 16:30:50 lorbus: \o/ 16:30:59 .hello smilner 16:30:59 sanja: you were a little early 16:31:00 ashcrow: smilner 'None' 16:31:01 hey Dusty! =) 16:31:25 and hey everybody else also :) 16:31:26 waiting for the bot to listen to me... 16:31:44 #topic roll call 16:31:45 .hello2 16:31:47 miabbott: miabbott 'Micah Abbott' 16:31:47 .hello2 davdunc 16:31:50 davdunc: davdunc 'David Duncan' 16:32:10 #chair sanja dustymabe lorbus giuseppe 16:32:10 Current chairs: dustymabe giuseppe lorbus miabbott sanja 16:32:45 .hello2 16:32:46 #chair ashcrow davdunc 16:32:46 Current chairs: ashcrow davdunc dustymabe giuseppe lorbus miabbott sanja 16:32:46 sanja: sanja 'Sanja Bonic' 16:32:53 sometimes riot is really slow 16:32:59 had to refresh 16:33:00 .hello jlebon 16:33:01 jlebon: jlebon 'None' 16:33:03 * miabbott also notices the matrix lag 16:33:14 .hello sayanchowdhury 16:33:16 sayan: sayanchowdhury 'Sayan Chowdhury' 16:33:33 #chair jlebon sayan 16:33:33 Current chairs: ashcrow davdunc dustymabe giuseppe jlebon lorbus miabbott sanja sayan 16:34:56 oh, I missed an action item I think with all the meetings and "urgent" tasks and somehow next week came around, let's see 16:35:14 low turnout today, but oh well 16:35:17 #topic previous meeting action items 16:35:30 * dustymabe to schedule february VFAD a CFP for proposed topics 16:35:35 * dustymabe to send email to existing members of PA docker hub org and 16:35:35 proposed new members to solidify membership 16:35:55 * davdunc to inform WG about AWS scan results of Fedora Atomic Host 16:35:55 27.72 16:35:57 * sanja to create ticket on eliminating redundant mailing lists + irc 16:35:58 channels 16:36:02 * sanja to create irc tutorial to onboard newcomers from slack, etc 16:36:03 * misc to open ticket on the irc bot 16:36:04 .hello walters 16:36:05 walters: walters 'Colin Walters' 16:36:14 dustymabe: what can you tell us about your items? 16:36:19 #chair walters 16:36:19 Current chairs: ashcrow davdunc dustymabe giuseppe jlebon lorbus miabbott sanja sayan walters 16:36:25 #action dustymabe to schedule february VFAD a CFP for proposed topics 16:36:34 didn't do that one. will try to do it today 16:36:53 #info working with dockerhub members and new members and will give/revoke access 16:37:08 an interested topic came up in that email thread.. should we start using quay.io instead? 16:37:13 we can discuss later 16:37:51 good topic for open floor 16:38:17 davdunc: any updates on the AWS scans? 16:38:49 still pending completion. In the meantime, I have found some housekeeping needs. 16:39:26 artwork is not displaying properly. I am trying to determine if that is an issue I can resolve or if I need design's help. 16:39:48 #info AWS scans of Fedora Atomic Host still pending completion 16:40:01 i'm going to reaction the same item so we don't lose track 16:40:05 thanks. 16:40:19 #action davdunc to inform WG about AWS scan results of Fedora Atomic Host 16:40:20 27.72 16:40:28 sanja: your turn for updates 16:41:46 decided to delay the deletion ticket for when i have a more comprehensive list including github repos but had no time to make a list on which ones can be archived - as I don't know this and have no opinion, i need the team to tell me which repos can be archived 16:41:49 saying archiving because i'm assuming we don't want any of that deleted 16:42:03 but it'd be nice if not all the repos show up on projectatomic github if they're unused now 16:42:10 so waiting with that ticket action 16:42:23 sanja: is there a discussion somewhere about what repos to archive? 16:42:28 because it needs some time to wade through that 16:43:06 the riot tutorial is written and will be shown when the new website is announced, still gotta push it 16:43:11 dustymabe - no that discussion will happen on the ticket 16:43:13 and in a shared doc 16:43:17 #info riot/irc tutorial is written, will be published when new web site is announced 16:43:42 it'll just be a list of repo names and links - then if just one person says nay, strike through and it won't be archived i'd say? 16:44:07 the repos are your turf and you know what you need 16:44:09 sure. i was just wondering if there was an existing ticket or not 16:44:35 i just know that we are not using some of them and i'd like to make a cleanup via archiving the unused ones 16:44:36 sanja: im gonna just re-action you to create a ticket for the redundancy discussion, ok? 16:45:10 no, but as you're saying it, i think it's best to have 2 tickets 16:45:27 one for github repo archival the other for mailing list and irc channel rehaul 16:45:29 yes, reaction 16:45:40 next week should work 16:45:41 ok, you asked for it 16:45:41 two actions 16:45:46 ouch but that's ok 16:45:49 #action sanja to create ticket about elminating redundancy in mailing lists + irc channels 16:45:53 k that's it from me then 16:46:01 at least regarding previous action items 16:46:09 #action sanja to create ticket about archiving unused projectatomic github repos 16:46:29 is misc around? he's got an action about an irc bot 16:46:53 but i can't remember if that was in jest or not... 16:47:48 I don't remember either 16:48:55 well...i guess i'll just re-action that one too 16:49:00 #action misc to open ticket on the irc bot 16:49:03 #topic Design Meetings over Video 16:49:05 #link https://pagure.io/atomic-wg/issue/418 16:49:19 dustymabe: this assigned to you but it doesn't look like there has been a lot of activity 16:49:25 toward resolution, at least 16:49:50 miabbott: yeah that's my action item 16:50:06 the one we reactioned from earlier 16:50:53 * jbrooks totally spaced on this mtg 16:51:06 oh ok 16:51:11 does it still need the meeting tag? 16:51:47 probably not 16:52:09 #chair jbrooks 16:52:09 Current chairs: ashcrow davdunc dustymabe giuseppe jbrooks jlebon lorbus miabbott sanja sayan walters 16:52:28 ok, i'll remove that tag after this meeting 16:52:54 #topic Identify users for docker hub auto builds for system containers 16:52:56 #link https://pagure.io/atomic-wg/issue/379 16:53:02 dustymabe: i think this is another action of yours 16:53:08 it's unassigned though and is sporting the meeting tag 16:53:50 yeah that was part of my first #action item 16:54:02 which should be done now. I'll update the ticket 16:54:33 thanks! 16:54:44 that's all the 'meeting' tagged items, so on to open floor 16:54:46 #topic open floor 16:55:28 it's not really a topic but a question 16:55:59 lorbus: go for it 16:55:59 I have one, regarding quay/dockerhub 16:56:03 lorbus: go for it 16:56:04 I've been doing rpm packaging lately. Is there a containerized rpmbuild ? 16:56:15 that one can use as builder 16:56:19 go for it 16:56:35 lorbus: like a container with rpm-build binary installed? 16:56:42 exactly that 16:57:04 so.. I think this is an interesting topic 16:57:15 Off the top of my head I don't know of one specific to rpmbuild 16:57:21 i think we have a 'tools' container 16:57:24 But we've talked about tools container(s) before 16:57:29 which probably includes rpm-build 16:57:48 but I don't know if we need a container for every command that we would run 16:57:55 dustymabe: Do you know where it lives? I don't mind taking a look. 16:58:26 I really just want to use the container as build root, so I dont have to install BuildRequires on my laptop 16:58:28 or maybe we just create a thin layer with ENTRYPOINT /usr/bin/rpm-build 16:58:30 for each command 16:59:33 A feature we've talked about in system containers is the ability to add in stubs which do that kind of thing. It still needs a bit more work ... 16:59:41 but based on giuseppe's recent merge it could be doable as well 17:00:02 dustymabe: I found f26/tools in flibs, is that the tools container you are referencing? 17:00:10 ashcrow: yeah 17:00:10 i think this is it - https://src.fedoraproject.org/container/tools/blob/master/f/Dockerfile 17:00:29 ashcrow, yes, that would be very easy, but the difficult part is how to install additional packages in a system container 17:00:47 as that is the main goal for lorbus as I understand 17:01:08 giuseppe: I think that's overthinking it :-) I just mean the ability to be able to run $COMMAND and have the run in the system container for whatever commands it supports 17:01:09 at the same time it'd probably make sense to change the teams to basically be per-repo 17:01:42 maybe the simplest is to just delete all teams and have it be collaborators on the repo 17:01:43 * ashcrow pulls and checks the tools container for rpm-build while we are here 17:01:46 ashcrow: yeah that's something a little different 17:01:52 but I like that better TBH 17:02:05 with one or two identified repo owners? 17:02:14 ashcrow, miabbott, giuseppe: Cool! Thanks for the info already! 17:02:19 anyways we don't need to solve this now, just noting that in passing 17:02:28 lorbus: rpmbuild is not in the tools container as of today 17:02:34 ok. 17:02:39 lorbus: we need to ping tomas to get him to make one for f27 17:02:50 ok next topic 17:02:56 action that? 17:03:02 dustymabe: that'd be awesome! 17:03:18 I will see what I can do myself too :) 17:03:48 the next topic is related to quay/dockerhub 17:03:55 open floor now? (sorry, riot.im/matrix kept disconnecting) 17:04:07 ashcrow: can i action you to ping tomas? 17:04:09 now that we have friends on the quay side, should we considering having our projectatomic organization there instead 17:04:14 miabbott: sure 17:04:24 walters1: yeah, open floor 17:04:32 I'm ok with either. We originally said dockerhub in the blog post but if quay ends up being easier I'm all for it and will happily make an updated post. 17:04:41 #action ashcrow to ping tomas about building f27/tools container 17:04:53 ashcrow: i'm not sure about `easier`, but maybe more `where we want to be longer term` 17:05:00 ashcrow++ 17:05:22 I'm +1 for quay. 17:05:22 especially if we are at a poing of flux with dockerhub, i'd rather not invest there if we have a preferrable target 17:05:29 point* 17:06:06 agree with dustymabe about long term 17:06:07 sanja: one thing to note is that quay does require a small monthly fee (not unless we can get them to waive it) 17:06:08 and less risk of someone noticing these containers don't run with Docker :-) 17:06:12 IMO something to sprint to is having gpg-signed container images, and ideally built reliably from FOSS sources; dockerhub is not a friendly place for it, maybe quay.io will be, and obviously ideally registry.fedoraproject.org etc. 17:06:49 walters1: i almost wonder if registry.fedoraproject.org should use quay in the long term too 17:07:36 ok so obviously this will warrant discussion from others outside of this meeting 17:07:44 lorbus: I personally just use a "dev/pet" container 17:08:03 I'll start a ticket for it and point atomic-devel at the ticket 17:08:14 #action dusty to open ticket to start discussion about quay.io 17:08:22 awesome 17:08:48 miabbott: i return the meeting to you :) 17:09:29 any other topics/questions? 17:09:38 walters: I thought someone must've done already :D 17:09:49 sanja: want to give us an update from the atomic workstation SIG meeting? 17:09:51 i just have a few quick links; i was working over the weekend on FAW 17:09:53 any comments on logo? 17:09:55 #link https://pagure.io/fedora-comps/pull-request/220 17:10:01 new website will be announced for beta for a week this week 17:10:03 #link https://pagure.io/workstation-ostree-config/pull-request/70 17:10:04 sanja: i'm not clear where the actual voting is going to take place 17:10:07 it's gonna be on mailing list and twitter so plenty of time to give comments 17:10:15 sanja: I voted via twitter 17:10:25 i doubt many people follow either comps or workstation-ostree-config; so just FYI ^ 17:10:38 also did: 17:10:38 walters1: thanks! 17:10:39 #link https://pagure.io/workstation-ostree-config/pull-request/64 17:10:53 twitter voting miabbott 17:10:55 so rawhide is going to change a lot, and I'd like to backport this all to f27 at some point 17:11:14 walters1: hmm 17:11:35 would be nice just to get rawhide right and move forward 17:11:37 #info vote on new project atomic logo on mailing list or twitter 17:11:40 since jbrooks commented that this isn't something for the atomic-wg but for the bigger community or something if i remember correctly 17:11:41 #link https://twitter.com/projectatomic/status/965689983490195456 17:11:42 so it's not a formal voting process 17:11:46 #link https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-February/msg00053.html 17:11:55 usually it shouldn't even require voting, it's a style change - and obviously fedora and centos got their own logos for atomic host 17:11:58 so we can't decide much there 17:12:09 dustymabe, the problem is rawhide can't be the *only* development target until it's not always on fire... 17:12:23 walters1: well there's f28 now too 17:13:19 #info recent changes affecting fedora atomic workstation 17:13:22 #link https://pagure.io/fedora-comps/pull-request/220 17:13:22 hence it's just about the project atomic logo - i just wanna say that it's really not growth-friendly to have x logos for x projects with all projects having differnt kinds of docs in different places -> but that's a discussion for another time. baby steps for now. let's see into walters and dusty discussion 17:13:25 #link https://pagure.io/workstation-ostree-config/pull-request/70 17:13:32 #link https://pagure.io/workstation-ostree-config/pull-request/64 17:13:45 sanja, right, the PA logo would be a matter of project atomic governance -- I'm not sure what exactly that is, though ;) 17:13:46 (sorry, just trying to be orderly...) 17:14:06 walters: Do you have a dev container for the purpose of rpm building in a repo to compare? 17:14:11 and dustymabe regarding atomic workstation SIG: https://fedoraproject.org/wiki/Workstation/AtomicWorkstation/SIG the meeting notes are at the bottom, no specific update for now but i'll update next time if there's more in our biweekly meetings. 17:14:11 we will eventually have to have a bigger delta from atomic host as colin once noted on twitter 17:14:21 lorbus, https://github.com/cgwalters/dockerfiles/tree/master/fdev 17:14:39 I'd like to get automation into that, maybe have Buildah build the container per dep requirements and then run the build 17:14:50 walters: thanks! 17:15:02 #info first Fedora Atomic Workstation SIG meeting was held on Monday Feb 19 17:15:03 #link https://fedoraproject.org/wiki/Workstation/AtomicWorkstation/SIG/Notes 17:15:14 I think that fedora atomic and centos atomic are simply different ways to consume those distros, so no separate logos, really 17:15:35 also dustymabe retweeted something jessie is doing now that might collide with buildah - should we talk about that? 17:16:03 jbrooks but we got a different logo for fedora atomic which is a problem 17:16:08 since it does't say atomic host 17:16:18 and we got fedora atomic workstation now 17:16:28 and it's entirely different to project atomic brand as well 17:16:29 sanja, where does that logo appear? 17:16:35 sanja: i asked giusseppe about it 17:16:53 seems to have some overlap. I'm not sure if she's interested in working on a tool we built though 17:17:04 #info jessfraz working on something that could overlap with buildah 17:17:09 #link https://twitter.com/jessfraz/status/966057711552094209 17:17:10 i know all these topics sound like blah but it's important if we want contributors and growth 17:17:13 I don't think it's really like a branding logo, it's more like a piece of art or something 17:17:30 like: https://getfedora.org/en/ 17:17:32 jbrooks - the fedora atomic host logo you mean? 17:17:40 it should be noted that cyphar has been working towards something like buildah too 17:17:53 hold on everyone, let's focus on one topic at a time 17:17:57 I'm getting a bit confused :-) 17:17:58 jbrooks, dustymabe there are already some discussion upstream for running buildah as non root user 17:18:07 #link https://github.com/cyphar/orca-build 17:18:27 giuseppe: right, but we should probably make a decent effort to consolidate if there are multiple tools trying to do the same thing 17:18:32 sanja, I don't think there's really a fedora atomic host logo, is there? 17:18:39 giuseppe: do you mind responding to jessie's tweet directly? 17:18:42 sorry 17:19:09 instead of another implementation, Alex Larsson suggested we use ostree rofiles-fuse for the user case 17:19:20 https://getfedora.org/en/atomic/ this looks like a logo to me. 17:19:26 sorry ashcrow these folks are hard to corral :) 17:19:38 right, i'm just saying let's have a discussion about it 17:19:51 and yes giuseppe or dustymabe please respond to her tweet directly for visibility and possible subsequent discussion 17:19:56 miabbott: :-) 17:19:59 miabbott: you're doing a great job 17:20:09 giuseppe: do you mind? 17:20:10 dustymabe, sanja, sure 17:20:13 giuseppe++ 17:20:13 dustymabe: Karma for giuseppe changed to 2 (for the f27 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:20:28 sanja, is that a logo https://getfedora.org/en/server/ 17:21:02 giuseppe++ 17:21:02 sanja: Karma for giuseppe changed to 3 (for the f27 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:21:02 I guess? I don't think these images are really used in like logos -- do they appear anywhere other than the download page 17:21:05 * dustymabe going for food soon 17:21:29 jbrooks: i think they show up in the install media 17:21:29 There's definitely no centos atomic logo, it's just centos 17:21:37 ashcrow++ 17:21:51 zodbot's not always listening, is it? 17:21:57 * ashcrow chuckles 17:22:15 Let's take a step back ... what's the question we are discussing bout the logos right now? 17:23:07 :) 17:23:15 * dustymabe steps out. thanks for running micah 17:23:21 ok so giuseppe will reply to jessie, check 17:23:21 SIG meeting notes linked, check 17:23:22 logo time 17:23:42 to be fair, this meeting is about the Fedora Atomic WG...the logo for Project Atomic can be discussed at another time if we like 17:23:48 forget the FAH/FAW logos in the mailing list, it'll be just project atomic until we've figured out how to go about creating fah/faw/cah without annoying (a larger chunk of) people 17:23:54 my 2 cents: I think the atomic brand should have a logo that comes in different flavours, FAH, FAW, CentOS... 17:23:55 (since we only have about 6 mins left) 17:24:12 yes that's what jbrooks said basically initially in the mail 17:24:40 yes let's be done with that, i'll just see what twitter says in the end 17:24:43 few more days left 17:24:55 sanja: +1 :) 17:25:02 sanja: you are the community manager so you do hold all the power over the logo :) 17:25:03 and website already has 2 contributors that aren't me, thanks mclasen and Colin, an external guy who might end up doing more 17:25:04 sounds good to me 17:25:14 thanks lorbus - i think so too 17:25:21 sanja, are you going to post about that to the list? 17:25:43 its Marketing 101 really, have something the people recognize elsewhere as well 17:26:08 #info please contribute content to the new web site 17:26:09 post about what? 17:26:10 #link https://github.com/projectatomic/atomic-site-new 17:26:13 i already posted everything to the list 17:26:17 oh the new website stuff? 17:26:18 yes 17:26:20 Changing the site 17:26:24 that'll be in the announcement i mentioned previously this meeting 17:27:05 My #1 question is, why change from middleman in the first place, but the more work that goes into the new custom thing, the worse I feel about asking the question 17:27:29 it'll be a beta for a week via new.projectatomic.io before any changing takes place 17:27:30 so yes 17:27:31 definitely 17:28:16 after that week, if everything is alright, misc will make a redirect so new traffic that comes in via new is redirected to the root url - assuming everything works out 17:28:35 sounds good 17:29:11 #info tools container PR from action item 17:29:23 #link https://src.fedoraproject.org/container/tools/pull-request/2 17:29:24 ashcrow++ 17:29:29 one last try^^ 17:29:32 haha 17:29:43 don't I have any more cookies to give? :( 17:29:54 don't feel bad about asking questions, of course - because josh told me we wanna go away from middleman and because the process right now is cumbersome for me to introduce new docs - it's just not a structure i work well with but the bulk of the work is on me. and middleman isn't maintained anymore. 17:30:24 also my riot is slow so if i miss anything...i gotta reload 17:30:35 and some people send me docs in doc format 17:30:45 I think a few folks are having issues with riot atm :-/ 17:30:50 so i gotta make an md out of them anyway 17:30:57 No other open floor items from me. 17:31:08 question: is the old content from the old pa.io also migrated to the new atomic website?( sorry if I missed convo earlier) 17:31:12 and i'd rather go html directly and have more freedom - plus this way enables new contributors easier 17:31:13 I was thinking a switch to something like jekyll or hugo 17:31:17 as proven 17:31:52 * rubao|laptop s/convo/conversation 17:31:54 And personally, the idea of sending PRs in html, and writing in html w/o knowing how it'll be converted or how it'll look, seems... bad 17:32:01 ok folks we are at time 17:32:04 ok to wrap it up? 17:32:04 OK 17:32:16 jbrooks wanna discuss more via DM or #atomic? 17:32:16 and yes for wrapping it up 17:32:17 Anyway, I'll comment once the commenting time happens 17:32:17 lorbus thanks for commenting 17:32:20 about the marketing stuff :D you're very right 17:32:21 rubao|laptop: some of it will be, some is out of date 17:32:23 yes rubao, all is migrated already 17:32:23 everyone can bother sanja about the new web site in #atomic 17:32:25 time to end this one 17:32:25 http://new.projectatomic.io/ 17:32:26 ok 17:32:29 miabbott: haha +1 17:32:31 sanja =) 17:32:36 #endmeeting