17:00:17 <mattdm> #startmeeting Council (2015-07-20)
17:00:17 <zodbot> Meeting started Mon Jul 20 17:00:17 2015 UTC.  The chair is mattdm. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:17 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:00:18 <mattdm> #meetingname council
17:00:19 <zodbot> The meeting name has been set to 'council'
17:00:20 <mattdm> #chair mattdm jreznik jwb cwickert rdieter langdon sgallagh decause
17:00:20 <zodbot> Current chairs: cwickert decause jreznik jwb langdon mattdm rdieter sgallagh
17:00:22 <mattdm> #topic Introductions, Welcomesy
17:00:30 <mattdm> Hi everyone!
17:00:31 <decause_OSCON> .hello
17:00:31 <zodbot> decause_OSCON: (hello <an alias, 1 argument>) -- Alias for "hellomynameis $1".
17:00:37 <langdon> .hello langdon
17:00:40 <zodbot> langdon: langdon 'Langdon White' <langdon@fishjump.com>
17:00:48 <decause_OSCON> .hello decause
17:00:49 <sgallagh> .hello sgallagh
17:00:49 <zodbot> decause_OSCON: decause 'None' <decause@redhat.com>
17:00:52 <zodbot> sgallagh: sgallagh 'Stephen Gallagher' <sgallagh@redhat.com>
17:01:09 <mattdm> hi remy, langdon, stephen!
17:01:17 <langdon> hi!
17:01:20 <decause_OSCON> hi there
17:01:21 <sgallagh> mattdm: Welcome back
17:01:41 <mattdm> thanks! been digging out all morning, can almost see the surface of the ground
17:01:45 <mattdm> at least, I think that's ground
17:01:58 <jwb> hello
17:02:02 <mattdm> hi josh!
17:02:55 * mattdm waits a few minutes for cwickert, jkurik, rdieter_work
17:03:10 * mattdm updates template to s/jreznik/jkurik/
17:03:48 <kushal> .hellomynameis kushal
17:03:49 <zodbot> kushal: kushal 'Kushal Das' <kushaldas@gmail.com>
17:03:56 <mattdm> hi kushal!
17:04:02 <mattdm> for the record...
17:04:04 <mattdm> #link https://fedoraproject.org/wiki/Council_meeting_process
17:04:15 <mattdm> is a handy template for running a Council IRC meeting
17:05:01 <mattdm> Okay, let's go ahead and get started.
17:05:04 <mattdm> #topic Today's Agenda
17:05:24 <mattdm> By the council meeting schedule, this is our tickets and ongoing work checkin
17:05:37 <mattdm> as I said on the mailing list, i don't want us to get in the habit of being bound by that...
17:05:46 <mattdm> but we should also make sure we don't forget to go through things.
17:05:50 <mattdm> So:
17:06:01 <mattdm> 1. Globalization FAD request
17:06:05 <mattdm> 2. PRD reviews
17:06:11 <mattdm> 3. Dopr service
17:06:17 <mattdm> 4. Fedora Student
17:06:25 <mattdm> 5. Who do we want next for subproject status report?
17:06:28 <mattdm> Anything else?
17:06:44 <decause_OSCON> flock council session?
17:07:06 <mattdm> decause_OSCON: hmmm maybe make that the focus of next week's open floor?
17:07:13 <decause_OSCON> kk
17:07:21 <decause_OSCON> +1
17:07:27 * mattdm makes note
17:07:31 <mattdm> oooh
17:07:51 <mattdm> #info next week we'll make the Flock council session the focus of the meeting
17:08:21 <mattdm> #topic Globalization FAD request
17:08:31 <mattdm> #link https://fedorahosted.org/council/ticket/39
17:09:02 <mattdm> I'm generally in favor of this. I'm generally in favor of anything that brings unity and cohesiveness to some of our scattered groups
17:09:21 <mattdm> The requested budget is a little high for a fad -- usually those target $5k or so
17:09:42 <mattdm> #link https://fedoraproject.org/wiki/FAD_G11N_2015
17:10:19 <langdon> isnt 3 days longer than normal (perhaps resulting in >5k)?
17:10:49 <jwb> yeah, i'm a bit concerned where the money would come from
17:10:51 <mattdm> langdon: I think the releng fad was 4. they kind of vary.
17:10:59 <jwb> particularly with the number of FADs we've had recently
17:11:11 * langdon might be only attending 1-2 days of fads that are longer :)
17:11:37 <mattdm> It also isn't directly aligned with one of our medium-term objectives, even though as the proposal shows, it clearly benefits our _general_ objectives.
17:11:53 <mattdm> decause_OSCON: as the OSAS connection, can you look into the budget situation?
17:12:23 * jwb notes that Ruth is on PTO
17:12:46 <mattdm> isn't ruth at OSCON with decause_OSCON?
17:13:02 <decause_OSCON> mattdm: yes, to both
17:13:07 <jwb> hm.  i might be mixing her schedule up then
17:13:07 <mattdm> ah :)
17:13:12 <jwb> i know it's crazy the next few weeks
17:13:25 <mattdm> yeah. summer. :)
17:13:26 <jwb> anyway, the total budget is already noted at $6445
17:13:28 <jwb> so more than 5k
17:13:49 <jwb> and that's just travel
17:13:53 <jwb> another $2200 for hotel
17:14:33 <mattdm> it does look like they're getting that 2200 from Red Hat's G11N group rather than needing Fedora funding
17:14:55 <jwb> not confirmed
17:15:30 <mattdm> So, I guess we really need to know what the budget situation is before confirming this.
17:15:40 <sgallagh> Also they're asking for $550 for a social event.
17:15:47 <sgallagh> Err, $555
17:15:55 <sgallagh> So a total of $7000 from the Fedora coffers.
17:16:06 <jwb> yeah.  so the total request is either $7k or $9220
17:16:54 <jwb> might as well round up to $10k, since the longer we delay, the more likely flight costs go up
17:17:27 <mattdm> I'm not aware of any competing FAD proposals currently. If the money _is_ available in the budget, would we want to commit it to this, or hold back for other possible FADs?
17:18:07 * jwb shrugs
17:19:19 <mattdm> I guess I am inclined to vote for it (assuming availablity of funds, or possibly for a reduced-funding version), unless there are in-the-works plans for a FAD more closely aligned with immediate objectives
17:19:37 <mattdm> But that vote is definitely conditional on the state of the budget
17:20:03 <mattdm> decause_OSCON can you #action yourself to discuss that with ruth when she is not on PTO?
17:20:20 <decause_OSCON> yes
17:20:36 <mattdm> decause_OSCON: thanks :)
17:20:46 <decause_OSCON> #action decause talk to ruth about budgegt
17:21:01 <mattdm> Does anyone think this is a _bad_ use of Fedora's FAD funds?
17:21:27 <jwb> no.  and to be honest, i don't like the unless part.  seems easy to game.  should be first come first serve
17:22:36 <mattdm> I *would* like to see people laying out their plans for these earlier, so we can weigh better. I _don't_ think first come first serve is necessarily the best for the project given our limited resources.
17:23:00 <decause_OSCON> quarterly deadlines could help
17:23:02 <mattdm> But I also have a lot of sympathy in favor of people who actually do the planning work for something like this.
17:23:32 <jwb> i just don't want someone to see "oh, the council has $10k to spend.  quick, let's throw together a FAD around Cloud"
17:23:39 <jwb> (not picking on cloud)
17:23:45 <mattdm> decause_OSCON: yeah. can you work on a plan for that? seems in line with your role :)
17:24:05 <jwb> we should also note that as the fiscal year moves on, funds become much harder to come by
17:24:08 <kushal> jwb, awww :p
17:24:14 * decause_OSCON needs to have an
17:24:22 <mattdm> jwb: oh, definitely. I meant specifically to prioritize FADs in line with the approved 12-18 Month Community Objectives
17:24:29 <decause_OSCON> proper full discussion on budgetg
17:25:13 <mattdm> in the meantime, since we're 25 minutes in... let's take this back to the mailing list and ticket, awaiting update from Remy on budget
17:25:16 <decause_OSCON> #action decause set a meeting with mattdm abd ruth about highlevel budget process
17:25:30 <mattdm> #topic PRD reviews
17:25:55 <mattdm> So, I don't want to actually *talk* about these here
17:25:59 <mattdm> I just want to remind everyone of
17:26:06 <mattdm> #link https://fedorahosted.org/council/ticket/31
17:26:16 <mattdm> #link https://fedorahosted.org/council/ticket/32
17:26:21 <mattdm> #link https://fedorahosted.org/council/ticket/36
17:26:34 <mattdm> #info that's updated PRDs for Server, Workstation, and Cloud
17:26:51 <mattdm> people put a lot of work into those, so we owe them at least an ACK
17:27:12 <mattdm> </end nagging>
17:27:25 <mattdm> I'm including myself in the nagging there, too, of course. :)
17:27:43 <mattdm> and moving on :)
17:27:47 <mattdm> #topic DOPR service
17:28:05 <mattdm> #link https://fedorahosted.org/council/ticket/38
17:28:15 <mattdm> we had some discussion about this in the ticket
17:29:25 <mattdm> I think it's a generally cool idea, but I have a lot of concerns
17:29:50 <mattdm> If I'm the council member who cares about it the most, I guess I can continue to work on those concerns
17:29:59 <mattdm> anyone else have input?
17:30:13 <mattdm> #action mattdm to continue working on this
17:30:28 <langdon> mattdm, i have a bit over concern with overlapping service with centos
17:30:40 <langdon> but... that isn't really a "trademark" question
17:31:13 <mattdm> langdon well, if we're putting the fedora trademark on centos, that seems like a trademark question :)
17:31:20 <langdon> lol
17:31:31 <langdon> i meant centos infra is also building something similar
17:31:39 <langdon> like a "docker build service"
17:31:50 <langdon> that can build fedora images IIRC
17:32:24 <jwb> that's not confusing at all.
17:32:35 <mattdm> is it the same Red Hat team working on both, or different?
17:32:41 <langdon> jwb, its docker.. everything is possible
17:32:56 <langdon> mattdm, the ssame?!?! of course not
17:32:56 <mattdm> and aobut 1% of it is advisable!
17:33:05 <jwb> langdon, it's software.  everything is possible.  that doesn't mean it's a great idea.
17:33:29 * langdon mutters should remember some Jurassic park quote here
17:33:41 <jwb> langdon, i know exactly which you mean
17:33:53 <langdon> so.. the goals are slightly different, of course... but the output is kind of the same
17:33:59 <mattdm> nuke it from orbit! it's the only way to be sure.
17:34:22 <mattdm> wait, wrong movie.
17:34:35 <langdon> i also think spot's idea and your idea (#13 and #14) are really the way to go.. i don't think I ever realized they would show up in the "fedora account"
17:35:59 <mattdm> what if we asked them to get a specific, new account "Fedora DOPR" or something, to distance it from the official Fedora-produced images?
17:36:30 <kushal> mattdm, the name is still there.
17:36:37 <kushal> *Fedora*
17:36:41 <langdon> mattdm, i wouldn't want that as a user.. right? i want the "credit" for the images.. maybe? and.. kushal +1
17:36:49 <kushal> That will be enough to confuse people.
17:37:30 <decause_OSCON> how do other distros deal with it?
17:37:41 <mattdm> they don't have any cool service like this.
17:37:42 <langdon> so.. i would suggest that the next step is to try to get a meeting together between the cent folks and the fedora folks working on this.. then maybe see what the actual goal/requirements are.. cause.. like.. i am not sure I see the point in copr->d-file->docker-hub under u/fedora
17:37:43 * decause_OSCON is a docker hub n00b
17:38:15 <langdon> d-file -> /u/langdon .. now that might make sense in the way copr does...
17:38:31 <jwb> langdon, yeah, agreed
17:38:35 <langdon> i put something together i want to share with people while it grows up
17:38:50 <mattdm> the objection, I guess, is that upstream Docker doesn't have an API for this, so we'd have to hold their credentials
17:39:38 <jwb> only if we wanted auto-sync
17:39:49 <langdon> mattdm, yeah.. i don't know.. i am just not sure I understand the goal
17:39:57 <jwb> if we built the image (?) and then told the user it's there, they could download/upload themselves
17:40:06 <jwb> i mean, ideally they'd do that anyway to make sure it isn't totally broken
17:40:34 <langdon> jwb, well.. and why wouldn't they just use a webhook from github->docker
17:40:49 <langdon> like where is the "copr advantage"? or stuff
17:41:09 <langdon> or even generic git repo -> commit hook -> docker hub
17:41:27 <mattdm> langdon: can you organize meeting with the dopr people and centos people?
17:41:35 <jwb> if the only advantage is auto-syncing, i'm not sure it's really worth proping up resources to do that
17:42:08 <langdon> mattdm, yeah.. i can try.. i am not sure it will be an easy answer though
17:42:13 <mattdm> "auto-syncing" sounds trivial. But it's more than that -- it's "push a button and my copr is available as a docker image"
17:42:27 <jwb> so why wouldn't we just make that another output of copr itself?
17:43:12 <mattdm> jwb: for that to really work, copr would have to act as a docker registry
17:43:16 <jwb> and?
17:43:18 <langdon> well.. when i had discussed this a while ago.. it was "copr build -> fedmsg -> docker-b-service -> fedmsg -> user can go get the image" .. perhaps in a registry perhaps as a tar
17:44:04 <mattdm> #action langdon to try to get team working on this talking with centos
17:44:23 <langdon> so.. i say.. let's stop the convo here.. and ill invite you to the meeting.. and we can get answers vs just theorizing
17:44:36 <mattdm> langdon++
17:44:36 <zodbot> mattdm: Karma for langdon changed to 4:  https://badges.fedoraproject.org/tags/cookie/any
17:44:51 * langdon wonders if this should be an envs&stacks "ticket"
17:44:51 <mattdm> also, looking at clock anyway. further dicussion back to ticket and lists!
17:45:09 * decause_OSCON could stand to learn a lot from this, so please keep me in the loop langdon :)
17:45:17 <mattdm> well, the trademark is still on us. but maybe we can say -- waiting on trademark until some technical issues are resolved.
17:45:25 <mattdm> anyway next topic
17:45:30 <mattdm> #topic Fedora Student
17:45:30 <decause_OSCON> #agreed
17:45:34 <mattdm> kushal ping :)
17:45:38 * langdon will invite council, optionally
17:45:40 <kushal> oops
17:45:43 <decause_OSCON> kushal++
17:45:55 <kushal> * typing
17:46:16 <kushal> So I had a meeting with decause_OSCON, we both agreed that this is a good idea to go forward.
17:46:28 <decause_OSCON> #agreed
17:46:50 <decause_OSCON> additionally, a fedora badge would be great too
17:47:07 <jwb> #undo
17:47:08 <zodbot> Removing item from minutes: <MeetBot.items.Topic object at 0x3a4e4750>
17:47:21 <kushal> But till the time the design for the letter pad gets ready, and decause_OSCON creates something like letterhead@fedoraproject.org for the same kind of workflow of logos, I need the permission to get the students start working.
17:47:30 <jwb> decause_OSCON, so let's not use zodbot commands for personal agreement
17:47:39 <mattdm> context, btw:
17:47:42 <mattdm> #link https://fedorahosted.org/council/ticket/37
17:47:50 <kushal> For the same, I need the permission of the council :)
17:47:55 <decause_OSCON> jwb: understood
17:48:06 <mattdm> and of course ties into
17:48:08 <mattdm> #link https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative
17:48:18 <decause_OSCON> ye
17:48:27 <decause_OSCON> yep*
17:48:31 <mattdm> yeah, I'm in favor of this. +1
17:48:36 <langdon> so.. kushal decause_OSCON is this to answer "just" the ticket? or more broadly than that? i am not quite sure i understand where it has evolved too?
17:49:35 <kushal> langdon, to start with, just the ticket, meanwhile decause_OSCON will come up with the wiki pages along with the full plan/workflow, I will help him out with this as required.
17:49:37 <langdon> there also seems to be disagreement in the ticket about the "physicality" of the output
17:49:44 <langdon> kushal, ack
17:49:59 <decause_OSCON> from what i understand, having a template for a Fedora certificate and letter head will be useful outside of just Kushals usecase
17:50:17 <kushal> decause_OSCON, +1
17:50:24 * langdon is in favor of a physical cert as an addition (for "coolness" reasons) to a digital proof for the university
17:50:33 <jwb> i'm confused who these students are that are waiting on a certificate from us, and what they've actually done
17:50:48 <decause_OSCON> spinning up an analog to logo@fp.o to request letterhead
17:50:59 <kushal> langdon, so we will give them actual letters explaining the work.
17:51:02 * mattdm is okay with signing physical certificates as long as it is not a daily chore :)
17:51:20 <decause_OSCON> nod nod
17:51:42 <jwb> specifically, this comment:
17:51:45 <jwb> "There are many students who are waiting for a response from us for long time on the same. So fast tracking this will help us a lot."
17:51:46 * langdon notes, they make stampers.. and we could put all the council members on it with like 50 bucks in stampers ;)
17:52:03 <kushal> jwb, student can be anyone who wants to do an unpaid project work under Fedora, any upstream contributor can mentor them. Only a few selected ones will have the letterheads to print and sign.
17:52:17 <jwb> kushal, so who is waiting on us?
17:52:33 <kushal> jwb, so at least in India we keep getting emails from various college students who wants to work under Fedora project.
17:52:42 <jwb> because i don't want to retroactively approve this for a bunch of people that we then have to go and verify the work they actually did
17:52:52 <langdon> jwb, i think the phrasing is off
17:53:08 <kushal> jwb, No work has been done yet.
17:53:12 <langdon> jwb, i think kushal means he has peeps who could *do* work if they had a way to get credit
17:53:19 <jwb> hence my question
17:53:21 <kushal> lalatenduM, +1
17:53:24 <kushal> oops
17:53:26 * langdon notes, he read it the way jwb did
17:53:27 <kushal> langdon, +1
17:53:44 <jwb> i'm fine with this if it's a fresh start going forward
17:53:56 <jwb> though i'm curious what work qualifies
17:54:01 <decause_OSCON> now can i #agree
17:54:03 <decause_OSCON> ?
17:54:07 <decause_OSCON> ;)
17:54:13 <mattdm> decause_OSCON: sooooon :)
17:54:16 <jwb> decause_OSCON, no, because blank #agree isn't informative
17:54:17 <kushal> jwb, Yes, this is for a fresh start, students can work for 1 month, or much longer time.
17:54:27 <jwb> kushal, right.  but what kind of project qualifies?
17:54:28 <kushal> decause_OSCON, #agree with a text :)
17:54:30 <mattdm> kushal: do you have an example of a specific project?
17:56:09 <kushal> jwb, mattdm For example previously students worked on getting particular features into ask-fedora upstream+packaging the dependencies.
17:56:09 <kushal> jwb, mattdm they have worked for desktop applications.
17:56:10 <jwb> so should decause_OSCON be tasked with approving a project before work begins as the University/outreachy guy?
17:56:10 <kushal> jwb, mattdm Projects like GSOC level.
17:56:10 <jwb> who's tracking that?
17:56:10 * decause_OSCON is more than willing to do so
17:56:23 <kushal> Actually lesser than GSOC in many cases.
17:56:24 <jwb> the idea in general is great.  we just need to make sure the details are handled
17:56:26 <langdon> can i propose something else... i am not sure i care how *much* work it is .. as long as it is "formal" ... so .. i think to be eligible for a letter... you must have 1) written a formal proposal with goals and deadlines 2) have a mentor who approves 3) complete on time (as assessed by mentor)
17:56:41 <jwb> langdon, yes, excellent
17:56:42 <kushal> jwb, Yes, there should be accountability.
17:56:52 <mattdm> langdon: *nod*
17:56:58 <decause_OSCON> langdon: nailed it
17:57:08 <kushal> jwb, langdon, yes,we can easily lend the rules from gsoc stories we do under Fedora project.
17:57:13 <kushal> same style.
17:57:48 <langdon> and... my "3" there is to allow the mentor to "adjust" the timeline in their judgement of the "scene on the ground"
17:57:50 <kushal> mattdm, also it should not required for you to sign the letters physically all the time, as sending them out is costly based on the place :)
17:58:06 <kushal> langdon, I thought that is given :)
17:58:21 <langdon> kushal, mattdm i disagree.. i think the "physical paper" is important.. but i could just be old
17:58:33 <langdon> if we need to find budget for it, let's do it
17:58:46 <kushal> langdon, what I am saying is that the physical paper does not have to be signed by FPL
17:58:58 <decause_OSCON> that letter in the mail won't be prohibitively expensive
17:59:04 * mattdm can make a rubber stamp with his signature
17:59:17 <langdon> kushal, we can make a stamp of matt's sig, and get 3 of them made.. put them around the world
17:59:21 <kushal> langdon, the local mentor (or the person in charge with letter heads) can sign along with the digital signature of the FPL>
17:59:40 <kushal> langdon, Yes, any similar idea :)
17:59:40 <langdon> and decause_OSCON +1
17:59:41 <mattdm> kushal how many of these are we talking about?
17:59:46 <decause_OSCON> what a wonderful problem to have: "too many students need letters approving their contributions"
17:59:54 <langdon> 40 a day </snark>
17:59:55 <mattdm> decause_OSCON true!
18:00:09 <langdon> i am in favor of matt having to spend all day signing these things :)
18:00:15 <mattdm> langdon: lol
18:00:24 <mattdm> I know you're not joking, is the sad part :)
18:00:30 <kushal> mattdm, It depends, if we are okay to go with small scale project works, then 10+ students in any month is easy.
18:00:45 <langdon> mattdm, well.. it was really to decause_OSCON
18:00:48 <langdon> 's point
18:00:51 <mattdm> Anyway, I'm okay either way :)
18:00:52 <kushal> with enough mentors, we can get 50-100 students :)
18:01:03 * langdon holds breath
18:01:23 <kushal> From a country where a million+ engineering students are passing out every year, number is always high :)
18:01:24 <mattdm> Since it's 2:00... can we get some of the specifics like langdon put forth in the ticket, and then do final approval there?
18:01:30 * decause_OSCON is happy to sign as many as necessary
18:01:48 <kushal> decause_OSCON, you still have to send them from USA to India, which is freaking expensive.
18:02:15 <kushal> decause_OSCON, that is why I am asking for local responsible mentors whom you approve with letterheads :)
18:02:24 <decause_OSCON> sign, scan, print locally?
18:02:37 <jwb> afk for a few min
18:02:39 <kushal> decause_OSCON, that is the digital signature I was talking about :)
18:03:04 <langdon> FAX!
18:03:06 <mattdm> kushal: is $2.38.
18:03:10 <mattdm> I can handle this :)
18:03:21 <kushal> Oh okay :)
18:03:27 <decause_OSCON> agreed
18:03:38 <kushal> Btw, passing out == Getting the college engineering degree
18:03:48 <kushal> In this case :p
18:04:00 <mattdm> in the US college students pass out from other causes
18:04:09 <kushal> rofl
18:04:16 <decause_OSCON> overstuduiousness mostly
18:04:24 <Southern_Gentlem> lol
18:04:24 <mattdm> decause_OSCON yes, of course.
18:04:35 <mattdm> anyway. let's take this to the ticket
18:04:44 <mattdm> #topic subproject report for august 3rd?
18:04:57 * mattdm checks calendar
18:05:00 <mattdm> #info that's definitely a monday
18:05:21 <mattdm> by the schedule I put forward, we'd do another subproject report in two weeks
18:05:39 <mattdm> I don't have anyone lined up... is there a particular group y'all'ld like to hear from?
18:06:37 <decause_OSCON> whos left?
18:06:52 <mattdm> SO much.
18:07:08 <decause_OSCON> interns? not a subproject, but would be good timing
18:07:30 <mattdm> docs, design, ambassadors (including various regions), all the g11n stuff, and a lot more
18:07:39 <decause_OSCON> they span many projects, but there is some *great* work coming in
18:07:48 <langdon> mattdm, who have we done so far? we need to make a page with a list and links to the videos
18:08:08 * decause_OSCON should get that action item
18:08:13 <mattdm> langdon: marketing, qa, and the engineering overview which I haven't watched yet.
18:08:21 <langdon> right after we make the "org structure" pic :)
18:08:30 <mattdm> and fedora editions
18:08:56 <decause_OSCON> these are commops tasks
18:09:06 <mattdm> decause_OSCON yes please :)
18:09:43 <decause_OSCON> #action decause commops create council report page with links to video
18:09:54 <mattdm> decause_OSCON So speaking of which, do you think your commops thing will be in solid enough initial form to report on in two weeks?
18:10:33 <langdon> sorta speaking of... whatever happened to the "contributor blog" conversation?
18:10:40 <decause_OSCON> with oscon, prolly not. the initial meeting happened, but we're going to need to build more steam
18:10:44 <langdon> cause this content might be good on their too
18:10:54 <langdon> *there
18:10:57 <mattdm> langdon: dunno. I need to ask ryan about that.
18:11:06 <mattdm> and yeah, that would be exactly the place for this.
18:11:16 <mattdm> decause_OSCON: okay. :)
18:11:24 * langdon knows the "there" he wants.. but his fingers decide on other one(s)
18:11:34 <mattdm> so, without any other suggestions, maybe I'll ask design team?
18:11:58 <langdon> mattdm, decause_OSCON maybe commops should ask design, no?
18:12:04 <decause_OSCON> what about g11n? they propsed that fad?
18:12:10 <langdon> right? cause it "should be" in their wheelhouse?
18:12:35 <langdon> their = commops..
18:12:40 * mattdm does not much care who does the asking :)
18:13:11 <mattdm> decause_OSCON: okay, sure, g11n it is. :)
18:13:20 * langdon doesn't care which human.. but which org matters for long term ownership
18:13:26 <mattdm> #action mattdm to ask new g11n team if they want to present on efforts in two weeks
18:13:54 <decause_OSCON> mattdm++
18:14:07 <mattdm> langdon: I'm okay with doing it for the purposes of organizing the council meetings. I agree that design is commops-aligned in general
18:14:24 <mattdm> and anyway. lookit the time. we lost this meeting by a good 14 minutes :)
18:14:43 <decause_OSCON> nod nod
18:14:46 <mattdm> thanks for joining everyone!
18:15:14 <mattdm> #endmeeting