18:00:43 <mattdm> #startmeeting Council (2016-12-05)
18:00:43 <zodbot> Meeting started Mon Dec  5 18:00:43 2016 UTC.  The chair is mattdm. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:43 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:43 <zodbot> The meeting name has been set to 'council_(2016-12-05)'
18:00:45 <mattdm> #meetingname council
18:00:45 <zodbot> The meeting name has been set to 'council'
18:00:47 <mattdm> #chair mattdm jkurik jwb cwickert langdon robyduck tatica bexelbie
18:00:47 <zodbot> Current chairs: bexelbie cwickert jkurik jwb langdon mattdm robyduck tatica
18:00:49 <mattdm> #topic Introductions, Welcomes
18:00:51 <zodbot> mattdm: Error: Can't start another meeting, one is in progress.
18:00:53 <mattdm> #meetingname council
18:00:53 <zodbot> The meeting name has been set to 'council'
18:00:55 <mattdm> #chair mattdm jkurik jwb cwickert langdon robyduck tatica bexelbie
18:00:55 <zodbot> Current chairs: bexelbie cwickert jkurik jwb langdon mattdm robyduck tatica
18:00:57 <mattdm> #topic Introductions, Welcomes
18:01:05 <bexelbie> .hello bex
18:01:06 <zodbot> bexelbie: bex 'Brian (bex) Exelbierd' <bex@pobox.com>
18:01:07 <langdon> .hello langdon
18:01:07 <jkurik> .hello jkurik
18:01:08 <mattdm> whoops sorry for double-paste :)
18:01:09 <zodbot> langdon: langdon 'Langdon White' <langdon@fishjump.com>
18:01:12 <zodbot> jkurik: jkurik 'Jan Kurik' <jkurik@redhat.com>
18:01:19 <mattdm> .hello mattdm
18:01:20 <zodbot> mattdm: mattdm 'Matthew Miller' <mattdm@mattdm.org>
18:01:22 <mattdm> jwb sends regrets
18:01:38 <robyduck> .hello robyduck
18:01:39 <zodbot> robyduck: robyduck 'Robert Mayr' <robyduck@gmail.com>
18:01:54 <mattdm> I think we have everyone who is expected...
18:01:56 <mattdm> that was quick!
18:02:01 <mattdm> #topic Today's Agenda
18:02:06 <mattdm> this was going to be PRD review...
18:02:12 <jkurik> :)
18:02:12 <mattdm> but we don't have updated PRDs to review
18:02:21 <mattdm> as I noted, this partly my fault...
18:02:30 <mattdm> as I had promised to send an inspirational message to the WGs
18:02:32 <mattdm> but did not.
18:02:41 <mattdm> I promise to do that soon. Maybe this week :)
18:02:59 <mattdm> In the meantime, let's do some "crank through tickets" work
18:03:19 <mattdm> 1. Election dates -- fix 'em?
18:03:24 <mattdm> 2. Reimbursement issues
18:03:32 <mattdm> 3. YouTube Brazil channel
18:03:40 <mattdm> 4. SoP for Budget?
18:04:00 <mattdm> wait, hold on -- that one was "hey bexelbie do you still want this ticket open?"
18:04:06 <mattdm> /pagure.io/Fedora-Council/tickets/issue/65
18:04:19 <mattdm> https://pagure.io/Fedora-Council/tickets/issue/65
18:04:36 <mattdm> so I'll pause here to see what bexelbie thinks :)
18:04:58 <bexelbie> While there are many great reasons to close it, I believe it still needs to be open
18:05:04 <bexelbie> I could even update it with progress
18:05:08 <bexelbie> but that might be saying too much ;)
18:05:17 <mattdm> thanks :)
18:05:25 <mattdm> 5. Have a training period for new first time Council members
18:05:33 <mattdm> anything else we want to be sure to get to?
18:06:06 <mattdm> okay then :)
18:06:17 <mattdm> #topic Fix election dates?
18:06:23 <mattdm> https://pagure.io/Fedora-Council/tickets/issue/78
18:06:56 <mattdm> There was some discussion in the ticket... do we want to decide this here?
18:07:09 <bexelbie> can we add more discussion?
18:07:11 <bexelbie> here or there?
18:07:16 <mattdm> bexelbie: yes :)
18:07:31 <mattdm> rule of thumb: here if we think it's gonna be 10 minutes or less
18:07:43 <mattdm> if we think it needs more discussion than that, kick it back to the ticket
18:07:45 <bexelbie> If we want to drive additional voting, fixing the voting time at a non-busy time (hah!) of the year would be best
18:07:50 <bexelbie> then we could build up to it, ec.
18:07:52 <bexelbie> I think
18:08:00 <bexelbie> that is kind of in support of your last comment mattdm
18:08:49 <mattdm> I guess I am, like, +0.75 to this for the council and other groups, and +0.25 for FESCo
18:08:53 <langdon> are holidays really a busy time of year for contributors? like aren't many people likely to have a bit more "non-work" free time to read things like campaign blog posts during holidays? (i think i do)
18:08:55 <jkurik> I still have the same opinion as I stated in my comment. Unless we do something with the current way we release Fedora (like the mattdm's proposal sent today) it makes no sense to have fixed dates for Elections.
18:08:56 * robyduck will add a comment there. Maybe we can go with lazy consensus with it? As also jwb is not here?
18:09:38 <mattdm> robyduck: yeah good plan
18:09:54 <bexelbie> I suspect the slow down in contribution is not tied to an uptick in blog reading - I think people are big-time afk
18:10:07 <mattdm> bexelbie: lol
18:10:17 <bexelbie> jkurik, I am not understanding why you feel like term of service and election date must be tied to the release structure?
18:10:21 <mattdm> I think he meant blog-reading as an activity in support of the election
18:10:44 <bexelbie> mattdm, I understood that - I am saying that during hte holidays I suspect readership goes down as well
18:11:08 <bexelbie> Aunt Katka doesn't want the kids on their laptops and all that
18:11:32 <langdon> bexelbie, thats why i read on my phone ... as an escape.. ;)
18:11:33 <jkurik> bexelbie: it makes sense at least for FESCo. It is a team put together to drive technical issue for one/two release cycles.
18:11:54 <bexelbie> jkurik, agreed that their term of service should be tied to the releases.  Why does their election need to be?
18:11:57 <mattdm> that's why I am only +0.25 for it for FESCo :)
18:12:05 <bexelbie> as long as we know who is coming in by the time we finish the release tha tpeople exit on
18:12:24 <mattdm> bexelbie: that's actually an interesting idea....
18:12:28 <bexelbie> i.e. we could elect the people who start with F26 half-way through F25
18:12:29 <jkurik> because elestions are just after we do a release ?
18:12:52 <langdon> bexelbie, i think in the election separate from service start model you need an event like the inaugaration to kick it off.. and, in fact, lots of ground work is done post election/pre-service in the presidential election as well.. so..i think it would be weird in fedora to have the election not directly lead to start of term
18:12:53 <bexelbie> I am willing to poke the bear and ask "why?" - tradition or necessity?
18:13:14 <bexelbie> langdon, or they could begin working on learning the ropes if they are new people
18:13:18 <bexelbie> by shadowing, etc.
18:13:34 <langdon> bexelbie, *that* is a good argument.. i am not convinced by the others ;)
18:14:38 <bexelbie> and if people are re-elected they can begin pre-planning with continuity
18:14:46 <bexelbie> in mind
18:15:25 <mattdm> bexelbie: what happens with, say, early change proposals affecting the release they were elected for but submitted to the current fesco?
18:15:58 <mattdm> This is what I meant by "thinking bigger than just the release cycle at the FESCo level"
18:16:11 * robyduck reads all the arguments but is still for traditional. It will always be a sort of dive-in for new elected/appointed members
18:16:14 <bexelbie> Do you mean the fact that they don't have a vote on those proposals?
18:16:17 <mattdm> I guess we really need jwboyer for this discussion as FESCo rep on th ecouncil.
18:16:18 <jkurik> bexelbie: I am not getting what will be the benefit of having fixed dates for elections. IMO the current model serves well
18:16:23 <mattdm> bexelbie: yes
18:16:41 <bexelbie> jkurik, I think the benefit is the ability to hopefully drive more turnout and to not have to juggle everything at the last minute like this year
18:16:51 <bexelbie> mattdm, that is what we have now - we haven't lost anything
18:17:08 <bexelbie> mattdm, however we may have a reason for the current group to consult with specific people before making their decision
18:17:19 <bexelbie> consult though, not voting
18:17:25 <mattdm> bexelbie: yeah, this is why I'm +0.25 for including FESCo too :)
18:17:36 * mattdm looks at clock and at 10-minute discussion suggestion
18:17:37 <jkurik> bexelbie: it is part of the release. If a release slips, elections slips as well
18:17:51 <bexelbie> what are the benefits for keeping it the way it works versus this model - why is this bad, other than change?
18:17:53 <mattdm> Why don't we take this back to the ticket?
18:18:13 <langdon> we aren't talking about this election, are we?
18:18:21 <bexelbie> langdon, not too my knowledge
18:18:35 <mattdm> in that case, let's *definitely* take it back to the ticket :)
18:18:35 <jkurik> langdon: no, these elections were just a trigger
18:18:35 <langdon> so i am +1 to mailga
18:18:42 <langdon> or mattdm even.. sorry mailga
18:18:51 <mattdm> lol
18:19:10 * bexelbie is generally +1 to mailga too :)
18:19:15 * langdon grumbles about tab completion
18:19:17 <mattdm> #info some discussion; taking it back to the ticket since this doesn't affect current election
18:19:24 <mattdm> #topic Reimbursement issues
18:19:30 <mattdm> https://pagure.io/Fedora-Council/tickets/issue/76
18:19:32 <mattdm> https://pagure.io/Fedora-Council/tickets/issue/77
18:20:30 <mattdm> bexelbie had a proposal in #76 (consider alternative reimbursement methods)
18:20:42 <mattdm> I'm going to call for lazy consensus on that one
18:21:07 <mattdm> I'm not sure what to do about #77
18:21:30 <bexelbie> re:#77 we need to think this through with a flexible policy
18:21:46 <bexelbie> we have so many things where we prepay expenses and avoid reimbursements that we shouldn't just penalize smaller events unnecesarily
18:22:04 <bexelbie> I'll work with Giannis on it, and put something together for lazy consensus - but not next week
18:22:08 <bexelbie> if that works for folks
18:22:31 <mattdm> bexelbie: sounds good
18:22:34 <langdon> bexelbie, +1
18:22:41 <robyduck> ok for me too
18:22:51 <langdon> well...
18:23:00 <bexelbie> one question
18:23:00 <mattdm> bexelbie: assigned to you
18:23:16 <bexelbie> have we ever had a legal opinion on maintaining lists of people who are/are not eligibile for funding?
18:23:21 <langdon> one quick q... are you going to address both 76 & 77 in one "new policy"? like what will the consensus be on?
18:23:31 <bexelbie> everytime it comes up there is a bunch of noise and no actual outcome
18:23:36 <bexelbie> re 76 a proposal is in there
18:23:43 <bexelbie> 77 is related, but separate, imho
18:24:00 <bexelbie> I could easily see 77 being a one-strike and your out rule
18:24:05 <bexelbie> but if we can't keep track of strikes that doesn't work
18:24:08 <mattdm> I think 76 is straightforward and I don't know what options we possibly have for 77.
18:24:10 <langdon> uhh
18:24:14 <langdon> did i read 77 wrong
18:24:23 <mattdm> bexelbie: sounds reasonable to ask legal@fedoraproject.org
18:24:41 <bexelbie> 77 is about fedora prepaying expenses instead of making people wait to be reimbursed after an event
18:24:43 <bexelbie> like for a plane ticket
18:24:47 <langdon> isn't 77 just about paying for someone else? like the project books the travel?
18:25:03 <langdon> ahh .. and the concern being they don't gather receipts or something?
18:25:09 <bexelbie> yes and tradition (hate that word) is that you can't get the $$ reimbursed until after the event and you've submitted reports
18:25:16 <langdon> cause if you pre-pay.. you will get the receipts...
18:25:16 <bexelbie> receipts aren't a problem in prepay as we did the paying :)
18:25:37 <bexelbie> It is an attempt to use the reimbursement process as a stick
18:26:05 <langdon> i guess I am not seeing the problem.. like i see the problem a contributor has but not why we can't, in some cases, have a rht-corp-card to prepay
18:26:21 <bexelbie> langdon, exactly
18:26:41 <bexelbie> and I bleieve most RH people don't use their CC as cost-transfer rules can make it hard to get it to the right cost center
18:26:58 <bexelbie> and now you've reminded me of a non-fedora reimb I need to process
18:26:59 <bexelbie> ugh
18:27:00 <bexelbie> :)
18:27:03 <robyduck> yup, but this topic is going on since years. It would be fine to get to an acceptable solution though
18:27:20 <robyduck> although it is not so easy
18:27:24 <langdon> bexelbie, ohh... no.. i meant a magic corp card .. like one that is owned by the company.. not a person.. that is specifically used for these kinds of expenses
18:27:34 <bexelbie> I think our current process disadvantages lower GDP countries and some lower-SES contributors
18:27:54 <bexelbie> langdon, yes that card is still subject to Cost center transfer rules
18:27:59 <bexelbie> unless you mean an events card
18:28:13 * langdon forgets that rht has some really heinous corp infra
18:28:21 <bexelbie> and the regional card holders have both limited budgets and no process to help them decide what can be prepayed
18:28:24 <bexelbie> a policy could fix that
18:28:38 <bexelbie> I also am trying to be more active with my RHT CC to unblock where needed
18:28:39 <langdon> bexelbie, i meant more like an events card
18:28:52 <langdon> but.. let's table it
18:28:57 * mattdm looks significantly at meeting clock
18:29:03 <mattdm> exactly :)
18:29:04 <bexelbie> which reminds me, in open floor, I want my title changed to FCAIC-ERF
18:29:17 <langdon> i just wanted to know if i should look in 76 to resolve both or if they would be independent
18:29:25 <bexelbie> langdon, independent :)
18:29:28 <bexelbie> imho
18:29:33 <mattdm> #info will make lazy-consensus decision on 76; 77 needs discussion and a proposal
18:29:35 <langdon> bexelbie, works for me
18:29:38 <mattdm> agree, independent
18:29:51 <mattdm> moving on!
18:29:57 <mattdm> #topic YouTube Brazil channel
18:30:05 <mattdm> https://pagure.io/Fedora-Council/tickets/issue/75
18:30:27 <mattdm> does anyone have any objection to this?
18:30:45 <bexelbie> I believe we need to centralize our branding and have regional portals that point inward
18:30:59 <bexelbie> I think splitting off content is hurting us globally as we have little content in some channels
18:31:08 <bexelbie> but I am honestly only about -.25 to -.5 on this
18:31:20 <bexelbie> I'd really like to hear marketing weigh in on this
18:31:42 * robyduck is not that happy with youtube, aren't there any other channels or ways we can do that better?
18:31:53 <mattdm> bexelbie: that's a good point. I'll take it to marketing.
18:32:01 <robyduck> bexelbie: +1 marketing is a good proposal
18:32:15 <mattdm> robyduck: you mean like a free software platform like mediagoblin?
18:32:34 <jkurik> I would prefer the way langdon has proposed: https://pagure.io/Fedora-Council/tickets/issue/75#comment-42022
18:32:44 <bexelbie> I believe that is also a good marketing question - where can we go for impact that is foss-y and what do we get if we go elsewhere?
18:33:13 * mattdm notes that they clearly *already* have a channel
18:33:33 <bexelbie> that means marketing needs to make it compelling for them to join the strategy, imho
18:33:41 <robyduck> mattdm: no, not necessily. But maybe something which can be better "controlled" like a dynamic channel?
18:33:44 <bexelbie> assuming we have that as our strategy
18:33:55 <mattdm> it's also important to note that the content is in Brazilian Portuguese
18:34:26 <robyduck> necessarily even
18:34:50 <bexelbie> a centralized posting location with language sub-parts allows for greater visibility to hopefully spread ideas across regions
18:35:04 <bexelbie> as the content will be understood centrally and shared as concept - even if not in viewership
18:35:11 * bexelbie hopes that wasn't to confusing in text
18:35:19 * bexelbie wants regions to talk to each other and share ideas!
18:35:23 <mattdm> bexelbie++
18:35:28 <zodbot> mattdm: Karma for bex changed to 3 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
18:36:04 <mattdm> I agree with that, although I don't want it to become "you can't do anything because we want to set up a grand global solution" and then that never happens
18:36:12 <mattdm> perfect as enemy of good and all that
18:36:28 <bexelbie> mattdm +1 - we need marketing to weigh in with a strategy soon, not a grand design :)
18:36:29 <langdon> but.. in this case.. we have a solution
18:36:40 <mattdm> #action mattdm to take fedora brasil youtube channel to Fedora Marketing for comment
18:36:52 <mattdm> langdon: which is?
18:37:20 <langdon> fedora youtube channel with playlists
18:37:43 <bexelbie> why not ask marketing to weigh in with a proviso that we approve the playlist if no response in X period of time?
18:37:52 <langdon> but i would take it to fed mktg to make sure they want to do that.. which might be what you are getting at?
18:37:56 <bexelbie> I think we need the questions put to marketing regardless
18:38:03 <bexelbie> langdon, yep :)
18:38:04 <langdon> i know for modularity they recommended a separate channel
18:38:06 * mattdm notes that googling for "fedora youtube" does not give helpful results
18:38:35 <bexelbie> it'd be interesting to hear why they did that with modularity - I presume it is in their plan :)
18:38:40 <langdon> mattdm, do it a few times.. google will learn.. but.. it still wont work for anyone else :)
18:38:57 <mattdm> langdon: it's all.... hat comedy
18:39:10 <langdon> bexelbie, well.. we have a lot of "not broadly interesting" content.. i think we should revisit with some of our overview stuff
18:39:20 <bexelbie> langdon, playlist it :)
18:39:24 <langdon> but sprint demos in the fedora channel might be meh
18:39:26 <mattdm> anyway. next step here is clear. next topic?
18:40:07 <bexelbie> yes
18:40:08 <langdon> yep
18:40:10 <mattdm> #topic Create standard operating procedure for how treasurers interact
18:40:21 <mattdm> bexelbie added a comment in the ticket
18:40:23 <mattdm> actually...
18:40:26 <mattdm> #info bexelbie added a comment in the ticket
18:40:28 <mattdm> done!
18:40:30 <mattdm> :)
18:40:31 <bexelbie> I've updated the ticket - basically I am working to get the data to be collected
18:40:36 <bexelbie> so the reporting becomes more automatic
18:40:43 <bexelbie> we need to be talking about what we did not the $$
18:40:45 <bexelbie> imho
18:40:52 <bexelbie> beyond fiscal management, of course
18:41:01 <mattdm> #info "This would allow the reporting problems to be somewhat alleviated and allow the focus to stop being on $$ and become on impact and activity reporting."
18:41:04 <mattdm> bexelbie++
18:41:14 <bexelbie> For example, it is hard to find out what we spent on an event - it is even harder to find out we were going their in the first place :)
18:41:16 <mattdm> i know i just gave you a cookie but have another virtual one
18:41:34 <bexelbie> my goal is to eliminate the first problem and focus on the second
18:41:40 * bexelbie is done repeating mattdm repeating me now :)
18:41:45 <mattdm> lol
18:42:00 <mattdm> #topic Have a training period for new first time Council members
18:42:05 <mattdm> https://pagure.io/Fedora-Council/tickets/issue/79
18:42:30 <langdon> weren't there comments on this ticket?
18:42:39 <mattdm> langdon: there are not now
18:42:47 <langdon> i see that :)
18:42:50 * bexelbie hasn't commented yet
18:43:05 <mattdm> i do remember seeing comments about this somewhere
18:43:09 <langdon> email
18:43:18 <langdon> i thought it was ticket traffic
18:43:23 <mattdm> hmmmm
18:43:48 * langdon digs
18:43:50 <bexelbie> I don't recall any langdon but I am behind on email, as usual
18:43:55 <mattdm> My comment, I think, is that we're not really expecting brand-new users to join the council
18:44:09 <mattdm> it should generally be people with some serious experience in the project to begin with
18:44:15 <nb> As for ticket 77, in NA, we sometimes prepay expenses, especially stuff like airline tickets
18:44:31 <mattdm> nb - can you put that in that ticket? :)
18:44:33 <nb> generally, it's only for people we know and trust will actually follow through with going to the event
18:44:43 <bexelbie> there is now a comment in 79
18:44:47 <langdon> ahh.. there was an email thread.. and a ticket
18:44:51 <langdon> two different things
18:44:57 <mattdm> bexelbie: shiny :)
18:45:18 <mattdm> okay, so, I guess this one is "discuss in ticket" :)
18:45:23 <mattdm> #info discuss in ticket
18:45:34 * langdon trying to get the link to the email thread
18:45:39 <mattdm> anyone *disagree* with what I said above?
18:46:09 <nb> mattdm, yes, i will put that in the ticket
18:46:10 <bexelbie> mattdm, agreed 100%
18:46:17 <jkurik> mattdm: I agree :)
18:46:22 <bexelbie> I think this is something commops can work on to help figure out how to take contributors to the next level
18:46:25 <robyduck> I think the two comments from mattdm and bexelbie are perfect. It is not really possible, and people know that, to make a training period for something which will come up in the future. We certainly need people who know the Project very good and have experience
18:46:26 <bexelbie> and that isn't - run for council
18:46:53 <mattdm> okay. does anyone object to me closing this as declined after that comment?
18:47:08 * robyduck also thinks the wiki page is quite good. He also read it many times before nominating himself
18:47:16 <langdon> i added the mail thread to the ticket too
18:47:25 <bexelbie> refreshing
18:47:44 <mattdm> robyduck: thanks :) The number of hours I spent per word on that page is pretty high :)
18:47:50 <mattdm> langdon++
18:47:50 <zodbot> mattdm: Karma for langdon changed to 2 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
18:47:51 <jkurik> mattdm: +1 to close
18:47:52 <robyduck> mattdm++
18:47:53 <zodbot> robyduck: Karma for mattdm changed to 6 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
18:47:56 <bexelbie> mattdm, will you put the comment in the ticket - then +1
18:48:00 <langdon> +1 from me too
18:48:07 <mattdm> bexelbie: yep, will write it as soon as done here.
18:48:27 <mattdm> #info we're going to close this as declined with comments in the ticket
18:48:33 <mattdm> #topic open floor
18:48:39 <mattdm> look time to spare :)
18:48:48 <langdon> now.. all that said.. more blog posts by council members on what they are doing.. why on the council.. etc.. would be a good thing
18:49:13 <langdon> which was more the subject of the mail thread than the ticket
18:49:21 <bexelbie> :)
18:49:29 <mattdm> #info More blog posts from council members would be good
18:49:39 <mattdm> I'm thinking about getting back into Fedora This Week writing
18:49:44 <mattdm> note not "five things in fedora"
18:49:49 <mattdm> that was too many things :)
18:49:50 * langdon provides overly specific action items in meetings
18:50:12 <mattdm> anything else?
18:50:19 <langdon> yes.. typing
18:50:26 * mattdm waits
18:50:30 <langdon> how about we add a monthly (two monthly? ) "Notes from the council" or something blog post
18:51:03 * langdon notes bi-monthly means both twice-a-month and every-two-months.. cause english is awesome
18:51:07 <robyduck> langdon: good one, maybe pushing it to zanata for translating too? Just for local contributors and better undertanding?
18:51:22 <bexelbie> langdon, I use that to change requirements as needed - leave it alone :)
18:51:28 <langdon> bexelbie, lol
18:51:46 <langdon> literally... lol.. people are looking at me funny in my cube
18:51:50 <bexelbie> I think we could go with a goals/follow-up style article
18:52:02 <langdon> i think matt should lead it ;)
18:52:11 * langdon beats mattdm to the punch
18:52:18 <langdon> actually.. commops should lead it!
18:52:37 <mattdm> lol.
18:52:39 <bexelbie> well, I will say writing my goals article provided some clarity for me
18:52:51 <bexelbie> and a council goals article once a quarter (see what I did there ...) could be useful
18:52:56 <mattdm> langdon: I think that'd be a good thing for me to do.
18:53:17 <langdon> well.. it is comms.. i think mattdm should set its direction.. comms should enforce it ;)
18:53:33 <mattdm> langdon: commops should harrass me into writing it? :)
18:53:35 <bexelbie> I need to send my Objectives and Conferences email
18:53:37 <langdon> might also help your "2 release a year" marketing problem
18:53:39 <bexelbie> to the council
18:53:56 <mattdm> langdon: what, by making it six (or is it twenty four)?
18:53:59 * bexelbie is expecting something on par with Warren Buffet's letter!
18:54:19 <langdon> ha
18:54:43 <langdon> mattdm, regular, ongoing updates are often appreciated by journos..
18:54:52 <langdon> i dont know.. im just talking crazy
18:55:21 <mattdm> it's a good idea.
18:55:38 <mattdm> i'm going to end the meeting now though because I'm getting no-food-brain-feeling
18:55:50 <langdon> ha
18:56:00 <bexelbie> +1 to no brain in mattdm ... oh wait
18:56:02 <langdon> you can start writing the council notes update while you eat!
18:56:03 <bexelbie> :P
18:56:07 <mattdm> thanks everyone
18:56:11 <mattdm> #endmeeting