17:01:42 <jberkus> #startmeeting fedora_atomic_wg
17:01:42 <zodbot> Meeting started Wed Jul 19 17:01:42 2017 UTC.  The chair is jberkus. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:42 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:01:42 <zodbot> The meeting name has been set to 'fedora_atomic_wg'
17:01:49 <jberkus> #topic Roll Call
17:01:50 <jbrooks> .fas jasonbrooks
17:01:50 <zodbot> jbrooks: jasonbrooks 'Jason Brooks' <JBROOKS@REDHAT.COM>
17:02:04 <maxamillion> .hello maxamillion
17:02:05 <zodbot> maxamillion: maxamillion 'Adam Miller' <maxamillion@gmail.com>
17:02:16 <dustymabe> .hello dustymabe
17:02:18 <zodbot> dustymabe: dustymabe 'Dusty Mabe' <dustymabe@redhat.com>
17:02:28 <ksinny> .hello sinnykumari
17:02:29 <zodbot> ksinny: sinnykumari 'Sinny Kumari' <ksinny@gmail.com>
17:02:44 <bowlofeggs> .hello bowlofeggs
17:02:45 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <randy@electronsweatshop.com>
17:03:05 <strigazi> .hello strigazi
17:03:06 <zodbot> strigazi: strigazi 'Spyros Trigazis' <strigazi@gmail.com>
17:03:07 <scollier> .hello scollier
17:03:08 <zodbot> scollier: scollier 'Scott Collier' <emailscottcollier@gmail.com>
17:03:54 <jberkus> #chair jbrooks jberkus maxamillion dustymabe ksinny bowlofeggs strigazi scollier
17:03:54 <zodbot> Current chairs: bowlofeggs dustymabe jberkus jbrooks ksinny maxamillion scollier strigazi
17:04:07 * gholms takes a seat in the bleachers
17:04:28 <jberkus> #topic action items from last meeting
17:04:39 <jberkus> maxamillion roshi to come up with guidelines for meeting quorum for
17:04:39 <jberkus> the atomic working group
17:04:44 <jberkus> maxamillion, roshi ?
17:05:06 <maxamillion> yeah, we did that and I completely forgot to update the ticket ... I'll do that now
17:05:19 * roshi is here
17:05:24 <maxamillion> jberkus: do you have the ticket link handy/
17:05:25 <maxamillion> ?*
17:05:30 <jberkus> nope
17:05:36 <maxamillion> alright, I'll go find it
17:05:36 <jberkus> wasn't tagged with meeting
17:05:44 <maxamillion> ah
17:05:47 <jberkus> #topic open meeting tickets
17:06:03 <jberkus> IRC channels and mailing lists: https://pagure.io/atomic-wg/issue/295
17:06:26 <jberkus> how do I link a specific comment in the issue?
17:06:49 <jberkus> ah, there we go: https://pagure.io/atomic-wg/issue/295#comment-448583
17:07:44 <dustymabe> jberkus: quick question
17:07:50 <jberkus> yah?
17:08:03 <dustymabe> other people when they run the meeting change the topic for each 'ticket' with the meeting tag
17:08:18 <dustymabe> do you intentionally not do it that way?
17:08:41 <jberkus> dustymabe: it's not in the wiki instructions
17:09:01 <jberkus> oh, wait, it is
17:09:08 <jberkus> it's just not tagged as code so I didn't see it
17:09:22 <jberkus> #topic Ticket 295 Mailing lists and IRC
17:09:37 <dustymabe> jberkus: thanks
17:09:50 <jberkus> so this is about our new MLs/IRC for post cloud/atomic split
17:09:50 <dustymabe> #link https://pagure.io/atomic-wg/issue/295
17:09:59 <jberkus> proposal: https://pagure.io/atomic-wg/issue/295#comment-448583
17:10:46 <jberkus> the one open item from that proposal is whether or not the atomic "releng" team actually wants to use the channel #fedora-atomic; dustymabe says yes, maxamillion, roshi etc. weren't sure?
17:11:16 <jberkus> otherwise, we'll just take a confirmational vote and assign updating docs
17:11:32 <gholms> Oh, right.  Which list should people go to for help with fedora atomic?
17:11:49 <dustymabe> gholms: i think the plan is for non-automated email to go to atomic-devel
17:12:00 <maxamillion> jberkus: I'm fine with it, but I won't speak for all of releng
17:12:06 <gholms> Including support questions?
17:12:14 <roshi> not sure I fit the "atomic-releng" team moniker, but I'm fine with it
17:12:16 <gholms> If so then we're all set.
17:12:48 <jberkus> gholms: support questions go to atomic@
17:12:54 <jberkus> atomic@pa.io
17:13:06 <jberkus> although atomic-devel is actually fine
17:13:22 <dustymabe> yeah i don't see a lot of traffic on atomic@
17:13:27 <gholms> That might be worth writing down alongside wherever we write down atomic-devel.
17:13:32 <gholms> Okay, cool.
17:13:38 <jberkus> ok, so voting on the proposal, with that amendment:
17:13:46 <jberkus> vote to confirm?
17:13:50 <gholms> As long as people can find it that's all that matters.  :)
17:14:07 <dustymabe> jberkus: i'd prefer to filter people towards atomic-devel ??
17:14:35 <jbrooks> For support?
17:15:06 <jbrooks> The typical split among projects is project for user Q's project-devel for devel discussion
17:15:48 * gholms has no strong opinions either way, but just wants it written down
17:15:51 <jbrooks> It could probably all go on one list, though -- maybe get rid of one of them in that case
17:16:14 <dustymabe> yeah - i feel like atomic has been more 'announce' type stuff. i hardly ever see messages there
17:16:15 <maxamillion> gholms: same
17:16:28 <maxamillion> I care not what color the bike shed is painted, just that it is in fact painted
17:16:35 <jbrooks> there's atomic-announce too
17:16:59 <jberkus> ok, vote to confirm the proposal with no amendment?
17:17:17 <roshi> +1
17:17:21 <jbrooks> +1
17:17:28 <dustymabe> i like it like it is - pointing people to atomic-devel - so +1
17:17:48 <dustymabe> gholms: 'atomic-devel @projectatomic.io will be used for all mailing list discussions.'
17:17:52 <dustymabe> is how it is written now
17:17:57 <jberkus> how many votes do we need on our new quorum?
17:17:59 <jberkus> oh, and +1
17:18:02 <ksinny> +1
17:18:03 <jbrooks> is irc part of this?
17:18:06 <gholms> Okee dokee
17:18:08 <jberkus> yes, see the proposal
17:18:19 <dustymabe> jberkus: yeah we're basically voting on https://pagure.io/atomic-wg/issue/295#comment-448583
17:18:23 <maxamillion> +1
17:18:27 <dustymabe> known as jberkus' proposal
17:18:48 <dustymabe> also - anyone who has not voted in the ticket, it would be good to get your +1 recorded there
17:19:02 <gholms> +1
17:19:51 <jberkus> if someone can link me the new quorum rules ... maxamillion ?
17:20:16 <jberkus> as an aside, we *may* be moving the pa.io mailing lists to fedora infra
17:20:24 <dustymabe> ksinny: gholms maxamillion roshi etc. can you add your +1 to the ticket
17:20:28 <maxamillion> jberkus: I still need to write them up
17:20:33 <jberkus> ah
17:20:34 <ksinny> done
17:20:39 <roshi> sure
17:20:39 <gholms> Sure
17:20:43 <dustymabe> thanks
17:20:52 <maxamillion> jberkus: doing that now
17:20:56 <jberkus> ok, now where do we need to add this information on IRC and MLs?
17:21:05 <gholms> (poke me after lunch if I forget)
17:21:07 <jberkus> in addition to changing the channels and lists themselves
17:21:12 <jberkus> I need volunteers for some actions
17:21:14 <dustymabe> jberkus: i think we've got enough votes to say this is good for pass
17:21:15 <roshi> done
17:21:22 <dustymabe> jberkus: can you volunteer to do a blog post on the changes?
17:21:25 <jberkus> first, who can get the new ML created?
17:21:34 <dustymabe> jberkus: it's done
17:21:38 <jberkus> dustymabe: sure.  pa.io blog, anywhere else?
17:21:41 <dustymabe> maxamillion: created it some time ago
17:21:44 <jberkus> how about IRC channel?
17:21:48 <dustymabe> jberkus: probably fedora magazine
17:21:52 <jberkus> dustymabe: ok
17:21:54 <dustymabe> IRC channel is created
17:21:57 <dustymabe> i'm in there now
17:22:01 <maxamillion> yeah, I made the new mailing list back in .... Feb?
17:22:13 <dustymabe> i'll change the topic to point people to #atomic mostly
17:22:16 <jberkus> action: jberkus to follow up with Fedora infra about moving pa.io MLs to Fedora infra
17:22:22 <ksinny> maybe adding up at wiki as page as welll https://fedoraproject.org/wiki/Atomic_WG ?
17:22:27 <jberkus> #action: jberkus to follow up with Fedora infra about moving pa.io MLs to Fedora infra
17:22:40 <jberkus> can someone volunteer to update the wiki?
17:23:13 * ksinny will update wiki
17:23:15 <dustymabe> haha - i know roshi is closing his eyes and saying *not me* *not me*
17:23:15 <jberkus> #action:  dustymabe to update IRC channel topics to reflect new scheme
17:23:21 <dustymabe> ksinny, yay!
17:23:29 <jberkus> #action ksinny to update wiki
17:23:38 <roshi> lol
17:23:45 <ksinny> dustymabe: :)
17:23:48 <jberkus> ksinny: can you comment on that ticket when you're done?  since you won't be at meeting next week
17:23:51 <gholms> Thanks!
17:23:51 * roshi spends a ton of time with the wiki - we'
17:23:56 <roshi> re old friends at this point
17:23:57 <ksinny> jberkus: sure
17:24:01 <dustymabe> this wasn't exactly discussed as part of this whole transaction but I'm going to sign up for:
17:24:05 * roshi can type
17:24:17 <dustymabe> #action dustymabe to get a new fedora calendar entry for the Fedora Atomic Working Group meetings
17:24:22 <jberkus> #action jberkus to write blog post for fedora magazine/pa.io on changes
17:24:55 <dustymabe> roshi: do you send wiki birthday presents?
17:25:13 <roshi> wiki was at my wedding
17:25:18 <ksinny> lol
17:25:34 <roshi> we mostly communicate via tcp these days, but sometimes we use some other protocols
17:25:59 <jberkus> ;-b
17:26:01 * gholms submits wiki updates via US Mail
17:26:17 <roshi> RFC-1149 also works
17:26:19 <jberkus> ok, that's done
17:26:30 <jberkus> #topic open floor
17:26:45 <jberkus> if you have an open floor item, please mention it and we'll take them in turn
17:26:47 <dustymabe> jberkus: one more meeting issue
17:26:51 <jberkus> oh?
17:26:56 <dustymabe> sorry i tagged it late
17:27:08 <jberkus> well, let's deal with it in open floor
17:27:11 <dustymabe> ok
17:27:17 <dustymabe> i'll bring it up now
17:27:25 <dustymabe> "Do at least 1-2 more 25 releases, or just switch to /updates "
17:27:33 <dustymabe> #link https://pagure.io/atomic-wg/issue/303
17:27:36 <dustymabe> opened by walters
17:27:53 <dustymabe> please give it a quick read
17:27:59 <strigazi> Will we create the kuberntes-sig in pagure today?
17:28:02 * roshi reads
17:28:12 <walters> it shouldn't be hard to fork the two-week release script to *just* do f25 ostree promotions, no images
17:28:17 <jberkus> strigazi: ok, you're in the queue
17:28:30 <strigazi> jberkus thanks
17:28:46 <jberkus> I have two items for open floor
17:28:53 <dustymabe> walters: do we need to touch the two week script at all?
17:29:00 <jberkus> dustymabe: anything needed for this other than a +1?
17:29:02 <walters> i was thinking fork/copy it
17:29:04 <dustymabe> why not just update bodhi to update the non updates ref?
17:29:15 * roshi doesn't have much of an opinion on how to do it, but +1 to maintaining the F25 atomic tree if we can
17:29:23 <dustymabe> jberkus: mostly looking for discussion and what approach should be taken
17:29:25 <roshi> at least until the EOL messaging is good to go
17:29:28 <walters> well the downside of that it's an at-most-once-a-day trickle of updates with no deltas
17:29:44 <walters> which is a pretty big change
17:30:08 <dustymabe> maxamillion: how do you feel about doing two week releases for f25 ?
17:30:33 <walters> i think we can likely stay on top of the tests for f25 for at least a month or two
17:31:03 <jberkus> I dont' see doing more than two releases
17:31:20 <jberkus> frankly, I'd be arguing against doing any at all except for kube being broken in the initial release of f26
17:32:05 <dustymabe> yeah I really like not doing anything more for f25 other than changing the ref that gets updated
17:32:18 <dustymabe> the kube being broken part will be fixed pretty soon
17:32:27 <roshi> 'releases' in this context is a two-week release, right?
17:32:31 <dustymabe> roshi: right
17:32:41 <roshi> kk, just making sure :)
17:32:44 <jbrooks> And we have the updates ref for f26 now -- kube does work there
17:33:02 <maxamillion> dustymabe: f25 is dead to Atomic Host
17:33:04 <jbrooks> I think shunting f25 to the updates ref is just fine
17:33:16 <dustymabe> maxamillion: that's kinda how I feel
17:33:27 <jbrooks> It's dead to me ;)
17:33:35 <dustymabe> i know that is not really being nice to *some* users
17:33:39 <roshi> it'll never be the wiki to me
17:33:40 <roshi> :p
17:33:43 <maxamillion> dustymabe: I would need a really compelling argument or a majority vote to change my mind on that
17:34:06 <dustymabe> ok so i think there are a few options
17:34:19 <dustymabe> - fixup two week release script and do more 25AH releases
17:34:37 <dustymabe> - point bodhi at release ref and start updating that ref every night when bodhi runs
17:34:44 <dustymabe> - do nothing and tell people to rebase to the updates ref
17:34:54 <gholms> Ooh, F26 updates works?  Awesome.
17:35:02 <jbrooks> and testing
17:35:07 <dustymabe> gholms: yeah - got that wired up last week
17:35:19 <jbrooks> dustymabe, option two seems best
17:35:41 <jbrooks> No work required from the user
17:35:42 <maxamillion> I like option two as well
17:36:07 <maxamillion> I like the idea of Atomic Host being an always-updating-to-latest platform (which I thought was kind of the point0
17:36:10 <dustymabe> walters: i know option 2 isn't the most ideal (updates every day and no static deltas), but i think in our 'look forward not back' mindset right now it would be best
17:36:17 <walters> ok
17:36:24 <dustymabe> maxamillion: yeah - we're getting there
17:36:25 <jberkus> maxamillion: it will be (hopefully) for f27
17:36:29 <dustymabe> to where we can offer the user that option
17:36:40 <walters> hopefully we'll get to updates batches for the rpm set as well
17:36:44 <jbrooks> heh, option
17:36:58 <dustymabe> #proposed for f25AH point bodhi at release ref and start updating that ref every night when bodhi runs
17:37:00 * gholms can't get on board with that as long as we ship broken images, but appreciates the idea
17:37:00 <walters> and then we can do deltas usefully between those when this happens again
17:37:10 <walters> i.e. for f27
17:37:30 <jberkus> ok, let's wind this up.  can someone write up on this ticket how the updates will work for last-f25
17:37:40 <jberkus> and then someone can write a blog post?
17:37:42 <dustymabe> sure
17:38:08 <dustymabe> #action dusty to put in place updating of last f25 ref automated via bodhi
17:38:19 <jberkus> ok, blog poster?
17:38:30 <dustymabe> jberkus: i can include that in the blog post I am writing
17:38:44 <jberkus> #action dustymabe to write blog post about last f25 updates
17:38:47 <jberkus> ok, next item
17:38:50 <jberkus> strigazi
17:38:52 <dustymabe> #action dusty to write a comprehensive blog post on updating f25->f26 and will include update about f25 updates ref
17:39:21 <strigazi> #link https://pagure.io/atomic-wg/issue/287
17:39:25 <jberkus> we voted last time to create a pagure project for kubernetes, no?
17:39:43 <strigazi> Yes, that was the conclusion of 287
17:40:11 <jberkus> so, who can create one? looks like anybody
17:40:29 <dustymabe> #action dustymabe to create kubernetes-sig pagure repo and notify interested parties
17:40:41 <strigazi> thanks dustymabe
17:40:44 <jberkus> is there any way to "move" issues from one repo to another?
17:40:58 <strigazi> good question
17:40:59 <roshi> don't think so
17:40:59 <dustymabe> jbrooks: are you interested in taking on somewhat of a leader role for that group?
17:41:05 <roshi> just have to duplicate it I think
17:41:07 <jbrooks> dustymabe, sure
17:41:10 <roshi> dupe and close
17:41:13 <dustymabe> jberkus: not right now - but I've requested that feature
17:41:26 <jberkus> ok.
17:41:30 <dustymabe> jberkus: awesome!
17:41:41 <dustymabe> grr jbrooks awesome!
17:41:44 <jberkus> #action jberkus to re-create issues in new repo
17:42:10 <jberkus> so let me know when it's ready
17:42:12 <dustymabe> i'm not sure how many really need to be re-created at this point
17:42:14 <jberkus> ok, next topics
17:42:17 <strigazi> jberkus I have one more sort of related item
17:42:22 <jberkus> dustymabe: there's a handful
17:42:25 <jberkus> strigazi: go ahead?
17:42:42 <dustymabe> jberkus: can you make sure they are all tagged with k8s ?
17:42:43 <strigazi> It is related to running kube in system containers
17:43:08 <strigazi> It would be nice if we could tag images with their version
17:43:23 <jbrooks> Yeah, I've been thinking about this
17:43:26 <strigazi> eg etcd:fc26_v3.x.x
17:43:34 <jberkus> they are
17:43:46 <jbrooks> I know we're going w/ release=0 for now
17:44:13 <jbrooks> until we can automate it, but I've been wondering if it'd be worth putting in a legit version # manually for the kube containers
17:44:42 <strigazi> sounds like an acceptable workaround
17:44:59 <jbrooks> On a similar issue, maxamillion, it'd be nice if the rawhide ones were getting auto-built, so we could point ppl to 1.7-based containers
17:45:10 <maxamillion> jbrooks: auto-built?
17:45:14 <dustymabe> jbrooks: i discussed this very issue with maxamillion last night
17:45:19 <jbrooks> The images
17:45:19 <maxamillion> RPMs aren't auto-built, why would containers?
17:45:29 <jbrooks> Ok, then, built
17:45:35 <jbrooks> by whatever means
17:45:35 <maxamillion> they're built now
17:45:41 <maxamillion> fedpkg switch-branch master
17:45:44 <maxamillion> fedpkg container-build
17:45:47 <jbrooks> Oh yeah? I thought you had to do them one-off
17:45:47 <maxamillion> rawhide container build
17:45:51 <maxamillion> nope
17:46:00 <jbrooks> So on what schedule do they build?
17:46:01 <maxamillion> they aren't *released*
17:46:04 <jbrooks> Ok
17:46:04 <maxamillion> but they are built
17:46:05 <jbrooks> right
17:46:11 <jbrooks> Released is what I mean
17:46:12 <maxamillion> what schedule? I don't understand
17:46:16 <maxamillion> they are built whenever you build them
17:46:22 <jbrooks> got it
17:46:27 <jbrooks> released
17:47:10 <dustymabe> ok - can i summarize ?
17:47:21 <dustymabe> i think what jbrooks is asking for is what I asked maxamillion about last night
17:47:39 <dustymabe> basically when an rpm gets built in rawhide it becomes availabe in the rawhide repos within a day
17:47:59 <dustymabe> jbrooks: is most likely wanting something similar from the container registry for containers that are built from rawhide rpms
17:48:00 <maxamillion> right now they are not released since they aren't stable content and that's a whole grey area ... I'm open to releasing them but right now that's just piling on more manual process to the container release process because right now there's various parts I don't have a good way to automate while we wait for factory2.0 (freshmaker) and osbs upstream features for the automatic rebuilds (the
17:48:06 <maxamillion> mapping of parent image inheritance is the pain point)
17:48:21 <jbrooks> right -- My apiserver container depends on registry.fedoraproject.org/f27/kubernetes-master:latest, and that depends on releases happening
17:49:16 <dustymabe> tl;dr i'm creating an issue to track this feature - but it's not going to happen soon because tooling needs to be built out to make this automated
17:49:17 <jbrooks> And if I tell someone, try out 1.7 on atomic by pulling XX image... that would also depend on releases -- either we need them in fedora or maybe we use the projectatomic docker hub namespace...
17:49:24 <dustymabe> so it is not an extra manual step for maxamillion
17:49:38 <jbrooks> OK, maybe I'll take that docker hub route for now
17:49:40 <dustymabe> jbrooks: see my tl;dr
17:49:52 <jbrooks> yeah
17:50:03 <dustymabe> sound reasonable? - this is something we want, just can't have it right now
17:50:41 <strigazi> So, for now we will have only the latest tag?
17:50:44 <jbrooks> it'll have to do
17:51:02 <walters> i'm not sure how useful the whole fedora branching model becomes with containers
17:51:13 <walters> really this is where modularity intersects
17:51:16 <maxamillion> yeah
17:51:25 <maxamillion> this is going to get messy fast
17:51:33 <walters> like IMO i think we should have say the last two major versions of kube as containers
17:51:49 <jbrooks> Some of this stuff -- it sort of approaches a break point where... is it worth pointing ppl to the fedora registries
17:51:51 <jberkus> ok, can we move this to a longer discussion somewhere else?
17:51:57 <jberkus> we still have two items
17:52:00 <jbrooks> OK
17:52:05 <strigazi> ok
17:52:06 <dustymabe> i'll create that ticket
17:52:09 <dustymabe> and we can discuss there
17:52:32 <jberkus> #action kubernetes-sig to discuss version tagging for kube system containers
17:52:41 <jberkus> ok, next itme
17:52:43 <jberkus> docs VFAD
17:52:52 <dustymabe> jberkus: i think that's a broader discussion - not juts for kube sig
17:52:58 <dustymabe> but, continue
17:53:16 <jberkus> tentatively we have a docs vfad scheduled for next week
17:53:39 <dustymabe> Friday July 28th
17:53:49 <jberkus> ok
17:53:52 <ksinny> Are we going to record Bluejeans discussion?
17:53:52 <dustymabe> #link https://pagure.io/atomic-wg/issue/294
17:54:08 <dustymabe> see proposed schedule: https://pagure.io/atomic-wg/issue/294#comment-448582
17:54:10 <jberkus> ksinny: for which?
17:54:23 <ksinny> jberkus: VFAD
17:54:30 <jberkus> yes
17:54:38 <ksinny> there are few sessions going to occur over bluejeans
17:54:43 <ksinny> ok, cool
17:54:58 <jberkus> so, FYI, I'm working on ad-hoc;ing CI/CD and doc hosting for the new asciibinder docs
17:55:17 <jberkus> I will try to get this set up far enough ahead of time so that people can set up their environments
17:55:59 <jberkus> ad-hoc'ing because still waiting on OpenShift Online hosting :-(
17:56:35 <dustymabe> jberkus: hmm - so this VFAD i think is less about the CI/CD doc stuff and more about finding existing docs, identifying gaps in docs, and organizing existing docs
17:56:54 <dustymabe> and planning the flock session so we can be super productive there
17:57:06 <dustymabe> am i missing anything?
17:57:14 <jberkus> dustymabe: we really don't want to be writing more docs in middleman
17:57:20 <jberkus> which will mean more docks to manually convert
17:57:48 <dustymabe> none of what I said included writing docs
17:57:50 <dustymabe> FYI
17:57:54 <jberkus> ah, ok
17:57:59 <jberkus> sure
17:58:01 <jberkus> that works
17:58:30 <jberkus> I do want ot have an alpha of the ci/cd system just so that the vfad can also give me feedback on it
17:58:33 <jberkus> before flock
17:58:35 <dustymabe> basically let's crawl all of our spaces where docs currently exist. index everything, come up with a plan for how to better organize them
17:58:38 <dustymabe> and what is missing
17:58:44 <jberkus> ok
17:58:57 <dustymabe> jberkus: that's why it's called "Docs Treasure Hunt"
17:58:59 <dustymabe> :)
17:59:10 <jberkus> #action dustymabe jberkus to write doc on docs vfad with all resources linked
17:59:32 <dustymabe> jberkus: after the fad or before?
17:59:36 <jberkus> ok, I was goign to bring up flock workshops, but we'll hold that for next week
17:59:42 <roshi> an odd definition of "treasure" :)
17:59:42 <jberkus> dustymabe: we need  prep page
17:59:47 <jberkus> on the wiki
18:00:05 <dustymabe> ok i was just thinking we would throw up and etherpad and go from there
18:00:15 <jberkus> ehterpad works too
18:00:18 <jberkus> just somewhere
18:00:21 <dustymabe> k
18:00:36 <jberkus> dustymabe: for oen thing, trish already identified a lot of things
18:00:40 <jberkus> trishna
18:00:47 <jberkus> ok, time's up
18:00:56 <jberkus> #endmeeting