17:01:50 <dustymabe> #startmeeting atomic-wg
17:01:50 <zodbot> Meeting started Wed Apr 26 17:01:50 2017 UTC.  The chair is dustymabe. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:50 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:01:50 <zodbot> The meeting name has been set to 'atomic-wg'
17:01:56 <dustymabe> #topic roll call
17:02:01 <dustymabe> .hellomynameis dustymabe
17:02:04 <jberkus> .hello jberkus
17:02:06 <yzhang> .hello yzhang
17:02:09 <zodbot> dustymabe: dustymabe 'Dusty Mabe' <dustymabe@redhat.com>
17:02:12 <zodbot> jberkus: jberkus 'Josh Berkus' <josh@agliodbs.com>
17:02:15 <zodbot> yzhang: yzhang 'Yu Qi Zhang' <jzehrarnyg@gmail.com>
17:02:24 <miabbott> .hello miabbott
17:02:27 <zodbot> miabbott: miabbott 'Micah Abbott' <miabbott@redhat.com>
17:02:54 <sayan> .hello sayanchowdhury
17:02:55 <zodbot> sayan: sayanchowdhury 'Sayan Chowdhury' <sayan.chowdhury2012@gmail.com>
17:03:04 <maxamillion> .hello maxamillion
17:03:05 <zodbot> maxamillion: maxamillion 'Adam Miller' <maxamillion@gmail.com>
17:03:06 <jbrooks> .hello jasonbrooks
17:03:09 <zodbot> jbrooks: jasonbrooks 'Jason Brooks' <JBROOKS@REDHAT.COM>
17:03:27 <kushal> .hellomynameis kushal
17:03:28 <zodbot> kushal: kushal 'Kushal Das' <mail@kushaldas.in>
17:03:46 <roshi> .hello roshi
17:03:47 <zodbot> roshi: roshi 'Mike Ruckman' <mruckman@redhat.com>
17:03:53 <dustymabe> hmm who ran the meeting last week?
17:04:06 <fatherlinux> .hello fatherlinux
17:04:08 <dustymabe> not seeing an email to the list
17:04:14 <zodbot> fatherlinux: fatherlinux 'Scott McCarty' <smccarty@redhat.com>
17:04:16 <dustymabe> fatherlinux: \o
17:04:21 <dustymabe> good to see you around
17:04:28 <jberkus> dustymabe: then it was probably me
17:04:34 <roshi> coulda been me too
17:04:53 <dustymabe> found it
17:04:56 * roshi never remembers to email to the list because he thinks checking meetbot is easier/more efficient
17:05:01 <fatherlinux> @dustymabe: same here. Good to see you. I am going to to completely admit my newb-ness. I have never been to one of these...
17:05:18 <jberkus> looks like me
17:05:19 <dustymabe> fatherlinux: sweet!
17:05:23 <jberkus> I'll email
17:05:24 <dustymabe> not much to it
17:05:32 <dustymabe> #topic previous meeting action items
17:05:34 <dustymabe> * jberkus to create tickets for prerequisites for removing kube packages
17:05:36 <dustymabe> from  base ostree
17:05:39 <dustymabe> * dustymabe, walters to discuss new release process at beginning of
17:05:41 <dustymabe> calendar year 2017
17:05:42 <dustymabe> * dustymabe walters jberkus to explore overlayfs writeability issue
17:05:44 <dustymabe> * dustymabe to blog using overlayfs in Atomic
17:05:47 <dustymabe> * scollier to update ticket on Future of Fedora Dockerfiles
17:05:49 <dustymabe> * jberkus jbrooks to do initial draft of PRD and ping dusty and group
17:05:50 <dustymabe> for further review
17:05:52 <dustymabe> * jberkus to lead planning some fedora-atomic work sessions around
17:05:55 <dustymabe> devconf
17:05:57 <dustymabe> damn -- wrong meeting
17:05:59 <dustymabe> ignore that
17:06:01 <jberkus> dustymabe: um, that's the wrong meeting
17:06:01 <jbrooks> heh
17:06:44 <kushal> which devconf?
17:06:50 <dustymabe> * jbrooks to lead writing up the new support policy and plan for rolling
17:06:53 <dustymabe> releases
17:07:00 <dustymabe> kushal: that was the wrong meeting
17:07:05 <dustymabe> jbrooks: looks like you had the only AI
17:07:28 <jbrooks> dustymabe, right, I haven't done that -- I actually forgot about it, I'll do it before next meeting
17:07:30 <jberkus> yeah, we mostly closed a lot of stuff last meeting
17:07:31 <dustymabe> k
17:07:33 <jberkus> FWIW, I'
17:07:38 <sayan> dustymabe: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-04-19/fedora_atomic_wg.2017-04-19-17.02.txt
17:07:41 <jberkus> I'm going to do a blog on overlayfs today ;-)
17:07:50 <maxamillion> :)
17:07:54 <dustymabe> #action jbrooks to lead writing up the new support policy and plan for rolling
17:07:55 <maxamillion> jberkus: +1
17:07:58 <jberkus> maxamillion: how are you feeling?
17:08:06 <dustymabe> jberkus: ok, let's talk about that after the meeting
17:08:25 <dustymabe> #topic  fedimg: don't use 'builder' instance for uploading AMIs
17:08:33 <dustymabe> #link https://pagure.io/atomic-wg/issue/269
17:08:54 <dustymabe> i created this issue to document an issue we had with releasing FAH yesterday
17:09:09 <dustymabe> and to track work that is being done that should mitigating it from happening again
17:09:22 <dustymabe> sayan is working on this, we'll track his progress there
17:09:36 <dustymabe> nothing else to really discuss. mostly an FYI
17:09:44 <jberkus> thanks
17:09:53 <jberkus> wow, EC2 instance deployment failing?  Imagine that!
17:10:01 <dustymabe> #topic  2WK Atomic Release Criteria
17:10:07 <dustymabe> #link https://pagure.io/atomic-wg/issue/264
17:10:14 <dustymabe> roshi: ^^
17:10:23 <roshi> done
17:10:31 <roshi> sorry, thought i twas pulled off the meeting tag
17:10:36 <dustymabe> can you add a comment and close the ticket?
17:10:40 <roshi> thanks for the edits folks
17:10:42 <roshi> sure
17:10:45 <dustymabe> thx
17:10:55 <dustymabe> #topic clarify policy on atomic host support for older Fedora "number" releases
17:11:01 <dustymabe> #link https://pagure.io/atomic-wg/issue/228
17:11:09 <jberkus> that's jbrooks's action item
17:11:12 <dustymabe> i think this was where jbrooks' action item came from
17:11:13 <dustymabe> yep
17:11:20 <dustymabe> ok so we're good on that one
17:11:39 <dustymabe> #topic design, deploy and document Fedora OpenShift Playground (FOSP)
17:11:45 <dustymabe> https://pagure.io/atomic-wg/issue/153
17:11:51 <dustymabe> blocked on hardware still?
17:11:54 <dustymabe> misc: ^^
17:11:59 <jberkus> dustymabe: no updates, still blocked on hardware
17:12:36 <dustymabe> jberkus: any time frame there?
17:12:43 <jbrooks> jberkus, did quaid ever add you to the ticket he mentioned?
17:12:51 <jbrooks> https://pagure.io/atomic-wg/issue/153#comment-432517
17:13:01 * jzb waves
17:13:13 <jbrooks> hey, jzb
17:13:13 <maxamillion> o/
17:13:51 <jberkus> yes, but there's been no updates to it in a couple of weeks
17:14:14 <kushal> jzb, hello :)
17:14:25 <dustymabe> jberkus: can you ping again?
17:14:34 <dustymabe> and that's all we can really do with this ticket
17:14:37 <jberkus> sure.
17:14:47 <dustymabe> #topic containers tickets
17:14:52 <dustymabe> #link https://pagure.io/atomic-wg/issues?status=Open&tags=containers
17:15:05 <dustymabe> where do we stand on these, we had a big "cleanup" a few weeks back
17:15:20 <dustymabe> can we fully start reviewing new containers?
17:15:35 <dustymabe> jberkus: how's the review of the owncloud container going?
17:15:58 <kushal> dustymabe, also do we prefer to have the real rpm packager to do the container build also?
17:16:21 <jberkus> dustymabe: actually got hung up on not having a PostgreSQL container for database, which was my big sidetrack from Friday
17:16:33 <jbrooks> kushal, that shoulnd
17:16:40 <jbrooks> shouldn't be necessary
17:16:53 <dustymabe> yeah, i'm sure we "prefer" it, but not necessary
17:17:12 <gholms> I'd imagin if the package's maintainer wants to co-maintain it that would be a great idea.
17:17:20 <gholms> *imagine
17:17:25 <kushal> gholms, yup.
17:17:30 <sayan> gholms: +1
17:17:40 <jberkus> jhogarth and I will need to revise the container submission ... I wish there was a way for me to do line-item edits on these, ala github
17:17:43 <kushal> jbrooks, dustymabe Understood, just want to say it out aloud for notes.
17:17:59 <gholms> I'm also prettyy sure it would be a good idea to ask the package's maintainer about that proactively when creating a new container.
17:18:05 <dustymabe> jberkus: you can put the file in a gist and make comments there
17:18:25 <kushal> Do we have a zodbot suggestion command?
17:18:32 <dustymabe> don't know
17:18:40 <roshi> it's #info
17:18:40 <gholms> kushal: #idea?
17:18:48 <roshi> that'll do what we want
17:18:55 <kushal> #idea <gholms> I'm also prettyy sure it would be a good idea to ask the package's maintainer about that proactively when creating a new container
17:19:00 <kushal> gholms, thanks.
17:19:01 <dustymabe> k
17:19:12 <dustymabe> jberkus: so we don't really have any other big blockers for containers?
17:19:23 <gholms> Man, am I bad at typing on this thing.  :/
17:19:31 * roshi doesn't think #idea does anything for zodbot
17:19:32 <jberkus> no, I need to do the last updates on help files, and jbrooks needs to notify all the maintainers
17:19:34 <roshi> use #info
17:19:48 <jberkus> there are new policy issues to debate, but they are all additive
17:19:59 <jbrooks> jberkus, Right, have we captured all the things that need notification?
17:20:08 <dustymabe> ok
17:20:11 <dustymabe> cool
17:20:15 <jberkus> jbrooks: as soon as I finish revision of Help
17:20:33 <kushal> #commands
17:20:33 <zodbot> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #rejected #restrictlogs #save #startmeeting #topic #unchair #undo #unlurk
17:20:36 <dustymabe> #info please review as many containers as you can!
17:20:44 <dustymabe> #topic open floor
17:20:49 <dustymabe> open floor everyone :)
17:20:56 <dustymabe> fatherlinux: jzb: did you all have something for us?
17:20:58 * roshi has nothing for this meeting
17:21:05 <dustymabe> jberkus: we are in open floor
17:21:06 <jberkus> jbrooks: so, today
17:21:24 <jberkus> (bad IRC day, for some reason)
17:21:28 <fatherlinux> @dustymabe: yeah, I definitely wanted to chat about the minimal container image work...
17:21:31 <kushal> Next week, I will start my travel for pycon.
17:21:32 <gholms> roshi: #idea and #help are pretty useful, too  ;)
17:21:43 <maxamillion> just a quick reminder that the docker namespace is gone and container namespace is the new way ... I'm going to get updated $DISTGIT ENV vars into the base images soon and then we'll be completely cut over
17:21:53 <roshi> gholms: but is #idea an actual zodbot thing?
17:21:56 <roshi> that was my question
17:22:02 <dustymabe> maxamillion++ on the docker -> container transition
17:22:06 <maxamillion> :D
17:22:09 <dustymabe> fatherlinux: what questions do you have :)
17:22:10 <nb> roshi, it is
17:22:12 <maxamillion> also, I'm out next week for Red Hat Summit
17:22:18 <roshi> ok, wasn't sure
17:22:23 <nb> roshi, it is a thing, according to #commands
17:22:24 <maxamillion> <3 all your faces but I'll be presenting during the time of this meeting
17:22:27 <fatherlinux> @dustymabe: so a bunch :-)
17:22:31 <roshi> wanted to make sure it was captured in the logs
17:22:42 <gholms> roshi: Yes
17:23:01 <fatherlinux> I have heard rumors that Fedora is working on it's own minimal image. I am wondering if this is built off the work that Collin did in CentOS?
17:23:20 <dustymabe> fatherlinux: yeah pretty much
17:23:37 <dustymabe> https://fedoraproject.org/wiki/Changes/ContainerMinimalImage#Summary
17:24:09 <jzb> dustymabe: will that be released with 26, or out of band?
17:24:16 <dustymabe> jzb: with 26
17:24:22 <dustymabe> it's already being built for f26
17:24:26 <dustymabe> and was part of f26 alhpa
17:24:37 <jzb> excellent
17:25:07 <dustymabe> http://dl.fedoraproject.org/pub/fedora/linux/releases/test/26_Alpha/Docker/x86_64/images/Fedora-Container-Minimal-Base-26_Alpha-1.7.x86_64.tar.xz
17:25:11 <fatherlinux> @dustymabe sweet. So, next question @jberkus, is there any way that we could highlight that work as the center tile on projectatomic.io? I think the Fedora Minimal image would be the right thing...
17:25:21 <jberkus> dustymabe: are we going to do a fedora-init container at the same time?
17:25:32 <jzb> fatherlinux: there was a thread about replacing with FLIBS
17:25:42 <dustymabe> jberkus: it's not planned, but would be nice to have
17:25:43 <jzb> but the minimal image might be good too
17:25:46 <jberkus> fatherlinux: honestly, a blog post would be the most appropriate thing for a specific image
17:25:46 <fatherlinux> @jzb: yeah, I saw, that's why I am asking here...
17:25:49 <fatherlinux> :-)
17:25:58 <jberkus> dustymabe: I don't know enough about systemd to do a good job
17:26:04 <maxamillion> wait, we want to release that thing?
17:26:14 <fatherlinux> So, another question, what is fedora-init?
17:26:16 <dustymabe> maxamillion: why not ?
17:26:24 <maxamillion> nobody requested it be released
17:26:39 <jberkus> fatherlinux: base image with systemd inside
17:26:40 <dustymabe> maxamillion: hmm
17:26:42 <maxamillion> need a releng ticket for new release artifacts
17:26:48 <fatherlinux> @jberkus: ack :-)
17:26:50 <dustymabe> maxamillion: yeah I opened a ticket for it
17:26:54 <maxamillion> dustymabe: oh?
17:27:01 <maxamillion> dustymabe: alright, my bad ... nvm, all good
17:27:02 <dustymabe> one sec
17:27:05 <jbrooks> jberkus, it's already in there, right?
17:27:11 * maxamillion needs to get up to speed
17:27:12 <walters> what are we planning to call it when we upload it to the hub?
17:27:17 <walters> who owns that?
17:27:20 <maxamillion> dustymabe: sorry, oversight on my part
17:27:33 <dustymabe> https://pagure.io/releng/issue/6619
17:27:38 <mrguitar> jberkus: the fedora base image already has systemd. The init one should just tweak the profile and add the /sbin/init as the default command
17:27:38 <walters> the koji/imagefactory naming is...bad
17:27:53 <dustymabe> mrguitar: hi
17:27:55 <dustymabe> .fas mrguitar
17:27:56 <zodbot> dustymabe: mrguitar 'Ben Breard' <mrguitar.net@gmail.com>
17:27:59 <dustymabe> nice
17:28:13 * mrguitar should get a better freenode nick :/
17:28:20 <jberkus> mrguitar: huh.  can we discuss this on #fedora-cloud?  because I'm getting some issues using it in the standard base image
17:28:21 <dustymabe> pretty awesome if you ask me
17:28:28 <jberkus> mrguitar: or on #atomic
17:28:38 <dustymabe> walters: when you say what are we planning to call it?
17:28:45 <dustymabe> you mean what name will it have in the registry?
17:28:50 <walters> right
17:28:51 <fatherlinux> My bigger question is could we highlight all of the base images, both the normal fedora one and the minimal one (when it is released)...
17:29:03 <walters> (and we *are* planning to push it to registry.fedoraproject.org right?)
17:29:21 <maxamillion> fatherlinux: yes
17:29:27 <dustymabe> walters: yes
17:29:27 <maxamillion> fatherlinux: we're including them in the announcement
17:29:36 <dustymabe> or at least that was my thoughts
17:29:57 <miabbott> the RHEL minimal is rhel7-atomic, so.....fedora-atomic?
17:30:10 <maxamillion> fatherlinux: example -> https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/HDPAL6VJFV55UWE64G2WGRWWKBHASWQT/
17:30:27 <dustymabe> miabbott: ehh
17:30:34 <dustymabe> lots of confusion there
17:30:43 <maxamillion> fatherlinux: we're also working on getting a webUI infront of our registry (something I thought we'd have had weeks ago, but we're blocked on rpm package review ... :/)
17:30:53 <miabbott> hey, i didn't name it.  blame mrguitar
17:31:08 <dustymabe> so i was thinking on a plane one day
17:31:14 <miabbott> as one does
17:31:14 <dustymabe> very late at night
17:31:25 * mrguitar kicks miabbott under the table
17:31:31 <dustymabe> about using acronyms for names of different "base images"
17:31:33 <maxamillion> naming things is hard
17:31:34 <gholms> Uh oh
17:31:34 <fatherlinux> @maxamillion: that is exactly what I am thinking. I would love to see a landing page on projectatomic.io then have the center tile point to that. On that landing page, have all of the types of images highlighted and then explain "why" people would want to use them. I don't think we have highlighted the fedora images enough and people are confused
17:31:41 <fatherlinux> I am anyway ;-)
17:31:58 <dustymabe> yes naming things is hard
17:32:13 <miabbott> dustymabe: acronyms == 'lots of confusion there'
17:32:15 <dustymabe> but I feel like acronyms would help us create unique names but also be descriptive about what is in the image?
17:32:20 <jberkus> (me would have named the minimal image "Quark")
17:32:20 <fatherlinux> @all I am not hell bent on any particular name. My main concern is that we highlight the work...
17:32:22 <maxamillion> fatherlinux: oh yeah, we haven't yet sorted out how to deliver all the metadata around container images we want to
17:32:22 <gholms> Heh.  We don't even say why one would want to use atomic in the first place.  Image-level detail would be even better.
17:32:51 <dustymabe> gholms: right now the real difference is that python is not in the image
17:32:55 <dustymabe> and we use microdnf for install
17:33:00 <dustymabe> of other software
17:33:04 <dustymabe> so it's just a smaller base
17:33:20 <dustymabe> so that is basically why someone would want to use it
17:33:36 <dustymabe> basically they don't want to use python and don't need it for anything and want a smaller image to build on top of
17:33:41 <dustymabe> am i missing something?
17:33:55 <gholms> Great.  That belongs on the web site.
17:34:06 <walters> the thing is the name is ABI, given the model for Docker/OCI-style derivation
17:34:14 <dustymabe> jberkus: do you want to create a ticket somewhere for highlighting the container images on the atomic site?
17:34:14 <fatherlinux> @gholms: yeah, when you land at project atomic site, there is a host on the left, and a registry on the right. Then, in the middle, there is this "thing."  IMHO, it would make sense to have images in the middle so that this is the complete minimal set of things that a user would download to get started with containers...
17:34:23 <jberkus> maxamillion: until we get the webUI, where should I point people for FLIBS?
17:34:42 <jberkus> dustymabe: sure
17:34:57 <jberkus> fatherlinux: that's the plan, see atomic-devel ML
17:35:10 <dustymabe> fatherlinux: there are other efforts we have going on too that we should probably link from the site, right?
17:35:14 <dustymabe> kompose is one example
17:35:27 <fatherlinux> @dustymabe agreed
17:35:29 <dustymabe> i know it's not exactly under the atomic umbrella, but it is part of kube incubator
17:35:39 <dustymabe> so maybe we can have a top three
17:35:39 <fatherlinux> I could picture sort of a 101, 201, 301 set of things we highlight
17:35:41 <maxamillion> jberkus: the build system?
17:35:44 <dustymabe> and then more under it
17:35:46 <maxamillion> jberkus: or the registry?
17:35:46 <fatherlinux> 101 = images, hosts, registry
17:35:52 <fatherlinux> 201 = compose, other things..
17:35:56 <jzb> dustymabe and others
17:36:01 <fatherlinux> 301 = deep security stuff, etc...
17:36:04 <jzb> We haven't updated the site in more than a year
17:36:10 <jberkus> https://github.com/projectatomic/atomic-site/issues/423
17:36:10 <jzb> it'd be nice if we rotated those things
17:36:24 <jberkus> maxamillion: user perspective, so registry
17:36:25 <jzb> so we don't have to choose, we just have to update it more frequently
17:36:26 <dustymabe> jberkus: should we track that in the atomic-wg tracker?
17:36:28 <mrguitar> I guess I'm the only one who would vote for f26-atomic :) It's so much nicer ring to it than fedora-container-minimal-base-26_alpha-1.7.x86_64
17:36:29 <dustymabe> as well
17:36:52 <jbrooks> This calls to mind the need for some projectatomic-specific meetings
17:36:57 <jberkus> mrguitar: that's what we call the Atomic OS image, though, so that would be fairly confusing
17:37:00 <fatherlinux> @jberkus what is FLIBS or container libraries?
17:37:04 <fatherlinux> This sounds 201
17:37:06 <jbrooks> Because this is getting away from fedora
17:37:08 <dustymabe> mrguitar: well the image filename is probably mostly irrelevant, what matters is what we put in the tag in the registry
17:37:14 <jberkus> fatherlinux: Fedoral Layered Image Build Service
17:37:38 <fatherlinux> @jberkus: ahh, that sounds cool
17:37:45 <dustymabe> jbrooks: i think you are right, there may be a time when we need that
17:37:46 <walters> jberkus, the proper name is Atomic Host though... https://pagure.io/releng/issue/6413
17:37:50 <fatherlinux> @jberkus: like digital transformation for Fedora ;-)
17:37:50 <jberkus> jbrooks: yah, maybe
17:37:53 <kushal> fatherlinux, no worries, even I was confused for some time with that name :p
17:37:59 <jbrooks> The time is nowq
17:38:12 <jbrooks> Because there's also centos atomic
17:38:15 <jbrooks> for all this
17:38:28 <jzb> jbrooks: are there still CentOS atomic meetings?
17:38:34 <dustymabe> jzb: yep
17:38:38 <jbrooks> Every week
17:38:41 <dustymabe> poor attendance
17:38:46 <dustymabe> i've been bad about showing up
17:38:52 <dustymabe> jbrooks: is the rock of that group
17:38:59 <jberkus> this is getting off-topic
17:39:10 <dustymabe> yep - we can continue in #fedora-cloud
17:39:12 <dustymabe> after the meeting
17:39:12 <jberkus> let's table the Atomic meeting discussions
17:39:26 <dustymabe> did anyone ask a question that was not addressed?
17:39:41 <maxamillion> jberkus: for now, unfortunately the best thing we have is the release emails
17:39:48 <dustymabe> i'll finish with an FYI
17:39:53 <fatherlinux> @jberkus: ack
17:40:01 <dustymabe> we are doing a 2wk Fedora Atomic Host release today
17:40:04 <maxamillion> jberkus: or we could maybe provide a doc on how to query the registry via rest api ... but also not the best user experience
17:40:14 <jberkus> maxamillion: in that case, I'll put up a wiki page with the current list of images?
17:40:15 <dustymabe> and this will be the first release that DigitalOcean will fully support
17:40:25 <fatherlinux> @dustymabe: do you have info on the centos atomic meeting? I should probably start attending that one too ;)
17:40:42 <jberkus> fatherlinux: PM
17:40:46 <dustymabe> fatherlinux: jbrooks will give you that info in #fedora-cloud
17:41:22 <dustymabe> we'll be doing a blog post about DigitalOcean tomorrow. will appreciate some tweets etc around that
17:41:27 <fatherlinux> @dustymabe: that is EXACTLY why I would like to have an images featured on project atomic. We could highlight Digital Ocean, and other places people can get images. Reasons why they would want to use Fedora images, etc...
17:41:27 <dustymabe> once we put out the blog post
17:41:48 <dustymabe> fatherlinux: this is the atomic host "image", not the container image
17:41:54 <dustymabe> but yeah, i agree with you
17:41:57 <dustymabe> having that would be nice
17:42:21 <fatherlinux> @dustymabe, ahhh
17:42:25 <fatherlinux> oops...
17:42:43 <dustymabe> fatherlinux: see you do it too :)
17:42:56 <dustymabe> ok all, going to close out the meeting
17:43:01 <dustymabe> let's head over to #fedora-cloud
17:43:11 <roshi> thanks dustymabe
17:43:13 <dustymabe> or if more than one convo is going on take it to #atomic
17:43:16 <gholms> dustymabe: We should still say why people should be interested in using it in that announcement.  ;)
17:43:33 <dustymabe> gholms: interested in using digitalocean?
17:43:54 <dustymabe> the announcement is specifically about fedora atomic host in digital ocean
17:44:00 <dustymabe> it has nothing to do with containers, FYI
17:44:02 <jberkus> dustymabe: can we update getfedora.org?
17:44:18 <dustymabe> jberkus: sure, but the only guy that works on our websites is a volunteer
17:44:23 <dustymabe> so help is welcome
17:44:30 <dustymabe> ok closing out meeting
17:44:33 <dustymabe> 3..
17:44:40 <jberkus> where's source?
17:44:40 <dustymabe> 2..
17:44:45 <dustymabe> 1..
17:44:48 <gholms> dustymabe: More like answering the question, "Fedora is already on DO.  Why is this significant?"
17:44:52 <maxamillion> jberkus: someone would have to update that by hand every two weeks
17:44:59 <dustymabe> #endmeeting