21:07:36 <decause> #startmeeting
21:07:36 <zodbot> Meeting started Tue Mar 24 21:07:36 2015 UTC.  The chair is decause. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:07:36 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
21:07:38 <FranciscoD> ah, here he is :)
21:07:41 <randomuser> decause++
21:07:46 <decause> #topic rollcall
21:07:53 <decause> .hello decause
21:07:55 <zodbot> decause: decause 'None' <remyd@civx.us>
21:08:00 <FranciscoD> .hello ankursinha
21:08:02 <zodbot> FranciscoD: ankursinha 'Ankur Sinha' <sanjay.ankur@gmail.com>
21:08:03 <sesivany> .fas eischmann
21:08:04 <zodbot> sesivany: eischmann 'Jiri Eischmann' <eischmann@redhat.com>
21:08:20 <Pintomatic> .fas Pintomatic
21:08:21 <zodbot> Pintomatic: pintomatic 'cesar pinto' <cesar.a.pinto@gmail.com>
21:08:24 <randomuser> .hello immanetize
21:08:25 <zodbot> randomuser: immanetize 'Pete Travis' <me@petetravis.com>
21:08:33 <giannisk> .fas giannisk
21:08:34 <zodbot> giannisk: giannisk 'Giannis Konstantinidis' <giannis@konstantinidis.cc>
21:08:48 <mitzie> .fas mitzie
21:08:50 <zodbot> mitzie: mitzie 'Zacharias Mitzelos' <mitzie@mitzelos.com>
21:08:58 <decause> .fas decause
21:09:01 <zodbot> decause: decause '' <remyd@civx.us>
21:09:24 <randomuser> *almost* the same
21:09:25 <decause> that everyone?
21:09:30 <decause> going once
21:09:32 <decause> going twice
21:09:33 * FranciscoD looks around for mailga
21:09:41 <decause> going thrice
21:09:51 <decause> #topic agenda
21:10:02 <decause> Pintomatic: link to agenda plz, or I can dig it up
21:10:25 <Pintomatic> http://etherpad.osuosl.org/fosco-032415
21:10:55 <decause> 1) What is Outreach? Define higher level goals for program
21:10:57 <Pintomatic> What is Outreach? Define higher level goals for program
21:10:57 <Pintomatic> Brainstorming: What are the top 10 priorities we should focus on.
21:10:57 <Pintomatic> Action + Timeline: What 3 things will we focus on and by when
21:11:06 <decause> like he said ^
21:11:28 <decause> #link http://etherpad.osuosl.org/fosco-032415
21:11:47 <decause> #topic What is Outreach?
21:11:59 <randomuser> so, I have a somewhat overreaching concern here
21:12:10 <decause> randomuser: shoot :)
21:12:40 <randomuser> FranciscoD and I were discussing this earlier, and it turned me to thinking about the distinction between strategy and tactics
21:13:23 <decause> randomuser: nod nod nod
21:13:32 <randomuser> the problem I thought we were addressing with this group - and I have vague recollections of others stating something like this - is that the project lacks a cohesive overall strategy
21:14:01 <decause> randomuser: and unifide messaging, and common communication channel across internal teams, yes
21:14:15 <randomuser> and with all of the discussions recently on FOSCO, I haven't seen any mention of *strategy* - it's all implementation details, ie complaints
21:14:17 <decause> s/unifide/unified/
21:14:41 <randomuser> the teams we have are relatively effective in their own space; I don't think this is the best use of energy
21:15:06 <decause> randomuser: valid
21:15:40 <randomuser> if there is not a vision for a broad strategy, and no will to create one, then FOSCO does not have merit
21:15:46 <randomuser> EOF
21:16:05 <decause> one of the first tasks/tickets in trac is to create a mission statement
21:16:30 <decause> this is going to require a process of input, and take some time to do
21:16:38 <randomuser> right...
21:16:39 <FranciscoD> !
21:16:44 <decause> normally, this would be ok-ish
21:16:54 <decause> except that FAMSco is in a holding pattern, waiting on FOSCo
21:16:59 <decause> is this a fair statement?
21:17:14 <FranciscoD> Do we have a general problem statement that fosco is supposed to address?
21:17:31 <Pintomatic> If I may?
21:17:34 <decause> FranciscoD: not yet, and we should absoltely create one
21:17:42 <FranciscoD> ah, hrm
21:17:44 <decause> FranciscoD: I heard there was much discussion today in #fedora-join about this
21:17:55 <decause> I joined eventually, but not until after
21:18:01 <Pintomatic> The concerns seem to be around FOSCO being a governance body right?
21:18:07 <FranciscoD> Yeah. We were trying to figure out fosco's purpose
21:18:08 <randomuser> this is back to what I said on the list;  we have a solution looking for problems
21:18:11 <randomuser> decause, I'll send you a log
21:18:15 <decause> randomuser: thanks
21:18:17 <Pintomatic> Because FAMSCO was and its suddenly no more
21:18:25 <FranciscoD> Pintomatic: not exactly - like randomuser says, we have a new body, but it has  no purpose
21:18:32 <FranciscoD> (for the time being)
21:18:47 <Pintomatic> FOSCO has no purpose?
21:18:52 <FranciscoD> so the retructuring and things aren't warranted at the moment
21:19:03 <decause> it has no *clear* purpose, I would say, yet
21:19:05 <FranciscoD> Pintomatic: we just said above that we don't know the problem we're trying to address
21:19:17 <Pintomatic> I envision FOSCO being a shared services function
21:19:46 <Pintomatic> firstly measuring, I saw some good concrete points around this.
21:20:03 <Pintomatic> Using those measurements to inform the groups.
21:20:39 <Pintomatic> Once solid synergies are identified those should / would be enthusiastically adopted by those groups.
21:20:51 <Pintomatic> The goal being to increase project reach
21:21:02 <Pintomatic> hence "outreach"
21:21:15 <sesivany> The reason why I think FOSCo should be created from my humble FAmSCo perspective is that there have been activities and processes that are in nature cross-team, but developed in the Ambassadors subproject because ambassadors needed them. That's for example budgeting, approving, reimbursing. My opinion is that others should be involved in this as well.
21:21:28 <FranciscoD> outreach as in increasing participation in Fedora - new contributor wise?
21:21:46 <decause> FranciscoD: there is good news for FOSco on the new user front
21:21:47 <decause> !
21:21:57 <Pintomatic> FranciscoD: yep, for instance
21:22:00 <decause> home http://blog.linuxgrrl.com/2015/03/24/enabling-new-contributors-brainstorm-session/
21:22:09 <randomuser> ha! you don't have to call for the talking stick in your own meeting :)
21:22:10 <decause> #link http://blog.linuxgrrl.com/2015/03/24/enabling-new-contributors-brainstorm-session/
21:22:11 <Pintomatic> But also users.
21:22:19 <Pintomatic> and mind share.
21:22:24 <FranciscoD> decause: oh, we talked to mizmo in the channel too - she thought fosco was about outreach as in diversity
21:22:34 <decause> there is a meeting happening tomorrow being led by design team around this Hubs concept for engaging new contributors
21:23:03 <FranciscoD> (similar to the gnome outreach initiatives)
21:24:32 <Pintomatic> I think , if FOSCO is to be successful it has to deliver something of use to all first.
21:24:52 <Pintomatic> In my mind this thing is first measurement.
21:25:11 <Pintomatic> On terms of reach , adoption. We can´t improve what we can´t measure.
21:25:31 <Pintomatic> Idea: FOSCO quarterly dashboard.
21:25:53 <Pintomatic> Include all measurements there and share with all groups. Serve as a barometer first.
21:26:03 <FranciscoD> Pardon me, what metrics are we measuring?
21:26:18 <Pintomatic> Er.. of the top of my head.
21:26:29 <Pintomatic> New contributors
21:26:31 <Pintomatic> Social media
21:26:40 <Pintomatic> Google analytics
21:27:18 <randomuser> so, these would be typically used by marketing to create trend data, demographics reports, etc
21:27:36 <randomuser> they can be used to measure the success of a campaign, but they are a tool
21:27:37 <Pintomatic> Indeed.
21:27:51 <randomuser> a group at this level uses tools to build something
21:28:02 <randomuser> if we want marketing tools, we would ask marketing
21:28:09 <decause> Pintomatic: analytics of some kind, yes
21:28:27 <Pintomatic> randomuser: Exactly. Like an executive dashboard.
21:28:47 <Pintomatic> So we can have more informed discussions.
21:28:58 <randomuser> Pintomatic, it sounds like you might be interested in joining the Marketing team :)
21:29:38 <Pintomatic> randomuser: well, yes and no. maybe I am missing the point in FOSCO then.
21:30:02 <Pintomatic> marketing data with no impact on ambassador activity is quite sterile.
21:30:21 <Pintomatic> my involvement started when asking for "metrics for success"
21:30:54 <Pintomatic> Which currently, we have some but those are not exactly what I am thinking about.
21:31:22 <FranciscoD> So, marketing collects data -> fosco uses this data to $do_something -> teams carry out the plan?
21:31:24 <Pintomatic> We can hopefully inform and influence other groups on what events to attend to maximise reach
21:31:44 <Pintomatic> FranciscoD: Yes!
21:32:03 <decause> ok, timecheck, we are halfway through
21:32:13 <decause> perhaps we should move onto the next item
21:32:29 <FranciscoD> So fosco will co-ordinate the teams according to a plan that it will come up with and so on. That clarifies a bit, thank you.
21:32:59 <FranciscoD> Could someone please update the fosco wiki page with this general purpose so that everyone looking for fosco is on the same page?
21:33:04 <Pintomatic> Yes. In theory. We should try to keep effort simple - simple
21:33:22 <FranciscoD> http://fedoraproject.org/wiki/FOSCo exists but is blank :)
21:33:44 <Pintomatic> Blank canvas :-)
21:34:07 <randomuser> decause, do you see anything actionable from the discussion so far?
21:34:09 <Pintomatic> Do we have agreement on this general purpose
21:34:30 <Pintomatic> I think we are not quite ready to move on
21:34:46 <Pintomatic> (hence my suggestion of video call... sigh)
21:34:49 <decause> anyone want to take on the update the wiki action?
21:35:20 <Pintomatic> I could try but I might break the page ...
21:35:38 <FranciscoD> Pintomatic: you seem to have the clearest idea, please do it :)
21:35:39 <randomuser> I'm open to taking action, but do not have any confidence that I can write something that would represent anyone else's perspective
21:35:54 <FranciscoD> it's awfully difficult to break the wiki ;)
21:36:16 <Pintomatic> randomuser: what is your concern?
21:36:51 <Pintomatic> Do you understand the suggested objective of FOSCO at this stage?
21:36:59 <randomuser> Pintomatic, there's been an ongoing discussion here about our concerns
21:37:17 <randomuser> I understand better now what your perspective is
21:37:23 <Pintomatic> right. that´s what I said earlier.
21:37:45 <Pintomatic> FAMSCO and FOSCO are not the same thing.
21:37:54 <randomuser> Understanding your personal perspective is not the same as reaching consensus on the mission statement of a top level leadership body
21:38:13 <Pintomatic> And here is the issue , thank you.
21:38:53 <Pintomatic> My 2 cents: if FOSCO aspires to be a top level leadership body it will likely fail on its purpose
21:39:18 <Pintomatic> FOSCO should aspire to
21:39:31 <Pintomatic> SERVE: by means of providing useful insight.
21:39:39 <Pintomatic> Timely , relevant.
21:40:07 <Pintomatic> INFORM: all units , on trends which might help us get closer to our objective.
21:40:29 <Pintomatic> and uncover opportunities , you know?
21:40:59 <randomuser> this is a transparent community; everyone already has the opportunity to offer insight, and they often do
21:41:14 <randomuser> the inform points are marketing responsibilities
21:41:33 <FranciscoD> (which we haven't been doing too well, I'll admit, but that's a different story)
21:41:37 <Pintomatic> Right. But if everything is working perfectly. Why do anything?
21:42:10 <Pintomatic> I could be controversial and point to various half empty pages.
21:42:10 <decause> timecheck: we are approaching 3/4 of the way through this meeting, in case we wanted to approach any other items on the agenda
21:42:27 <Pintomatic> on topics such as basic high level measurement of all things.
21:43:05 <randomuser> we've all seen the wiki :P
21:43:05 <Pintomatic> I think this item is the most important one, if there is no consensus that is a useful outcome on itself.
21:43:14 <decause> Pintomatic: I believe fedmsg/datanommer/datagrepper will be *crucial* sources for these types of proposed metrics
21:43:26 <sesivany> I'm looking at it from FAmSCo pespective, that FOSCo should replace FAmSCo, but I still fail to see it in the proposed mission statement. In my opinion, FOSCo should be a platform for communication (we know from famsco experience that it's beneficial that people from different teams/regions get together), second it should be a body that oversees subprojects, makes sure they work well, have all they need etc.
21:43:30 <Pintomatic> because randomuser raises the view of the many.
21:44:31 <FranciscoD> Pintomatic: that's because we haven't done any actual measurement in the past, at least not that I'm aware of
21:44:42 <decause> So, I think there are competing priorities here: The priority to keep FAMSCo activity ongoing, and the priority to spend a reasonable amount of time figuring out what FOSCo is/does/wantstodo/andhow
21:44:53 * randomuser nods
21:45:15 <randomuser> sesivany, what immediate functions do the ambassadors need from a group like fosco or famsco?
21:45:23 <decause> WHat I would like to propose in the meantime, is that FOSCo meet regularly, and handle the types of "usual" business that FAMSCO does at the beginning of the meeting
21:45:40 * FranciscoD nods
21:45:57 <decause> with the understanding tha tFOSCO will do "more" in the future, and "more" has much defining to be done
21:46:11 <decause> that hopefully will happen on the wiki
21:46:13 <decause> and trac
21:46:17 <decause> and etherpad
21:46:35 <Pintomatic> Anyone here represents marketing?
21:46:43 <FranciscoD> I'm active in mktg, yes
21:46:51 <sesivany> randomuser: communication with OSAS (Red Hat) regarding financials, solving escalated issues/conflicts.
21:46:58 <randomuser> jzb might be lurking around too
21:47:09 * decause was in the same room as jzb just a moment ago
21:47:11 <Pintomatic> Cool, could we work together on this idea of measurements?
21:47:16 <decause> he's busy on Atomic-y things today
21:47:19 <FranciscoD> sesivany: wasn't issues passed on to cwg sometime back?
21:47:19 <randomuser> ack
21:47:21 <Pintomatic> FransciscoD
21:47:42 <FranciscoD> Pintomatic: sure
21:48:12 <Pintomatic> Cool, lets aim to have something to show in 2 weeks.
21:48:37 <sesivany> FranciscoD: some of them, but then someone needs to create and maintain rules such as the infamous inactive ambassadors removal discussion.
21:48:42 <decause> so, an action of creating a metrcs proposal sounds like it is on the table?
21:48:45 <Pintomatic> A simple dashboard. which we can update monthly or something.
21:49:03 <Pintomatic> If this is marketing and no FOSCO, thats fine also.
21:49:20 <decause> this concept is most of the way there: http://thisweekinfedora.org/
21:49:40 <FranciscoD> sesivany: aye, but limited to the ambassadors group - logistics, planning, budgeting and so on, right.
21:49:58 <randomuser> Pintomatic, how about this idea:  work with marketing to develop the *type* of metrics you think would be useful, and ask infra to set up the reports
21:49:59 <decause> Is there a "list of FAMSCo Duties" somewhere?
21:50:22 <FranciscoD> Infra will do the implementing, yes
21:50:27 <Pintomatic> Beautiful, lets pick up on this.
21:50:28 <randomuser> Pintomatic, all that information is readily available, you just need to know what you are looking for and how to get it
21:50:34 <sesivany> decause: http://fedoraproject.org/wiki/Fedora_Ambassadors_Steering_Committee
21:50:39 <decause> sesivany++
21:51:05 <decause> this information needs to make it into the FOSCo materials
21:51:07 <Pintomatic> randomuser: I agree on this action, I can commit to that.
21:51:14 <randomuser> sesivany, what's the famsco status now? fully retired, limbo, active until replacement is functional?
21:51:17 <decause> sesivany: how does FAMSco decide what business it handles usually?
21:51:30 <randomuser> Pintomatic, if you haven't yet, I suggest you introduce yourself and your plans to the marketing list
21:51:55 <Pintomatic> randomuser: Shall do.
21:52:14 <sesivany> randomuser: we're still somehow functional, but all of us have been serving in FAmSCo for quite a long time (me almost three years) and we're are a bit burnt out.
21:52:14 <decause> #action Pintomatic introduce yourself and fosco resources to fedora-mktg maillist
21:52:24 <randomuser> decause, may as well change the topic now :P
21:52:36 <decause> #topic Next Meeting
21:52:44 <decause> what things do we want to cover next time?
21:52:59 <decause> 2) Top 10 Priorities
21:53:02 <randomuser> it sounds like the ambassador handoff needs work
21:53:21 <randomuser> sorry for steering the conversation so far adrift from that, ambassador activity is foreign to me
21:54:15 <randomuser> sesivany, is the process of cycling out inactive ambassadors something that needs to be addressed?
21:54:20 <Pintomatic> I suggest: we should review the progress on this dashboard idea.
21:54:24 <sesivany> randomuser: not that the only solution would be FOSCo, we have had such a situation several times in the past and new blood solved it, but when Matthew came up with FOSCo idea we agreed it could be a good opportunity for a fresh start.
21:54:38 <decause> randomuser: I don't know if moving FAMSCo meeting time to FOSCo meeting time is the best way to keep continuity
21:55:30 <randomuser> it seems clear to me that there needs to be a more firmly defined fosco before fosco can actually start taking on famsco responsibilities
21:55:31 <sesivany> randomuser: it has been solved, actions are carried out, just the consensus was a bit cumbersome solution, so it takes time to fully process it.
21:55:35 <decause> I think we need to find out if FAMSCo members (active) are available for this Tues 5pm EST slot
21:55:52 <FranciscoD> randomuser++
21:56:13 <decause> randomuser: that sounds right to me
21:56:17 <randomuser> like, there should be work on a charter
21:56:20 <decause> I don't want to speak for the FAMSCo though
21:57:15 <Pintomatic> Very unsure about what is there to gain from taking on this task
21:57:16 <decause> I will continue being available during FAMSCo time slots, to help bridge the gap
21:57:17 <sesivany> FAmSCo is able to do its job until FOSCo is ready, no problem there.
21:57:28 <randomuser> I don't feel comfortable with my opinion on things having voting weight just because I showed up, tbh
21:57:29 <Pintomatic> The ambassador removal bit
21:57:35 <Pintomatic> Seems like a poison chalice
21:57:49 <FranciscoD> Pintomatic: it's not very relevant to fosco here tbh
21:57:58 <FranciscoD> it's something that famsco handled after years of deliberation
21:58:15 <FranciscoD> let's not go back on the progress that has been made there this quick :)
21:58:15 <decause> sesivany: I am sensitive to your burnouts in FAMSco, and would like to get a list of "stuff to take off the FAMSCo plate" to help you folks
21:58:22 <randomuser> ..not that anyone suggested that it does, just pointing out that there should be first a clear goal, then a council approved charter, then membership filled
21:58:25 <sesivany> and even if we dismiss the idea of FOSCo, we will just do a new election and bring in new blood. I don't want it to sound like FOSCo is the only way to save FAmSCo.
21:58:29 <decause> burnout concerns*
21:59:31 <Pintomatic> Is there a reason why this feels a bit rigid and bureaucratic ?
21:59:54 <Pintomatic> We should focus on creating and establishing value first.
22:00:02 <decause> Pintomatic: to your point, yes
22:00:05 <Pintomatic> And then participation and responsibilities
22:00:09 <Pintomatic> will be earned.
22:00:16 <decause> I think Steering Committee implies bureaucracy and process
22:00:29 <FranciscoD> decause: +1
22:00:33 <Pintomatic> Otherwise the people in those current positions will not support anything.
22:00:40 <FranciscoD> which is why we want to be completely sure that a new body is required
22:00:43 <Pintomatic> We want to create something new here.
22:00:51 <FranciscoD> for which, the problem and steps required to solve it need to be clear
22:00:52 <randomuser> There are many, many opportunities for you to dig in and start creating value
22:01:08 <decause> ok, we are one minute over time now
22:01:10 <decause> so
22:01:18 <Pintomatic> But also many interpretations of what this group is meant to be
22:01:29 <sesivany> Pintomatic: sure, but FAmSCo currently makes sure that $100k is well spent throughout the community and that's big responsibility that comes with necessary bureaucracy.
22:01:55 <Pintomatic> Right.
22:01:59 <Pintomatic> Key point here.
22:02:09 <FranciscoD> Pintomatic: that came about because there was no clear purpose for fosco and different people assumed different things :)
22:02:30 <Pintomatic> Should FOSCO decide where to spend $$?
22:02:40 <Pintomatic> Honest question.
22:02:43 <FranciscoD> At the moment, that cannot be answered IMO
22:02:56 <Pintomatic> I don´t think we even need to get there.
22:03:07 <FranciscoD> we dont' know what fosco is to do - so we don't know what needs to be done. It's too early to decide on who should handle the budget.
22:03:20 <Pintomatic> The main thing guys.
22:03:23 <Pintomatic> Barometer.
22:03:33 <sesivany> Pintomatic: not FOSCo itself, but what we do in FAmSCo is that we collect ideas and plans from regions and make a comprehensive plan/budget for Red Hat.
22:03:51 <randomuser> Pintomatic, you're working on the presumption that fosco already exists and that you need only show up and decide what you want to do as part of FOSCo.  There's a large, fully functional community here already.
22:04:20 <Pintomatic> I think I get the flavour of what is happening .
22:04:37 <decause> Pintomatic: I *really* am invested in metrics as part of my role as FCL
22:04:50 <Pintomatic> FCL ?
22:05:08 <decause> Fedora Community Lead (new position, also working on defining that too ;) )
22:05:20 <Pintomatic> randomuser: with respect. I think we can benefit from the debate.
22:05:41 <randomuser> sure, I'm not opposed to debate :)
22:05:42 <decause> debate is healthy, and should continue on the mailling list and trac for now
22:05:44 <Pintomatic> People have different ideas and some of these are not entirely relevant.
22:05:45 <FranciscoD> decause: the way I think of it, the FCL would keep an eye on the different teams and ensure that they communicate and aid each other
22:05:46 <decause> we are 5 minutes over time
22:05:51 <sesivany> Pintomatic: for example my idea of FOSCo is that it should do for broader community for FAmCo does for ambassadors, but I suppose others have different opinions :)
22:05:53 <decause> FranciscoD: absolutely
22:05:56 <Pintomatic> might not be entirely relevant.
22:06:08 <FranciscoD> decause: it's sort of what the FPL is doing with the 5 things in fedora posts and so on
22:06:09 <sesivany> s/for/what
22:06:28 <decause> FranciscoD: There is a large laundry list of roles, and those will get prioritized as I get my footing
22:06:33 <FranciscoD> I'm not sure that an entire new body with restructuring is needed to address the current issues that we've brought up
22:06:43 <randomuser> decause, my general idea of the kind of thing fosco could accomplish is summed up in that log; let me know if you think I should clean it up and post some more functional synopsis
22:07:02 <FranciscoD> decause++
22:07:03 <decause> I've been in this position for only a short time now, and am very appreaciative of all your input on how I can help all the subprojects
22:07:41 <decause> we need to end this meeting today for now though
22:07:44 <Pintomatic> decause, you have your work cut out :-)
22:08:03 <decause> Pintomatic: oh yes, but there are many amazing contributors who are already helping me everyday to figure it out :)
22:08:06 <decause> sesivany++
22:08:06 <zodbot> decause: You have already given 1 karma to eischmann
22:08:13 <decause> we had a great talk about ambassadors on Friday
22:08:13 <randomuser> heh
22:08:18 <decause> Pintomatic: has been contributing to etherpad
22:08:21 <decause> we've got some good starts
22:08:24 <decause> it is going to take time
22:08:31 <decause> but that shouldn't mean the ambassadors are in limbo forever
22:08:53 <Pintomatic> Guys, should we have a nice video chat some time?
22:08:54 <decause> I belive we resolved to maintain famsco meeting time, with Decause serving as go between for proto-fosco meeetings
22:09:01 <randomuser> Pintomatic, please, no
22:09:11 <Pintomatic> The problem with these meetings is the typing.
22:09:17 <Pintomatic> Okay okay ... sigh
22:09:24 <Pintomatic> :-)
22:09:26 <decause> Pintomatic: not as FOSCo, but as a "hi nice to meet you" yes, def
22:09:36 <decause> Pintomatic: send me some times you are avialable next week
22:09:39 <randomuser> it's much easier to interrupt while typing :)
22:09:39 <decause> offline
22:09:51 <Pintomatic> right right.
22:09:55 <sesivany> decause: no worries, most of the work is done in regions and those are very well fuctional, there is not much left to do for famsco and we can do it until this is solved ;)
22:09:55 <decause> sesivany: does that sound reasonable?
22:10:03 <decause> sesivany: great
22:10:08 <Pintomatic> I think we made progress.
22:10:16 <decause> keep me posted on ways I can help
22:10:33 <decause> Pintomatic: I think pingou is the one who wrote thisweekinfedora
22:10:35 <Pintomatic> Yes. This timeslot usually works for me , franciscoD i will be in touch :-)
22:10:37 <decause> threebean is also involved
22:10:51 <decause> Pintomatic: I'm excited about metrics, and where ever those fall will be interesting to th ecommunity
22:11:09 <decause> so if you are excite dabou tthat, let's start that conversation in the etherpad, and talk with fedora-infra about fedmsg
22:11:23 <Pintomatic> Absolutely, might be something to fall in somewhere else after all.
22:11:27 <decause> any other action items for today?
22:11:38 <decause> we're wayyyy over time, so I'm going to call it here
22:11:47 <decause> thanks for your time everyone
22:11:49 <Pintomatic> alrighty
22:11:55 <decause> #endmeeting