From 1d476c0a1af95237152023f0e9a4060e7242fa4b Mon Sep 17 00:00:00 2001 From: Brian (bex) Exelbierd Date: Jan 09 2017 12:58:22 +0000 Subject: Reorganize Repo and add initial ledger files Reorganize the repository slightly to allow for historical FY17 files Add new ledger files for common areas and NA. Others are pending validation. --- diff --git a/FY17/Q1/apac/Q1-2017.ods b/FY17/Q1/apac/Q1-2017.ods deleted file mode 100644 index fb7f099..0000000 Binary files a/FY17/Q1/apac/Q1-2017.ods and /dev/null differ diff --git a/FY17/Q1/apac/apacq1report.txt b/FY17/Q1/apac/apacq1report.txt deleted file mode 100644 index 8ff95cf..0000000 --- a/FY17/Q1/apac/apacq1report.txt +++ /dev/null @@ -1 +0,0 @@ -TODO: izhar diff --git a/FY17/Q1/emea/EMEA-Q1-Budget-Report.ods b/FY17/Q1/emea/EMEA-Q1-Budget-Report.ods deleted file mode 100644 index a6064c8..0000000 Binary files a/FY17/Q1/emea/EMEA-Q1-Budget-Report.ods and /dev/null differ diff --git a/FY17/Q1/latam/latamq1report.txt b/FY17/Q1/latam/latamq1report.txt deleted file mode 100644 index 974297b..0000000 --- a/FY17/Q1/latam/latamq1report.txt +++ /dev/null @@ -1 +0,0 @@ -TODO: potty diff --git a/FY17/Q1/na/Fedora_FAmNA_Budget_FY2017.xlsx b/FY17/Q1/na/Fedora_FAmNA_Budget_FY2017.xlsx deleted file mode 100644 index ca134c8..0000000 Binary files a/FY17/Q1/na/Fedora_FAmNA_Budget_FY2017.xlsx and /dev/null differ diff --git a/FY17/Q1/na/naq1report.txt b/FY17/Q1/na/naq1report.txt deleted file mode 100644 index 515f50d..0000000 --- a/FY17/Q1/na/naq1report.txt +++ /dev/null @@ -1 +0,0 @@ -TODO: award3535 diff --git a/FY17/Q1/quarterlyreporttemplate.ods b/FY17/Q1/quarterlyreporttemplate.ods deleted file mode 100644 index 2cbe50f..0000000 Binary files a/FY17/Q1/quarterlyreporttemplate.ods and /dev/null differ diff --git a/FY17/Q2/emea/Fedora EMEA Quarterly Budget Report - Q2 FY17 - Report.pdf b/FY17/Q2/emea/Fedora EMEA Quarterly Budget Report - Q2 FY17 - Report.pdf deleted file mode 100644 index 592ef9f..0000000 Binary files a/FY17/Q2/emea/Fedora EMEA Quarterly Budget Report - Q2 FY17 - Report.pdf and /dev/null differ diff --git a/FY17/Q2/emea/Fedora EMEA Quarterly Budget Report - Q2 FY17.ods b/FY17/Q2/emea/Fedora EMEA Quarterly Budget Report - Q2 FY17.ods deleted file mode 100644 index cdac71d..0000000 Binary files a/FY17/Q2/emea/Fedora EMEA Quarterly Budget Report - Q2 FY17.ods and /dev/null differ diff --git a/FY17/adjustedannualbudgets/council/council.2016-04-11-18.00.log.html b/FY17/adjustedannualbudgets/council/council.2016-04-11-18.00.log.html deleted file mode 100644 index f186c69..0000000 --- a/FY17/adjustedannualbudgets/council/council.2016-04-11-18.00.log.html +++ /dev/null @@ -1,474 +0,0 @@ - - - - -#fedora-meeting log - - - - -
18:00:15 <mattdm> #startmeeting Council (2016-04-11)
-18:00:15 <zodbot> Meeting started Mon Apr 11 18:00:15 2016 UTC.  The chair is mattdm. Information about MeetBot at http://wiki.debian.org/MeetBot.
-18:00:15 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
-18:00:15 <zodbot> The meeting name has been set to 'council_(2016-04-11)'
-18:00:17 <mattdm> #meetingname council
-18:00:17 <zodbot> The meeting name has been set to 'council'
-18:00:19 <mattdm> #chair mattdm jkurik jwb cwickert langdon decause robyduck tatica
-18:00:19 <zodbot> Current chairs: cwickert decause jkurik jwb langdon mattdm robyduck tatica
-18:00:21 <mattdm> #topic Introductions, Welcomes
-18:00:25 <langdon> .hello langdon
-18:00:26 <zodbot> langdon: langdon 'Langdon White' <langdon@fishjump.com>
-18:00:31 <jwb> hi
-18:00:32 <jkurik> .hello jkurik
-18:00:34 <zodbot> jkurik: jkurik 'Jan Kurik' <jkurik@redhat.com>
-18:00:42 <mattdm> .hello mattdm
-18:00:43 <zodbot> mattdm: mattdm 'Matthew Miller' <mattdm@mattdm.org>
-18:00:44 <decause> .hello decause
-18:00:44 <robyduck> .fas robyduck
-18:00:45 <zodbot> decause: decause 'Remy DeCausemaker' <decause@redhat.com>
-18:00:48 <cwickert> .hello cwickert
-18:00:48 <zodbot> robyduck: robyduck 'Robert Mayr' <robyduck@gmail.com>
-18:00:51 <zodbot> cwickert: cwickert 'Christoph Wickert' <christoph.wickert@gmail.com>
-18:01:23 <mattdm> whoo, good crowd today :)
-18:02:23 <mattdm> well, let's get right to it...
-18:02:40 <mattdm> #topic Initial FY17 budget meeting
-18:02:47 * decause drumrolls
-18:03:12 <mattdm> ideally, this wouldn't be "initial" -- the initial meeting really should have been in September
-18:03:18 <mattdm> but we're getting a new process started
-18:03:20 <mattdm> see
-18:03:24 <mattdm> #link https://budget.fedoraproject.org/
-18:03:30 <mattdm> #info new budget process site
-18:03:48 <mattdm> we're currently at the "adjustment/allocation" stage
-18:04:01 <mattdm> having gotten the community budget numbers from our sponsor
-18:04:16 <mattdm> decause, you wanna take this?
-18:04:27 <decause> mattdm: the big number, yeah?
-18:04:31 <mattdm> yeah
-18:04:43 <decause> #topic The Big Number
-18:04:52 <mattdm> #link http://lists.fedoraproject.org/archives/list/council-discuss@lists.fedoraproject.org/message/TML72C4572A6FVK6UJDFCMUN56T4PKJ4/
-18:05:04 <decause> #info The Big Number this year, is the same as last year, at $195,000
-18:05:05 <mattdm> #info email from mattdm summarizing things from this morning
-18:05:34 <decause> the difference this year, is how we discuss and prioritize making that number stretch
-18:06:01 <mattdm> #info That covers events, swag, Fedora conferences, activity days, and any other community spending
-18:06:20 <decause> *everything*
-18:06:24 <mattdm> #info Does not include infrastructure, hardware, etc
-18:06:42 <decause> meant to put one * on that 'everything' ;)
-18:07:23 <decause> we should just take a moment to make sure everyone here has read mattdm's email to the council list today
-18:07:29 * mattdm quiets up and lets decause talk
-18:07:45 <mattdm> (although if anything was unclear, I can help explain)
-18:07:45 <decause> as it condenses all the history into one succinct place
-18:08:22 <decause> I've spent the past few weeks shaking the trees to get our regional information into one place, which mattdm has done a great job of compiling
-18:08:31 <decause> our new budget site
-18:08:40 <decause> #link http://budget.fedoraproject.org
-18:09:10 <decause> is where we'll announce the regional allocations
-18:09:29 <decause> as well as the central budget for Fedora events
-18:10:27 <decause> Regions are still responsible for crunching/reporting their own numbers, but they have additional support now via the Community Blog and CommOps team to help publicize and socialize their events
-18:10:40 <decause> as well as help with gathering some impact metrics for such activity
-18:11:24 <decause> a place where we're gathering all the budget information is the new fedora-budget repository hosted on pagure
-18:11:32 <decause> #link http://pagure.io/fedora-budget
-18:12:23 <decause> by treating the budget process the same way we treat other infrastructure within fedora, and use the same tools to wrangle it, we can make it much easier to distribute the load of reporting
-18:13:08 <decause> right now, there are directories for each fiscal year, and each region, but the data we have from year's past has not been fully committed to the repository
-18:13:40 <decause> which is a "nice-to-have" for historical reasons, but not entirely necessary for today's talks
-18:14:57 <decause> I'm going to be working with the delegates from each region to standardize on a reporting mechanism (spreadsheet) that we use on a quarterly basis to report on action and impact
-18:15:08 <decause> and then updating budget.fp.o accordingly with the numbers
-18:16:01 <decause> I am accountable for getting the numbers into "production" but regions are accountable for delivering their numbers to the repository
-18:16:07 <jwb> i have a question
-18:16:15 <decause> yes, now is a good time for questions
-18:16:31 <jwb> why would you use a spreadsheet and then manually transfer data to the repo, instead of just taking pull requests to the repo?
-18:17:19 <decause> preferably, all the data would come in as pull-requests; the same way we collaborate on other kinds of infrastructure
-18:17:33 <decause> currently, the most common way budget has been reported is via spreadsheet
-18:17:35 <cwickert> ?
-18:18:07 <decause> I'm more interested in having a central place where all the data can be seen, and working out the standard way it is reported across regions
-18:18:10 <decause> which we haven't tried before
-18:18:12 <decause> cwickert:
-18:18:27 <MarkDude> Standardizing regional things whilst we have special rules for India seems dubious at best. It sets the region in a non parity state, IMO. It'1 2016, can we still have "special rules for the brown folks in India?" (This is in context of parity of regions, reporting, making budgets, etc.)
-18:18:41 <jwb> a spreadsheet -> repo method seems like a lot of manual work that is error prone
-18:18:51 <cwickert> I wonder why there is this strong focus on tooling because I don't think we had a tooling problem in the past. AFAICS the problem was always manpower and I'm afraid with the different roles this will get worse.
-18:18:55 <mattdm> MarkDude: hold that for a second plase
-18:18:58 <MarkDude> And fed msg bus could help with at least parts of this. It's untapped to fully help us do things smoothly
-18:19:11 <cwickert> But this is just a side-question and has nothing to do with the actual numbers
-18:19:23 <MarkDude> No prob FPL :)
-18:19:44 <decause> cwickert: the problem before has been cycles, agreed
-18:20:18 <decause> the roles make sure that we know who is responsible for what
-18:20:35 <cwickert> decause: did you manage to fill all vacant roles?
-18:20:40 <decause> rather than all the ambassadors unofficially picking somone to carry the load of reporting expenses, we officially pick a person,a nd support them
-18:20:41 <mattdm> the main problem with tooling I saw was having everything in one place. even with the wiki before, it's really inconsistant
-18:21:45 <decause> cwickert: I have not gotten responses from all regions yet, no, but in light of there being actual numbers at stake, I expect an elevated level of attention and interest
-18:22:37 <cwickert> decause: ok, let's see. ignore my question and let's move on to crunching numbers then
-18:22:51 <decause> designating roles and having accountability is how we do #action items in meetings, and it is something I think will improve follow-through. we'll see how the experiment ends up :)
-18:23:06 <decause> cwickert: nod nod nod
-18:23:23 <decause> any other questions on process before we go forward with numbers?
-18:23:30 <mattdm> tools are the easy part; figuring out what to do with limited budget is much harder :-/
-18:23:36 <decause> mattdm: agreed.
-18:24:16 <MarkDude> mattdm: +1
-18:24:54 <decause> briefly, to markdude's question: The is no special policy for India. India is part of APAC, and their regional budget is what the scope of this meeting is about.
-18:25:13 <decause> other questions?
-18:25:14 <decause> going once
-18:25:16 <decause> going twice
-18:25:17 <decause> going thrice
-18:25:28 <decause> #topic Crunching the Numbers
-18:25:49 <decause> So, I think mattdm has characterized the crunch nicely in the update to council list
-18:26:02 <decause> and I would add some flavor
-18:26:57 <decause> keeping the budget at historical levels has been due to our ability to report on what we've spent, and how that expenditure creates value for the project.
-18:27:05 <decause> we want to grow
-18:27:09 <MarkDude> Process is same to join all parts of Fedora, minus rules for India. By definition special rules, tho Im dropping it due to not the time. Shutting up :)
-18:27:12 <decause> and growing means growing pains
-18:27:36 <decause> this year, we've already seen an increased demand for Fedora Events (FADs) that is up from historical levels
-18:27:50 <decause> so, we're probably not going to have enough budget to do all the thigns we want to do
-18:28:04 <decause> the important part to remember, is that a budget cycle is a full year
-18:28:14 <decause> and if we want to impact the budget, it takes months to do it
-18:28:36 <mattdm> (although note on FADs: it's not necessarily up hugely from earlier, just up from what the flat budget is based on, which leads to a dissonance)
-18:28:38 <decause> so this year, is going to be all about getting our metrics and numbers square, so that we can tell the story *next* year for increasing and growing our budget
-18:29:14 <mattdm> decause++
-18:29:22 <cwickert> !
-18:29:29 <decause> cwickert: you can just chime in ;)
-18:29:38 <cwickert> We've always had this problem and the only way to improve is with proper reporting
-18:29:45 <decause> 100% agreed
-18:29:46 <decause> yes
-18:29:49 <cprofitt> +1
-18:29:54 <cwickert> that also means: We (at least in EMEA) requested more then we got
-18:30:08 <cwickert> and at that point we just had to do a haircut
-18:30:17 <cwickert> trim all events by x percent
-18:30:25 <cwickert> and even skip some small ones
-18:30:26 <MarkDude> If we dont spend the money in a cycle, we may get less. This is partly responsible for "budget issues" we had in another region years ago. Funding needs change. Based on many things. I did NOT want to do release parties for a while, partly due to the Distro being not too usable. Following consistency model I should have had events, so I can do them now?
-18:31:02 <cwickert> I don't think this should be a problem, we just need to pay a little attention. But I'm all for making the FAds happen, even if this means spending less on other events
-18:31:20 <cprofitt> spending money to ensure the ability to spend it in the future is a bad way of running the ship.
-18:31:28 <robyduck> cwickert: +1
-18:32:10 <cprofitt> +1 cwickert
-18:32:27 <MarkDude> RH has the money, we made the product. Some regions choose not to do extra events due to monies. Things vary.
-18:32:30 <MarkDude> cprofitt: +1
-18:32:31 <decause> cwickert: and it is my hope that by improving the connection between ambassadors and commops, we don't ahve to leave event owners to do the reporting entirely on their own
-18:33:14 <decause> cprofitt: yes, budget is odd in this way, here or in other places. What we have not done before is keeping track of the "hair" that we left on the floor after trimming
-18:33:42 <mattdm> cprofitt: Agreed. We need to be able to show the impact of money spent.
-18:33:49 <decause> if there is an event/opportunity that we are *not* taking, we should record that opportunity cost somewhere so that next year, when we propose the budget, we can make the case for increase.
-18:34:08 <mattdm> MarkDude: Well, keep in mind that this is far from all of the money spent on Fedora
-18:34:29 <MarkDude> False choice, we can do FADs AND local events. We can do more, and more importantly not lower our high standards in process. Having a 20% reserve is a decent way to allow for extras, yet still gauge.
-18:34:54 <cprofitt> decause: yes, if we can track those 'not done' this year items that may come back that would be good. Budget is always a bit difficult... one idea I like is having a small percentage of the budget that is allocated towards 'initiatives' - spefically trying new things.
-18:35:02 <cwickert> I think it comes down to: How can we make sure we make the FADs happen? I see two options: 1) allocate a good chunk of the budget and cut the regional events on the other hand. 2) use the regional budgets to sponsor FAD attendees. While 2 is more flexible, 1 is cleaner and will (hopefully) help us getting more money for FADs next year.
-18:35:05 <MarkDude> Yes FPL. Ty for letting me speak here to bring these points up. I'll lurk now, and let you folks do your awesomeness. :)
-18:35:36 <cprofitt> mattdm: yes, we need to show the imapct.
-18:35:56 <cprofitt> +1 decause on recording opportunities missed.
-18:36:01 <decause> MarkDude: increasing/reserves anything that is dealing with increasing the "big number" is out of scope for today's discussion. It is important that we have those conversations some where, but the time for adjustment has passed. We have to spend the numbers we have.
-18:36:38 <cprofitt> decause++ budget page looks good.
-18:36:41 <decause> cwickert: this is helpful
-18:37:32 <mattdm> So... what are our next steps here?
-18:37:43 <decause> mattdm: right
-18:37:57 <mattdm> I'd _really_ like to see something like https://pagure.io/fedora-budget/raw/master/f/FY17/proposedannualbudgets/emea/FedoraEMEABudgetFY2017.ods from LATAM, NA, and APAC
-18:38:52 <jwb> perhaps we can take the overall budget, allocate money for flock, FUDCons, and FADs, and then divide the remaining amount among the regions once we have the budgets from the regional coordianators?
-18:38:54 <decause> I have a very simple task ahead: update the budget numbers here: https://budget.fedoraproject.org/#budgetnumbers
-18:38:59 <jwb> er, coordinators
-18:39:39 <cprofitt> mattdm: would you want that spreadsheet to containe impact data or just expenses?
-18:39:40 <decause> jwb: that sounds about right, yes
-18:39:49 <mattdm> cprofitt: awesome question :)
-18:40:01 <decause> cprofitt: the "impact" data is part of the event reportin that we're going to track going forward
-18:40:09 <cprofitt> jwb +1 that sounds like a good way to do it.
-18:40:11 <mattdm> I was thinking maybe each thing have a link to an event page, which would contain that?
-18:40:26 <mattdm> cprofitt: but if you have a better idea I'd love to hear it
-18:40:47 <decause> I don't think we can "ex post facto" reporting standards onto last year, but we can do some archeology to dig that up for some events
-18:40:55 <decause> mattdm: +1
-18:41:08 <cprofitt> mattdm: hmm... I know that the BrickHack event we had attendee badges...
-18:41:13 <mattdm> FWIW, the breakdown in the previous regional budgets (considering regional budgets alone) is about: 16% APAC, 26% EMEA, 16% LATAM, 42% NA
-18:41:30 <decause> and going forward, the event reports, even if they are hosted on personal blogs, will be aggregated on the commblug
-18:41:33 <decause> commblog
-18:41:39 <decause> so that we have them all in one place later
-18:41:54 <decause> and there are some bullet points that get addressed in each post
-18:41:59 * decause digs up link for impact metrics:
-18:42:02 <mattdm> cprofitt: fedora-badges badges? that's definitely useful, since we can do analytics on that later.
-18:42:11 <jwb> mattdm: i'm not sure that breakdown holds any longer to be honest
-18:42:15 <cprofitt> the event page would help with 'expected attendance', 'actual attendance'... but measuring impact might need to have multiple inputs. Different events like converting to Python 3 might have better metrics based on commits.
-18:42:20 <decause> #link https://fedoraproject.org/wiki/Budget.next#Reimbursement
-18:42:33 <mattdm> jwb Yeah, that's just the historical allocations
-18:42:43 <mattdm> (also not including FUDCons/Flock)
-18:42:48 <cprofitt> we likely need to take a closer look at all the possible sources of metrics based on event types... and help organizers of future events be aware that those tools exist.
-18:42:58 <jwb> mattdm: i mention it because i think people need to be aware that historical allocations are not likely to match to this year's allocations
-18:43:23 <decause> cprofitt: yes, we have a script that is a PoC on tracking fedmsg data in the fedora-stats-tools repo
-18:43:49 <cprofitt> decause: yes, going back might not be worth the effort. Looking forward we just have to make sure we take a look at how to measure an event... ensure we give as much support to the person coordinating the event as possible.
-18:44:15 <mattdm> cprofitt++
-18:44:15 <zodbot> mattdm: Karma for cprofitt changed to 9 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
-18:44:17 <decause> cprofitt: these are great discussions to have, and I'm def into it from the commops side of things for sure
-18:44:29 <decause> falls squarely within "metrics" areas
-18:44:49 <decause> jwb: yes, I think this is good to point out as well
-18:44:51 <cprofitt> decause: yeah, likley a side conversation as it is a little bit of a birdwalk for this conversations main topic...
-18:45:19 <decause> so, as a warning, I mentioned on the ambassador list that if we didn't have a proposed budget reported, that it would impact our ability to allocate budget for a region
-18:45:22 <mattdm> Council members: I want to highlight what jwb said a few minutes ago. I agree and want to make sure no one _disagrees_....
-18:45:42 <mattdm> That is: we won't use historical percentage as the baseline for regional allocation
-18:45:52 <mattdm> (It _might_ end up like that, but it might not.)
-18:46:04 <mattdm> Does anyone disagree with that?
-18:46:13 <decause> +1 history does not dictate future necesarily
-18:46:18 <cprofitt> mattdm: so we want people to agree upfront to the 'norm' for determining budget?
-18:46:32 <cprofitt> I do not disagree mattdm
-18:46:37 <mattdm> cprofitt: I'm not sure I understand that question....
-18:47:02 <decause> cprofitt: we just want to be clear that this year's numbers will not necessarily be the same as last year's numbers per region
-18:47:02 <cwickert> -1
-18:47:03 <cprofitt> we want peole to agree with the method of allocating funds -- ahead of allocation..
-18:47:22 <decause> cprofitt: hang back for a sec, this is a big question
-18:47:34 <decause> cwickert: ?
-18:47:34 <cprofitt> k
-18:47:36 <jwb> cwickert: you disagree that historical budget allocation is not how we're going to allocate this year's budget?
-18:47:45 <cwickert> I think historical allocations are the only thing we can actually rely on
-18:48:02 <decause> meh
-18:48:14 <cwickert> and if we don't, we will punish the regions who did good reporting in the past
-18:48:21 <langdon> this paticular year? or future years?
-18:48:27 <jwb> cwickert: i think doing so is not responsible.  the 42% allocation to NA seems excessive given the growth of the contributor bases in the other regions
-18:49:19 <cwickert> jwb: good point, but I don't see how an increase in user base translates into numbers
-18:49:21 <jkurik> if we do not use the historical allocations what will be the way how the budget is distributed ?
-18:49:32 <decause> cwickert: contributor, not user
-18:49:33 <langdon> so.. i definitely agree that this year might be weird.. but why wouldn't we use historical in future years?
-18:49:56 <jwb> jkurik: perhaps we can look at the submitted budget and attempt to gauge impact of the events and activites
-18:50:19 <cprofitt> We want to, as a group, agree on a method for determining funding. Keeping in mind that this may, or may not, reflect historical spending. The method of allocation is meant to maximize impact and regional spending may flucuate based on multiple factors. What I am having issues grasping is what the other method is.
-18:50:28 <robyduck> we shoud at least keep history in mind when it comes to decide whether cut one or another region. Not relying totally on it, but neither forget it
-18:50:40 <mattdm> robyduck: yeah, well put
-18:50:41 <decause> Question have we ever had a standard "percentage" for each region?
-18:50:45 <jwb> robyduck: yes that is certainly fair
-18:50:49 <decause> I don't think we have
-18:50:50 <mattdm> also cprofitt, well put :)
-18:50:56 <jwb> decause: mattdm listed them above
-18:51:03 <langdon> also .. what does "historical" mean here? do you mean "na always gets 42%" or do you mean "na spent 42% last year and had xyz growth, we shoudl give them more"?
-18:51:14 <decause> jwb: for every year?
-18:51:19 <mattdm> I was *just* looking at the nominal allocations
-18:51:25 <mattdm> not even actual-spent money
-18:51:35 <cprofitt> perhaps having a two part system.... part of the budget is historical, with a portion being allocated based on potential impact.
-18:51:44 <jwb> decause: yes?
-18:52:04 <decause> ok, good to know.
-18:52:18 <cwickert> ok, let me rephrase what I wrote earlier: we need to give all regions a chance. They are to submit a budget, that's the process we always followed. but when we need to decide on the submitted budgets, then we need to have history in mind to see how realistic a request is. We had this 3 or 4 years with the APAC regions: They were very enthusiastic and requested a lot of money, but did not spend much in the end.
-18:52:28 <jwb> look, the fact is that we've had a flat budget for the past 5 years but we've been doing more.  if we cannot sufficiently explain why that budget needs to go up, through both accurate _planning_ and accurate _reporting_, it won't go up
-18:52:50 <decause> jwb: this is def the reality
-18:52:52 <decause> yes
-18:53:03 <cprofitt> example: 70% is allocated by historical and 30% is allocated by potential impact. I agree with cwickert that we need to ensure all regions know we are doing this and have a chance to get their reporting in place.
-18:53:32 <robyduck> jwb++
-18:53:32 <mattdm> cwickert: I can agree with that.
-18:53:34 <jwb> cwickert: yeah.  unfortunately, enthusiasm does not trump actually doing things.
-18:53:41 <langdon> cprofitt, that proposal does not account for "poor planning" ... aka asked for 10 spent 5
-18:54:04 <decause> cwickert: I think you're trying to future-proof against the right things, yes
-18:54:38 <cprofitt> langdon: it was meant to be a rough proposal. I agree we need to adjust based on actually spent money not proposed, but unspent.
-18:55:01 <mattdm> I'm definitely suffering from lack of standarization of process in the past
-18:55:21 <decause> mattdm: agreed. aggregating this history has been challenging
-18:55:37 <cwickert> cprofitt: not sure if we can do a percentage, but more something along the lines: Let them request money, look at the requests when they come in and then say: "Ok, region X has a tendency to under-spend, so we cut their budget by 20%, while region Z does very good reporting and therefor we cut their budget by only 5%. That's what we did in FAmSCo all the years.
-18:55:54 <cprofitt> mattdm: agreed we need to standardize and let everyone know what the process will be.
-18:56:05 <cprofitt> cwickert: that works for me.
-18:56:06 <cwickert> s/reporting/reporting+budgeting
-18:56:35 <cprofitt> we can also work with regions that have had inconsistent reporting / planning and help them improve.
-18:56:38 <cwickert> decause: we don't have numbers from the regions yet, right?
-18:56:57 <mattdm> cwickert: yeah, by not following history, I don't mean throwing all that out.
-18:56:59 <jwb> cwickert: i can agree with that somewhat.  my main point is that past allocation does not ensure future allocation.  it has to be somewhat results driven, based on whatever we consider "results" to be (e.g. perceived or actual impact, accuracy, etc)
-18:57:04 <dzho> one sees in federal research grant funding decisions the use of proposals vetted by peer review, the results of which are consulted by ultimate decision makers. It involves a lot of poorly rewarded work by those doing the review, but I wonder if there's anything useful from that model?
-18:57:11 <decause> cwickert: we have EMEA numbers, and some LATAM numbers, some rought NA numbers, but I need APAC numbers most
-18:57:20 <cprofitt> +1 jwb
-18:57:39 <mattdm> as far as know only EMEA and APAC have planned/actual budget numbers for FY15 and FY14
-18:57:39 <cwickert> jwb: sure, we totally agree and I'm all for enabling new contributors in other regions because this is where we can grow
-18:57:56 <jwb> dzho: i think that is essentially what we are proposing here, yes.  the peers in this case are the council and the regions
-18:58:10 <cwickert> decause: we have two FAmSCo members in APAC, let me talk to them on Wednesday
-18:58:19 <decause> cwickert: awesome, thank you
-18:58:45 <decause> dzho: yes, what jwb said
-18:58:57 * dzho nods, continues lurking
-18:59:43 <decause> so, from what it looks like, we want the future allocations to be *informed* by historical percentages, but adjusted by results and ahereance to the process
-19:00:00 <langdon> decause, and actuals
-19:00:10 <mattdm> okay, so, here we are an hour in. We should be looking at next steps :)
-19:00:21 <mattdm> I definitely think we should continue next Monday....
-19:00:27 <cprofitt> decause: yes.
-19:00:35 <jwb> step 1 was suggested.  which is basically, put in the values for flock, FADs, and fudcons
-19:00:35 <cprofitt> +1 mattdm
-19:00:36 <decause> mattdm: I believe we allocated an extra hour today
-19:00:37 <mattdm> but we should be looking at concerete decisions at that point.
-19:00:42 <decause> I did at least on fedocal last time
-19:01:02 <mattdm> jwb: I did that in a spreadsheet right before the meeting, which I then failed to save properly :)
-19:01:08 <jwb> decause: if you've imported the ical from fedocal, it does not update
-19:01:26 <mattdm> An open question is whether we're going to put the proposed $17k into the APAC FAD
-19:01:34 <decause> jwb: I think I only added it statically last week, which we cancelled, and then didn't double-blcok this week
-19:01:37 <decause> that is my bad
-19:01:48 <jwb> decause: er, update in whatever calendar you imported it to.  so i'm not sure anyone noticed if you changed it even if you did
-19:02:02 <jwb> mattdm: i mean in the budget.fp.org site
-19:02:06 <decause> jwb: I'll post those types of updates to the council-discuss next time too, just in case
-19:02:15 <mattdm> jwb: oh, good call.
-19:02:19 <jwb> people really love spreadsheets when they are just extra manual steps..
-19:02:31 <decause> jwb: the formulas are nice
-19:02:40 <decause> I prefer csv myself, it is portable and human readable
-19:02:55 <mattdm> spreadsheets suck. however, they're really convenient to hack on without knowing what you're really doing :)
-19:03:08 <decause> aspirationally, I'd love ot paint a picture of what budget reporting could be like :P
-19:03:18 <langdon> i heard jwb propose creating a taiga card for autouploading
-19:03:54 <nb> 17k for a FAD?
-19:03:56 <jwb> the council doesn't use taiga.  it could though, and i'd probably be way happier than using trac
-19:04:02 * nb thought they were generally 5k
-19:04:06 <mattdm> nb: er, sorry. FUDCon
-19:04:06 <nb> or are you talking about fudcon?
-19:04:08 <nb> oh ok
-19:04:18 <mattdm> which is also quite high
-19:04:18 <decause> If we get more information from the regions as we go forward, I'm ok with adjusting, but I've given notice on the lists, and reached out individually too (as cwickert will also do this week with apac)
-19:04:28 <mattdm> but basically what we approved for LATAM
-19:05:05 <cwickert> 17k for a FAD?
-19:05:10 <cwickert> where does this come from?
-19:05:22 <mattdm> cwickert: from me mistyping "FUDCon" :)
-19:05:23 <cwickert> ah, sorry, FUDCon
-19:05:31 <cwickert> sorry, slow reading the backlog
-19:06:41 <mattdm> decause: you wanna #action yourself for putting up a proposal on the budget.fpo page?
-19:07:28 <decause> #action decause post a proposed budget scenario to council list, and upload the document (spreadsheet or otherwise) to the pagure.io repo
-19:07:46 <mattdm> decause++
-19:07:55 <decause> mattdm: what I need to know from council is the preferred contours of the scenario
-19:07:58 <decause> i will crunch a few of them
-19:08:12 <mattdm> decause yeah, I was just gonna say a few possibilities would be nice
-19:08:18 <decause> but mostly I have to make 7 numbers happen:
-19:08:23 <decause> the first one is done:
-19:08:28 <decause> Total: 195,000
-19:08:56 <decause> I think cwickert original observation about rolling the FUDCon funding into 'council' instead of 'each region' was a keen one
-19:09:20 <MarkDude> +1
-19:09:28 <cwickert> decause: actually, premiere events have always been handled globally
-19:09:28 <decause> so I will take the proposed FUDCon and FLock (and pending FAD requests) and roll those into council
-19:09:38 <nb> cwickert++
-19:09:38 <zodbot> nb: Karma for cwickert changed to 7 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
-19:10:03 <decause> i will follow up with OSAS to find out if we got dedicated OSAS funding for Outreachy
-19:10:11 <decause> #action decause follow up with OSAS to find out if we got dedicated OSAS funding for Outreachy
-19:10:16 <cwickert> decause: I think the first step is premiere events vs. regional budget and then we can further distribute the regional budget.
-19:10:26 <mattdm> cwickert: yeah, except for in the FY14 budget email, where they were divvyed up to the regions even though then later handled centrally
-19:10:27 <decause> otherwise, I'd like to request that we allocate one slot per quarter as one scenario
-19:10:39 <decause> ideally 2 (tech and non-tech)
-19:10:44 <decause> that'll be one scenario
-19:10:59 <decause> but the overarching scenario, of the regional percentages
-19:11:23 <decause> those should hold as a "base-line" then, but will not be 100% the same as history
-19:11:28 <cwickert> and we could as well say: premiere events = council, regional budget = FAmSCo. That's what we did in the past. It wasn't perfect (for technical events in a region such as FADs), but it worked.
-19:11:50 <robyduck> yup
-19:11:52 <mattdm> I'd like to see regional planning FADs budgeted in, and as line items for the regions
-19:12:26 <decause> #info regional budget planning FADs for each region, as part of the region's budget
-19:12:27 <cwickert> mattdm: if we fly the design team to the US for a FAD, how is that regional?
-19:12:40 <mattdm> there's some disparity in the docs on FADs about whether or not they regional events in general
-19:12:48 <decause> FAD is a centrally organized, not regionally organized event
-19:12:50 <cwickert> decause: I disagree with the #info
-19:12:53 <cwickert> right
-19:13:08 <mattdm> cwickert: but in what I meant above, I meant specifically region-focused planning FADs
-19:13:10 <nb> so we all should have a regional planning FAD now?
-19:13:19 <decause> cwickert: mattdm is talking about budte planning FADs, like what EMEA has been doing for years
-19:13:31 <decause> s/budte/budget
-19:13:36 * nb not opposed
-19:13:47 <mattdm> nb I think it's a good model. It makes sense to colocate it with other events (Flock, FUDCons) when possible
-19:13:51 <cwickert> mattdm, decause: that should be one FAD for each region, so easy to budget.
-19:14:00 <nb> mattdm, yeah
-19:14:03 <cwickert> s/budget/project
-19:14:03 <decause> nb: yes, we should, so that there are *always* numbers for the council to consider in the future, unlike today ;)
-19:14:21 <mattdm> cwickert: yeah, and that's why I was suggesting putting them as line items in the regions
-19:14:29 <nb> decause, mattdm good idea
-19:14:32 <nb> we did that a few years ago in NA
-19:14:34 <cwickert> mattdm: makes sense
-19:14:52 <nb> Blacksburg maybe, we had the FAD the day before fudcon, then more people got to stay for fudcon also
-19:15:01 <decause> mattdm: standard $5K FAD limit?
-19:15:03 <mattdm> nb exactly, yeah.
-19:15:10 <cwickert> mattdm: note we might not even need a planing FAD in some regions if they have FLOCK or a FUDCon
-19:15:10 <mattdm> decause: up in the air, I think
-19:15:19 <cwickert> decause: yes, 5k should be ok everywhere
-19:15:20 * mattdm squints at that bottom line
-19:15:26 <decause> mattdm: agreed. I can try to crunch a high and low scenario then
-19:15:34 * decause signs up for more work
-19:15:37 <decause> :P
-19:15:38 <mattdm> decause++
-19:15:39 <nb> cwickert, true, depending on how many people get funded for flock/fudcon otherwise
-19:15:52 * nb sees it more as "paying for more people to go to Flock, given that there is a planning session at flock"
-19:15:54 <mattdm> cwickert: I'd rather say "we have the planning FAD at Flock/FUDCon"
-19:15:54 <nb> or something like that
-19:15:59 <nb> mattdm++
-19:15:59 <zodbot> nb: Karma for mattdm changed to 12 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
-19:16:01 <decause> the good news is, Flock planning has given their number at $75K this year
-19:16:09 <cwickert> mattdm: that's what I meant
-19:16:09 <decause> same as last year
-19:16:18 <mattdm> cwickert: cool
-19:16:27 <decause> so, that is a nice 'not-dotted-line' item
-19:16:52 <jwb> that's an interesting way to put it :)
-19:17:10 <cwickert> decause: prices are highter are EMEA and NA, but travel is more expensive in APAC and LATAM. So 5k for a planning FAD should do everywhere and if it is co-located with another event, we just skip it in the budget.
-19:17:29 <robyduck> to avoid confusion, why don't we put those planning FAD events in the reginal budget and handle the other FADs globally? This way every region also can manage their budget better, doing the planing with other events like fudcon or flock.
-19:17:42 <robyduck> just a thought
-19:17:48 <jwb> cwickert: no... we show the that 5k was allocated to bring more people to Flock/FUDCon
-19:17:53 <jwb> we don't "skip" things any more
-19:17:56 <mattdm> robyduck: I think that's what we're saying
-19:18:08 <decause> robyduck: yeah, what mattdm said
-19:18:10 <nb> jwb++
-19:18:10 <zodbot> nb: Karma for jwboyer changed to 9 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
-19:18:13 <robyduck> we can name them differently
-19:18:30 <robyduck> but that's a detail
-19:18:33 <cwickert> jwb: ok, if you put it that way.
-19:19:02 <decause> we're going to be settling on a standard format for reporting these things (my vote is based off the very decent EMEA sheet)
-19:19:06 <mattdm> I am all for finding more ways to get involved, active people on the ground at Flock that don't involve them needing to give a talk
-19:19:22 <decause> #link https://docs.google.com/spreadsheets/d/11nWHrooCwoiWqGx4iEUnITQAWwQrQ6_2ito8GUtBk_g/edit#gid=0
-19:19:30 <nb> mattdm, i agree.  I mainly only submitted a talk so that I could hopefully get funding
-19:19:35 <robyduck> mattdm: would be nice
-19:19:47 * nb wnats to go to plan stuff for next year in NA
-19:19:54 <mattdm> that's probably a conversation for another time, though :)
-19:19:59 <decause> agreed
-19:20:13 <decause> I'm going to be pushing my updates to the pagure.io/fedora-budget repo
-19:20:20 <decause> they'll likely be spreadsheets/csv
-19:20:28 <decause> unless jwb, you have a better suggestion?
-19:20:45 * decause is *def* open to better ideas
-19:21:07 <jwb> i suggested just updating the website with pull requests, but whatever works for the people actually doing this is what will work best
-19:21:18 <mattdm> I saw whatever works, is consistent, and puts 'em all in the same place for later
-19:21:30 <decause> jwb: the website does not get granular down to the proposed budget levels (yet)
-19:21:52 <decause> standing up the entire 'fedora-websites' repo is a bit much to just twiddle a number
-19:21:55 <decause> imho
-19:22:25 <decause> jwb: but yeah, the future /could/ look like a webhook that updates the production site based on data in fedora-budget repo
-19:22:28 <decause> ideal bridge
-19:22:31 <decause> +1 jwb
-19:22:39 * cwickert needs to run now, it's already late here. I will read the log later, but so far I'm happy with decause's approach.
-19:23:03 <decause> cwickert: thank you for your support, and I'll be sure to add council to the pagure.io members with push/pull access
-19:23:17 <mattdm> thanks cwickert!
-19:23:20 <decause> doing budget with PR's is going to be *much* better than emailing spreadsheets
-19:23:31 <cwickert> #action cwickert to discuss the budget with FAMSCo, in particular from APAC and LATAM
-19:23:58 <cwickert> ok, bye
-19:25:13 <nb> decause, we could always make it a separate repo
-19:25:25 <decause> nb: http://pagure.io/fedora-budget
-19:25:30 <decause> ok
-19:25:31 <decause> so
-19:25:40 * mattdm isn't technically leaving but is starting to have wandering-brain syndrome....
-19:25:55 <decause> what were those percentages again? I can dig for them in the logs, but it'd be nice to have some consensus on what they are
-19:26:18 <nb> decause, oh ok
-19:26:36 <decause> nb: which, btw, there is a NA folder that could *totally* use some input ;)
-19:26:41 <mattdm> decause the historical fraction?
-19:26:42 <decause> nb++
-19:26:46 <decause> mattdm: yes
-19:26:55 * decause didn't know there was one before today
-19:27:15 <mattdm> decause: roughly: APAC 16% EMEA 26% LATAM 16% NA 42%
-19:27:28 <decause> I'll have a few scenarios for everyone to discuss next week
-19:27:33 <mattdm> it's not a rule -- it's an extrapolation from FY14, FY15, FY16
-19:27:56 <decause> mattdm: acknowleged, I think we all agreed that it is more of a 'guideline' than a rule
-19:28:02 <decause> +1
-19:28:17 <decause> next week we should still do a double block though, yeah?
-19:28:35 <mattdm> decause: well, I think we shouldn't even consider it a guideline -- more, another input into the process
-19:28:44 <mattdm> decause: yeah, I think double-book is good
-19:28:55 <decause> #action decause schedule double-block council meeting for budgeting on fedocal
-19:29:06 <langdon> literally dbl? or 2h?
-19:29:14 <mattdm> 2h = dbl
-19:29:29 <mattdm> or I guess we could also get #fedora-meeting-1 :)
-19:29:33 <decause> #help Ambassadors please submit your Budget Reports, Proposals, and Delegation Selections to decause ASAP
-19:30:10 <mattdm> #info where ASAP really means "this week, because we want to decide things next week, so we can actually spend money without fear"
-19:30:39 <langdon> probably should info those fy16 allocations too, no?
-19:31:17 <mattdm> langdon: maybe?
-19:31:32 <decause> langdon: I don't think they are supposed to be 'concrete'
-19:31:50 <langdon> decause, well.. they were for fy16, right?
-19:32:21 <mattdm> more info doesn't hurt
-19:32:24 <decause> langdon: I thought mattdm said they were conglomerated from history,not just last year
-19:32:25 * mattdm composes an info
-19:32:32 <langdon> ok
-19:32:39 <decause> yeah, since mattdm crunched, he knows best
-19:33:36 <mattdm> #info Allocation of regional portion of budget over last three years roughly APAC 16%, EMEA 26%, LATAM 16%, NA 42%. This is nominal, not money actually spent. FY17 and future budgets not necessarily based on this number.
-19:33:42 <decause> mattdm: since I'm going to be travelling on Thursday, and attending all-weekend events, the sooner the better. I'd like to have the scenarios posted by Wednesday in an ideal world
-19:33:57 <decause> mattdm++
-19:34:38 <mattdm> decause: hopefully that can happen :)
-19:35:29 <decause> mattdm: :)
-19:35:35 <decause> ok
-19:35:45 <decause> I think we're all in a good place here?
-19:36:00 <jwb> yes
-19:36:04 <mattdm> Good enough. Planning to be in a great place this time next year.
-19:36:09 <mattdm> Thanks, everyone!
-19:36:27 <mattdm> (esp. decause who did the bulk of the typing!)
-19:36:30 <mattdm> #endmeeting
- diff --git a/FY17/adjustedannualbudgets/council/council.2016-04-11-18.00.log.txt b/FY17/adjustedannualbudgets/council/council.2016-04-11-18.00.log.txt deleted file mode 100644 index a92fffa..0000000 --- a/FY17/adjustedannualbudgets/council/council.2016-04-11-18.00.log.txt +++ /dev/null @@ -1,447 +0,0 @@ -18:00:15 #startmeeting Council (2016-04-11) -18:00:15 Meeting started Mon Apr 11 18:00:15 2016 UTC. The chair is mattdm. Information about MeetBot at http://wiki.debian.org/MeetBot. -18:00:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. -18:00:15 The meeting name has been set to 'council_(2016-04-11)' -18:00:17 #meetingname council -18:00:17 The meeting name has been set to 'council' -18:00:19 #chair mattdm jkurik jwb cwickert langdon decause robyduck tatica -18:00:19 Current chairs: cwickert decause jkurik jwb langdon mattdm robyduck tatica -18:00:21 #topic Introductions, Welcomes -18:00:25 .hello langdon -18:00:26 langdon: langdon 'Langdon White' -18:00:31 hi -18:00:32 .hello jkurik -18:00:34 jkurik: jkurik 'Jan Kurik' -18:00:42 .hello mattdm -18:00:43 mattdm: mattdm 'Matthew Miller' -18:00:44 .hello decause -18:00:44 .fas robyduck -18:00:45 decause: decause 'Remy DeCausemaker' -18:00:48 .hello cwickert -18:00:48 robyduck: robyduck 'Robert Mayr' -18:00:51 cwickert: cwickert 'Christoph Wickert' -18:01:23 whoo, good crowd today :) -18:02:23 well, let's get right to it... -18:02:40 #topic Initial FY17 budget meeting -18:02:47 * decause drumrolls -18:03:12 ideally, this wouldn't be "initial" -- the initial meeting really should have been in September -18:03:18 but we're getting a new process started -18:03:20 see -18:03:24 #link https://budget.fedoraproject.org/ -18:03:30 #info new budget process site -18:03:48 we're currently at the "adjustment/allocation" stage -18:04:01 having gotten the community budget numbers from our sponsor -18:04:16 decause, you wanna take this? -18:04:27 mattdm: the big number, yeah? -18:04:31 yeah -18:04:43 #topic The Big Number -18:04:52 #link http://lists.fedoraproject.org/archives/list/council-discuss@lists.fedoraproject.org/message/TML72C4572A6FVK6UJDFCMUN56T4PKJ4/ -18:05:04 #info The Big Number this year, is the same as last year, at $195,000 -18:05:05 #info email from mattdm summarizing things from this morning -18:05:34 the difference this year, is how we discuss and prioritize making that number stretch -18:06:01 #info That covers events, swag, Fedora conferences, activity days, and any other community spending -18:06:20 *everything* -18:06:24 #info Does not include infrastructure, hardware, etc -18:06:42 meant to put one * on that 'everything' ;) -18:07:23 we should just take a moment to make sure everyone here has read mattdm's email to the council list today -18:07:29 * mattdm quiets up and lets decause talk -18:07:45 (although if anything was unclear, I can help explain) -18:07:45 as it condenses all the history into one succinct place -18:08:22 I've spent the past few weeks shaking the trees to get our regional information into one place, which mattdm has done a great job of compiling -18:08:31 our new budget site -18:08:40 #link http://budget.fedoraproject.org -18:09:10 is where we'll announce the regional allocations -18:09:29 as well as the central budget for Fedora events -18:10:27 Regions are still responsible for crunching/reporting their own numbers, but they have additional support now via the Community Blog and CommOps team to help publicize and socialize their events -18:10:40 as well as help with gathering some impact metrics for such activity -18:11:24 a place where we're gathering all the budget information is the new fedora-budget repository hosted on pagure -18:11:32 #link http://pagure.io/fedora-budget -18:12:23 by treating the budget process the same way we treat other infrastructure within fedora, and use the same tools to wrangle it, we can make it much easier to distribute the load of reporting -18:13:08 right now, there are directories for each fiscal year, and each region, but the data we have from year's past has not been fully committed to the repository -18:13:40 which is a "nice-to-have" for historical reasons, but not entirely necessary for today's talks -18:14:57 I'm going to be working with the delegates from each region to standardize on a reporting mechanism (spreadsheet) that we use on a quarterly basis to report on action and impact -18:15:08 and then updating budget.fp.o accordingly with the numbers -18:16:01 I am accountable for getting the numbers into "production" but regions are accountable for delivering their numbers to the repository -18:16:07 i have a question -18:16:15 yes, now is a good time for questions -18:16:31 why would you use a spreadsheet and then manually transfer data to the repo, instead of just taking pull requests to the repo? -18:17:19 preferably, all the data would come in as pull-requests; the same way we collaborate on other kinds of infrastructure -18:17:33 currently, the most common way budget has been reported is via spreadsheet -18:17:35 ? -18:18:07 I'm more interested in having a central place where all the data can be seen, and working out the standard way it is reported across regions -18:18:10 which we haven't tried before -18:18:12 cwickert: -18:18:27 Standardizing regional things whilst we have special rules for India seems dubious at best. It sets the region in a non parity state, IMO. It'1 2016, can we still have "special rules for the brown folks in India?" (This is in context of parity of regions, reporting, making budgets, etc.) -18:18:41 a spreadsheet -> repo method seems like a lot of manual work that is error prone -18:18:51 I wonder why there is this strong focus on tooling because I don't think we had a tooling problem in the past. AFAICS the problem was always manpower and I'm afraid with the different roles this will get worse. -18:18:55 MarkDude: hold that for a second plase -18:18:58 And fed msg bus could help with at least parts of this. It's untapped to fully help us do things smoothly -18:19:11 But this is just a side-question and has nothing to do with the actual numbers -18:19:23 No prob FPL :) -18:19:44 cwickert: the problem before has been cycles, agreed -18:20:18 the roles make sure that we know who is responsible for what -18:20:35 decause: did you manage to fill all vacant roles? -18:20:40 rather than all the ambassadors unofficially picking somone to carry the load of reporting expenses, we officially pick a person,a nd support them -18:20:41 the main problem with tooling I saw was having everything in one place. even with the wiki before, it's really inconsistant -18:21:45 cwickert: I have not gotten responses from all regions yet, no, but in light of there being actual numbers at stake, I expect an elevated level of attention and interest -18:22:37 decause: ok, let's see. ignore my question and let's move on to crunching numbers then -18:22:51 designating roles and having accountability is how we do #action items in meetings, and it is something I think will improve follow-through. we'll see how the experiment ends up :) -18:23:06 cwickert: nod nod nod -18:23:23 any other questions on process before we go forward with numbers? -18:23:30 tools are the easy part; figuring out what to do with limited budget is much harder :-/ -18:23:36 mattdm: agreed. -18:24:16 mattdm: +1 -18:24:54 briefly, to markdude's question: The is no special policy for India. India is part of APAC, and their regional budget is what the scope of this meeting is about. -18:25:13 other questions? -18:25:14 going once -18:25:16 going twice -18:25:17 going thrice -18:25:28 #topic Crunching the Numbers -18:25:49 So, I think mattdm has characterized the crunch nicely in the update to council list -18:26:02 and I would add some flavor -18:26:57 keeping the budget at historical levels has been due to our ability to report on what we've spent, and how that expenditure creates value for the project. -18:27:05 we want to grow -18:27:09 Process is same to join all parts of Fedora, minus rules for India. By definition special rules, tho Im dropping it due to not the time. Shutting up :) -18:27:12 and growing means growing pains -18:27:36 this year, we've already seen an increased demand for Fedora Events (FADs) that is up from historical levels -18:27:50 so, we're probably not going to have enough budget to do all the thigns we want to do -18:28:04 the important part to remember, is that a budget cycle is a full year -18:28:14 and if we want to impact the budget, it takes months to do it -18:28:36 (although note on FADs: it's not necessarily up hugely from earlier, just up from what the flat budget is based on, which leads to a dissonance) -18:28:38 so this year, is going to be all about getting our metrics and numbers square, so that we can tell the story *next* year for increasing and growing our budget -18:29:14 decause++ -18:29:22 ! -18:29:29 cwickert: you can just chime in ;) -18:29:38 We've always had this problem and the only way to improve is with proper reporting -18:29:45 100% agreed -18:29:46 yes -18:29:49 +1 -18:29:54 that also means: We (at least in EMEA) requested more then we got -18:30:08 and at that point we just had to do a haircut -18:30:17 trim all events by x percent -18:30:25 and even skip some small ones -18:30:26 If we dont spend the money in a cycle, we may get less. This is partly responsible for "budget issues" we had in another region years ago. Funding needs change. Based on many things. I did NOT want to do release parties for a while, partly due to the Distro being not too usable. Following consistency model I should have had events, so I can do them now? -18:31:02 I don't think this should be a problem, we just need to pay a little attention. But I'm all for making the FAds happen, even if this means spending less on other events -18:31:20 spending money to ensure the ability to spend it in the future is a bad way of running the ship. -18:31:28 cwickert: +1 -18:32:10 +1 cwickert -18:32:27 RH has the money, we made the product. Some regions choose not to do extra events due to monies. Things vary. -18:32:30 cprofitt: +1 -18:32:31 cwickert: and it is my hope that by improving the connection between ambassadors and commops, we don't ahve to leave event owners to do the reporting entirely on their own -18:33:14 cprofitt: yes, budget is odd in this way, here or in other places. What we have not done before is keeping track of the "hair" that we left on the floor after trimming -18:33:42 cprofitt: Agreed. We need to be able to show the impact of money spent. -18:33:49 if there is an event/opportunity that we are *not* taking, we should record that opportunity cost somewhere so that next year, when we propose the budget, we can make the case for increase. -18:34:08 MarkDude: Well, keep in mind that this is far from all of the money spent on Fedora -18:34:29 False choice, we can do FADs AND local events. We can do more, and more importantly not lower our high standards in process. Having a 20% reserve is a decent way to allow for extras, yet still gauge. -18:34:54 decause: yes, if we can track those 'not done' this year items that may come back that would be good. Budget is always a bit difficult... one idea I like is having a small percentage of the budget that is allocated towards 'initiatives' - spefically trying new things. -18:35:02 I think it comes down to: How can we make sure we make the FADs happen? I see two options: 1) allocate a good chunk of the budget and cut the regional events on the other hand. 2) use the regional budgets to sponsor FAD attendees. While 2 is more flexible, 1 is cleaner and will (hopefully) help us getting more money for FADs next year. -18:35:05 Yes FPL. Ty for letting me speak here to bring these points up. I'll lurk now, and let you folks do your awesomeness. :) -18:35:36 mattdm: yes, we need to show the imapct. -18:35:56 +1 decause on recording opportunities missed. -18:36:01 MarkDude: increasing/reserves anything that is dealing with increasing the "big number" is out of scope for today's discussion. It is important that we have those conversations some where, but the time for adjustment has passed. We have to spend the numbers we have. -18:36:38 decause++ budget page looks good. -18:36:41 cwickert: this is helpful -18:37:32 So... what are our next steps here? -18:37:43 mattdm: right -18:37:57 I'd _really_ like to see something like https://pagure.io/fedora-budget/raw/master/f/FY17/proposedannualbudgets/emea/FedoraEMEABudgetFY2017.ods from LATAM, NA, and APAC -18:38:52 perhaps we can take the overall budget, allocate money for flock, FUDCons, and FADs, and then divide the remaining amount among the regions once we have the budgets from the regional coordianators? -18:38:54 I have a very simple task ahead: update the budget numbers here: https://budget.fedoraproject.org/#budgetnumbers -18:38:59 er, coordinators -18:39:39 mattdm: would you want that spreadsheet to containe impact data or just expenses? -18:39:40 jwb: that sounds about right, yes -18:39:49 cprofitt: awesome question :) -18:40:01 cprofitt: the "impact" data is part of the event reportin that we're going to track going forward -18:40:09 jwb +1 that sounds like a good way to do it. -18:40:11 I was thinking maybe each thing have a link to an event page, which would contain that? -18:40:26 cprofitt: but if you have a better idea I'd love to hear it -18:40:47 I don't think we can "ex post facto" reporting standards onto last year, but we can do some archeology to dig that up for some events -18:40:55 mattdm: +1 -18:41:08 mattdm: hmm... I know that the BrickHack event we had attendee badges... -18:41:13 FWIW, the breakdown in the previous regional budgets (considering regional budgets alone) is about: 16% APAC, 26% EMEA, 16% LATAM, 42% NA -18:41:30 and going forward, the event reports, even if they are hosted on personal blogs, will be aggregated on the commblug -18:41:33 commblog -18:41:39 so that we have them all in one place later -18:41:54 and there are some bullet points that get addressed in each post -18:41:59 * decause digs up link for impact metrics: -18:42:02 cprofitt: fedora-badges badges? that's definitely useful, since we can do analytics on that later. -18:42:11 mattdm: i'm not sure that breakdown holds any longer to be honest -18:42:15 the event page would help with 'expected attendance', 'actual attendance'... but measuring impact might need to have multiple inputs. Different events like converting to Python 3 might have better metrics based on commits. -18:42:20 #link https://fedoraproject.org/wiki/Budget.next#Reimbursement -18:42:33 jwb Yeah, that's just the historical allocations -18:42:43 (also not including FUDCons/Flock) -18:42:48 we likely need to take a closer look at all the possible sources of metrics based on event types... and help organizers of future events be aware that those tools exist. -18:42:58 mattdm: i mention it because i think people need to be aware that historical allocations are not likely to match to this year's allocations -18:43:23 cprofitt: yes, we have a script that is a PoC on tracking fedmsg data in the fedora-stats-tools repo -18:43:49 decause: yes, going back might not be worth the effort. Looking forward we just have to make sure we take a look at how to measure an event... ensure we give as much support to the person coordinating the event as possible. -18:44:15 cprofitt++ -18:44:15 mattdm: Karma for cprofitt changed to 9 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any -18:44:17 cprofitt: these are great discussions to have, and I'm def into it from the commops side of things for sure -18:44:29 falls squarely within "metrics" areas -18:44:49 jwb: yes, I think this is good to point out as well -18:44:51 decause: yeah, likley a side conversation as it is a little bit of a birdwalk for this conversations main topic... -18:45:19 so, as a warning, I mentioned on the ambassador list that if we didn't have a proposed budget reported, that it would impact our ability to allocate budget for a region -18:45:22 Council members: I want to highlight what jwb said a few minutes ago. I agree and want to make sure no one _disagrees_.... -18:45:42 That is: we won't use historical percentage as the baseline for regional allocation -18:45:52 (It _might_ end up like that, but it might not.) -18:46:04 Does anyone disagree with that? -18:46:13 +1 history does not dictate future necesarily -18:46:18 mattdm: so we want people to agree upfront to the 'norm' for determining budget? -18:46:32 I do not disagree mattdm -18:46:37 cprofitt: I'm not sure I understand that question.... -18:47:02 cprofitt: we just want to be clear that this year's numbers will not necessarily be the same as last year's numbers per region -18:47:02 -1 -18:47:03 we want peole to agree with the method of allocating funds -- ahead of allocation.. -18:47:22 cprofitt: hang back for a sec, this is a big question -18:47:34 cwickert: ? -18:47:34 k -18:47:36 cwickert: you disagree that historical budget allocation is not how we're going to allocate this year's budget? -18:47:45 I think historical allocations are the only thing we can actually rely on -18:48:02 meh -18:48:14 and if we don't, we will punish the regions who did good reporting in the past -18:48:21 this paticular year? or future years? -18:48:27 cwickert: i think doing so is not responsible. the 42% allocation to NA seems excessive given the growth of the contributor bases in the other regions -18:49:19 jwb: good point, but I don't see how an increase in user base translates into numbers -18:49:21 if we do not use the historical allocations what will be the way how the budget is distributed ? -18:49:32 cwickert: contributor, not user -18:49:33 so.. i definitely agree that this year might be weird.. but why wouldn't we use historical in future years? -18:49:56 jkurik: perhaps we can look at the submitted budget and attempt to gauge impact of the events and activites -18:50:19 We want to, as a group, agree on a method for determining funding. Keeping in mind that this may, or may not, reflect historical spending. The method of allocation is meant to maximize impact and regional spending may flucuate based on multiple factors. What I am having issues grasping is what the other method is. -18:50:28 we shoud at least keep history in mind when it comes to decide whether cut one or another region. Not relying totally on it, but neither forget it -18:50:40 robyduck: yeah, well put -18:50:41 Question have we ever had a standard "percentage" for each region? -18:50:45 robyduck: yes that is certainly fair -18:50:49 I don't think we have -18:50:50 also cprofitt, well put :) -18:50:56 decause: mattdm listed them above -18:51:03 also .. what does "historical" mean here? do you mean "na always gets 42%" or do you mean "na spent 42% last year and had xyz growth, we shoudl give them more"? -18:51:14 jwb: for every year? -18:51:19 I was *just* looking at the nominal allocations -18:51:25 not even actual-spent money -18:51:35 perhaps having a two part system.... part of the budget is historical, with a portion being allocated based on potential impact. -18:51:44 decause: yes? -18:52:04 ok, good to know. -18:52:18 ok, let me rephrase what I wrote earlier: we need to give all regions a chance. They are to submit a budget, that's the process we always followed. but when we need to decide on the submitted budgets, then we need to have history in mind to see how realistic a request is. We had this 3 or 4 years with the APAC regions: They were very enthusiastic and requested a lot of money, but did not spend much in the end. -18:52:28 look, the fact is that we've had a flat budget for the past 5 years but we've been doing more. if we cannot sufficiently explain why that budget needs to go up, through both accurate _planning_ and accurate _reporting_, it won't go up -18:52:50 jwb: this is def the reality -18:52:52 yes -18:53:03 example: 70% is allocated by historical and 30% is allocated by potential impact. I agree with cwickert that we need to ensure all regions know we are doing this and have a chance to get their reporting in place. -18:53:32 jwb++ -18:53:32 cwickert: I can agree with that. -18:53:34 cwickert: yeah. unfortunately, enthusiasm does not trump actually doing things. -18:53:41 cprofitt, that proposal does not account for "poor planning" ... aka asked for 10 spent 5 -18:54:04 cwickert: I think you're trying to future-proof against the right things, yes -18:54:38 langdon: it was meant to be a rough proposal. I agree we need to adjust based on actually spent money not proposed, but unspent. -18:55:01 I'm definitely suffering from lack of standarization of process in the past -18:55:21 mattdm: agreed. aggregating this history has been challenging -18:55:37 cprofitt: not sure if we can do a percentage, but more something along the lines: Let them request money, look at the requests when they come in and then say: "Ok, region X has a tendency to under-spend, so we cut their budget by 20%, while region Z does very good reporting and therefor we cut their budget by only 5%. That's what we did in FAmSCo all the years. -18:55:54 mattdm: agreed we need to standardize and let everyone know what the process will be. -18:56:05 cwickert: that works for me. -18:56:06 s/reporting/reporting+budgeting -18:56:35 we can also work with regions that have had inconsistent reporting / planning and help them improve. -18:56:38 decause: we don't have numbers from the regions yet, right? -18:56:57 cwickert: yeah, by not following history, I don't mean throwing all that out. -18:56:59 cwickert: i can agree with that somewhat. my main point is that past allocation does not ensure future allocation. it has to be somewhat results driven, based on whatever we consider "results" to be (e.g. perceived or actual impact, accuracy, etc) -18:57:04 one sees in federal research grant funding decisions the use of proposals vetted by peer review, the results of which are consulted by ultimate decision makers. It involves a lot of poorly rewarded work by those doing the review, but I wonder if there's anything useful from that model? -18:57:11 cwickert: we have EMEA numbers, and some LATAM numbers, some rought NA numbers, but I need APAC numbers most -18:57:20 +1 jwb -18:57:39 as far as know only EMEA and APAC have planned/actual budget numbers for FY15 and FY14 -18:57:39 jwb: sure, we totally agree and I'm all for enabling new contributors in other regions because this is where we can grow -18:57:56 dzho: i think that is essentially what we are proposing here, yes. the peers in this case are the council and the regions -18:58:10 decause: we have two FAmSCo members in APAC, let me talk to them on Wednesday -18:58:19 cwickert: awesome, thank you -18:58:45 dzho: yes, what jwb said -18:58:57 * dzho nods, continues lurking -18:59:43 so, from what it looks like, we want the future allocations to be *informed* by historical percentages, but adjusted by results and ahereance to the process -19:00:00 decause, and actuals -19:00:10 okay, so, here we are an hour in. We should be looking at next steps :) -19:00:21 I definitely think we should continue next Monday.... -19:00:27 decause: yes. -19:00:35 step 1 was suggested. which is basically, put in the values for flock, FADs, and fudcons -19:00:35 +1 mattdm -19:00:36 mattdm: I believe we allocated an extra hour today -19:00:37 but we should be looking at concerete decisions at that point. -19:00:42 I did at least on fedocal last time -19:01:02 jwb: I did that in a spreadsheet right before the meeting, which I then failed to save properly :) -19:01:08 decause: if you've imported the ical from fedocal, it does not update -19:01:26 An open question is whether we're going to put the proposed $17k into the APAC FAD -19:01:34 jwb: I think I only added it statically last week, which we cancelled, and then didn't double-blcok this week -19:01:37 that is my bad -19:01:48 decause: er, update in whatever calendar you imported it to. so i'm not sure anyone noticed if you changed it even if you did -19:02:02 mattdm: i mean in the budget.fp.org site -19:02:06 jwb: I'll post those types of updates to the council-discuss next time too, just in case -19:02:15 jwb: oh, good call. -19:02:19 people really love spreadsheets when they are just extra manual steps.. -19:02:31 jwb: the formulas are nice -19:02:40 I prefer csv myself, it is portable and human readable -19:02:55 spreadsheets suck. however, they're really convenient to hack on without knowing what you're really doing :) -19:03:08 aspirationally, I'd love ot paint a picture of what budget reporting could be like :P -19:03:18 i heard jwb propose creating a taiga card for autouploading -19:03:54 17k for a FAD? -19:03:56 the council doesn't use taiga. it could though, and i'd probably be way happier than using trac -19:04:02 * nb thought they were generally 5k -19:04:06 nb: er, sorry. FUDCon -19:04:06 or are you talking about fudcon? -19:04:08 oh ok -19:04:18 which is also quite high -19:04:18 If we get more information from the regions as we go forward, I'm ok with adjusting, but I've given notice on the lists, and reached out individually too (as cwickert will also do this week with apac) -19:04:28 but basically what we approved for LATAM -19:05:05 17k for a FAD? -19:05:10 where does this come from? -19:05:22 cwickert: from me mistyping "FUDCon" :) -19:05:23 ah, sorry, FUDCon -19:05:31 sorry, slow reading the backlog -19:06:41 decause: you wanna #action yourself for putting up a proposal on the budget.fpo page? -19:07:28 #action decause post a proposed budget scenario to council list, and upload the document (spreadsheet or otherwise) to the pagure.io repo -19:07:46 decause++ -19:07:55 mattdm: what I need to know from council is the preferred contours of the scenario -19:07:58 i will crunch a few of them -19:08:12 decause yeah, I was just gonna say a few possibilities would be nice -19:08:18 but mostly I have to make 7 numbers happen: -19:08:23 the first one is done: -19:08:28 Total: 195,000 -19:08:56 I think cwickert original observation about rolling the FUDCon funding into 'council' instead of 'each region' was a keen one -19:09:20 +1 -19:09:28 decause: actually, premiere events have always been handled globally -19:09:28 so I will take the proposed FUDCon and FLock (and pending FAD requests) and roll those into council -19:09:38 cwickert++ -19:09:38 nb: Karma for cwickert changed to 7 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any -19:10:03 i will follow up with OSAS to find out if we got dedicated OSAS funding for Outreachy -19:10:11 #action decause follow up with OSAS to find out if we got dedicated OSAS funding for Outreachy -19:10:16 decause: I think the first step is premiere events vs. regional budget and then we can further distribute the regional budget. -19:10:26 cwickert: yeah, except for in the FY14 budget email, where they were divvyed up to the regions even though then later handled centrally -19:10:27 otherwise, I'd like to request that we allocate one slot per quarter as one scenario -19:10:39 ideally 2 (tech and non-tech) -19:10:44 that'll be one scenario -19:10:59 but the overarching scenario, of the regional percentages -19:11:23 those should hold as a "base-line" then, but will not be 100% the same as history -19:11:28 and we could as well say: premiere events = council, regional budget = FAmSCo. That's what we did in the past. It wasn't perfect (for technical events in a region such as FADs), but it worked. -19:11:50 yup -19:11:52 I'd like to see regional planning FADs budgeted in, and as line items for the regions -19:12:26 #info regional budget planning FADs for each region, as part of the region's budget -19:12:27 mattdm: if we fly the design team to the US for a FAD, how is that regional? -19:12:40 there's some disparity in the docs on FADs about whether or not they regional events in general -19:12:48 FAD is a centrally organized, not regionally organized event -19:12:50 decause: I disagree with the #info -19:12:53 right -19:13:08 cwickert: but in what I meant above, I meant specifically region-focused planning FADs -19:13:10 so we all should have a regional planning FAD now? -19:13:19 cwickert: mattdm is talking about budte planning FADs, like what EMEA has been doing for years -19:13:31 s/budte/budget -19:13:36 * nb not opposed -19:13:47 nb I think it's a good model. It makes sense to colocate it with other events (Flock, FUDCons) when possible -19:13:51 mattdm, decause: that should be one FAD for each region, so easy to budget. -19:14:00 mattdm, yeah -19:14:03 s/budget/project -19:14:03 nb: yes, we should, so that there are *always* numbers for the council to consider in the future, unlike today ;) -19:14:21 cwickert: yeah, and that's why I was suggesting putting them as line items in the regions -19:14:29 decause, mattdm good idea -19:14:32 we did that a few years ago in NA -19:14:34 mattdm: makes sense -19:14:52 Blacksburg maybe, we had the FAD the day before fudcon, then more people got to stay for fudcon also -19:15:01 mattdm: standard $5K FAD limit? -19:15:03 nb exactly, yeah. -19:15:10 mattdm: note we might not even need a planing FAD in some regions if they have FLOCK or a FUDCon -19:15:10 decause: up in the air, I think -19:15:19 decause: yes, 5k should be ok everywhere -19:15:20 * mattdm squints at that bottom line -19:15:26 mattdm: agreed. I can try to crunch a high and low scenario then -19:15:34 * decause signs up for more work -19:15:37 :P -19:15:38 decause++ -19:15:39 cwickert, true, depending on how many people get funded for flock/fudcon otherwise -19:15:52 * nb sees it more as "paying for more people to go to Flock, given that there is a planning session at flock" -19:15:54 cwickert: I'd rather say "we have the planning FAD at Flock/FUDCon" -19:15:54 or something like that -19:15:59 mattdm++ -19:15:59 nb: Karma for mattdm changed to 12 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any -19:16:01 the good news is, Flock planning has given their number at $75K this year -19:16:09 mattdm: that's what I meant -19:16:09 same as last year -19:16:18 cwickert: cool -19:16:27 so, that is a nice 'not-dotted-line' item -19:16:52 that's an interesting way to put it :) -19:17:10 decause: prices are highter are EMEA and NA, but travel is more expensive in APAC and LATAM. So 5k for a planning FAD should do everywhere and if it is co-located with another event, we just skip it in the budget. -19:17:29 to avoid confusion, why don't we put those planning FAD events in the reginal budget and handle the other FADs globally? This way every region also can manage their budget better, doing the planing with other events like fudcon or flock. -19:17:42 just a thought -19:17:48 cwickert: no... we show the that 5k was allocated to bring more people to Flock/FUDCon -19:17:53 we don't "skip" things any more -19:17:56 robyduck: I think that's what we're saying -19:18:08 robyduck: yeah, what mattdm said -19:18:10 jwb++ -19:18:10 nb: Karma for jwboyer changed to 9 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any -19:18:13 we can name them differently -19:18:30 but that's a detail -19:18:33 jwb: ok, if you put it that way. -19:19:02 we're going to be settling on a standard format for reporting these things (my vote is based off the very decent EMEA sheet) -19:19:06 I am all for finding more ways to get involved, active people on the ground at Flock that don't involve them needing to give a talk -19:19:22 #link https://docs.google.com/spreadsheets/d/11nWHrooCwoiWqGx4iEUnITQAWwQrQ6_2ito8GUtBk_g/edit#gid=0 -19:19:30 mattdm, i agree. I mainly only submitted a talk so that I could hopefully get funding -19:19:35 mattdm: would be nice -19:19:47 * nb wnats to go to plan stuff for next year in NA -19:19:54 that's probably a conversation for another time, though :) -19:19:59 agreed -19:20:13 I'm going to be pushing my updates to the pagure.io/fedora-budget repo -19:20:20 they'll likely be spreadsheets/csv -19:20:28 unless jwb, you have a better suggestion? -19:20:45 * decause is *def* open to better ideas -19:21:07 i suggested just updating the website with pull requests, but whatever works for the people actually doing this is what will work best -19:21:18 I saw whatever works, is consistent, and puts 'em all in the same place for later -19:21:30 jwb: the website does not get granular down to the proposed budget levels (yet) -19:21:52 standing up the entire 'fedora-websites' repo is a bit much to just twiddle a number -19:21:55 imho -19:22:25 jwb: but yeah, the future /could/ look like a webhook that updates the production site based on data in fedora-budget repo -19:22:28 ideal bridge -19:22:31 +1 jwb -19:22:39 * cwickert needs to run now, it's already late here. I will read the log later, but so far I'm happy with decause's approach. -19:23:03 cwickert: thank you for your support, and I'll be sure to add council to the pagure.io members with push/pull access -19:23:17 thanks cwickert! -19:23:20 doing budget with PR's is going to be *much* better than emailing spreadsheets -19:23:31 #action cwickert to discuss the budget with FAMSCo, in particular from APAC and LATAM -19:23:58 ok, bye -19:25:13 decause, we could always make it a separate repo -19:25:25 nb: http://pagure.io/fedora-budget -19:25:30 ok -19:25:31 so -19:25:40 * mattdm isn't technically leaving but is starting to have wandering-brain syndrome.... -19:25:55 what were those percentages again? I can dig for them in the logs, but it'd be nice to have some consensus on what they are -19:26:18 decause, oh ok -19:26:36 nb: which, btw, there is a NA folder that could *totally* use some input ;) -19:26:41 decause the historical fraction? -19:26:42 nb++ -19:26:46 mattdm: yes -19:26:55 * decause didn't know there was one before today -19:27:15 decause: roughly: APAC 16% EMEA 26% LATAM 16% NA 42% -19:27:28 I'll have a few scenarios for everyone to discuss next week -19:27:33 it's not a rule -- it's an extrapolation from FY14, FY15, FY16 -19:27:56 mattdm: acknowleged, I think we all agreed that it is more of a 'guideline' than a rule -19:28:02 +1 -19:28:17 next week we should still do a double block though, yeah? -19:28:35 decause: well, I think we shouldn't even consider it a guideline -- more, another input into the process -19:28:44 decause: yeah, I think double-book is good -19:28:55 #action decause schedule double-block council meeting for budgeting on fedocal -19:29:06 literally dbl? or 2h? -19:29:14 2h = dbl -19:29:29 or I guess we could also get #fedora-meeting-1 :) -19:29:33 #help Ambassadors please submit your Budget Reports, Proposals, and Delegation Selections to decause ASAP -19:30:10 #info where ASAP really means "this week, because we want to decide things next week, so we can actually spend money without fear" -19:30:39 probably should info those fy16 allocations too, no? -19:31:17 langdon: maybe? -19:31:32 langdon: I don't think they are supposed to be 'concrete' -19:31:50 decause, well.. they were for fy16, right? -19:32:21 more info doesn't hurt -19:32:24 langdon: I thought mattdm said they were conglomerated from history,not just last year -19:32:25 * mattdm composes an info -19:32:32 ok -19:32:39 yeah, since mattdm crunched, he knows best -19:33:36 #info Allocation of regional portion of budget over last three years roughly APAC 16%, EMEA 26%, LATAM 16%, NA 42%. This is nominal, not money actually spent. FY17 and future budgets not necessarily based on this number. -19:33:42 mattdm: since I'm going to be travelling on Thursday, and attending all-weekend events, the sooner the better. I'd like to have the scenarios posted by Wednesday in an ideal world -19:33:57 mattdm++ -19:34:38 decause: hopefully that can happen :) -19:35:29 mattdm: :) -19:35:35 ok -19:35:45 I think we're all in a good place here? -19:36:00 yes -19:36:04 Good enough. Planning to be in a great place this time next year. -19:36:09 Thanks, everyone! -19:36:27 (esp. decause who did the bulk of the typing!) -19:36:30 #endmeeting \ No newline at end of file diff --git a/FY17/adjustedannualbudgets/council/proposedadjustedbudgetfy17.csv b/FY17/adjustedannualbudgets/council/proposedadjustedbudgetfy17.csv deleted file mode 100644 index 8e9f0d5..0000000 --- a/FY17/adjustedannualbudgets/council/proposedadjustedbudgetfy17.csv +++ /dev/null @@ -1,78 +0,0 @@ -,,fF/fDI,fF/-DI,hF/DI,hF/hDI,hF/-DI -Events,,,,,, -------,,,,,, -"FUDCon LATAM",,15000,10000,10000,10000,10000 -"FUDCon APAC",,15000,15000,15000,15000,15000 -Flock,,75000,75000,75000,75000,75000 -FADs,,30000,30000,15000,15000,15000 -D&I,,11000,0,11000,5500,0 -,,,,,, -"Big Number",,195000,195000,195000,195000,195000 -subtotal,,156000,145000,126000,120500,115000 -Regional,,39000,50000,69000,74500,80000 -,,,,,, -"FADS Breakdown",,,,,, ---------------,,,,,, -Docs2016,,5000,5000,5000,5000,5000 -Design2016,,5000,5000,5000,5000,5000 -Cloud2016,,5000,5000,5000,5000,5000 -"FAD #1",,5000,0,0,0,0 -"FAD #2",,5000,0,0,0,0 -"FAD #3",,5000,0,0,0,0 -,,,,,, -"D&I Breakdown",,,,,, --------------,,,,,, -"Outreachy Winter",,5500,0,5500,2250,0 -"Outreachy Spring",,5500,0,5500,2250,0 -,,,,,, -,,,,,, -"Regions: R/4",,,,,, -------------,,,,,, -APAC,,9750,12500,17250,18625,20000 -EMEA,,9750,12500,17250,18625,20000 -LATAM,,9750,12500,17250,18625,20000 -NA,,9750,12500,17250,18625,20000 -,,,,,, -"Regions: R*HS",,,,,, --------------,,,,,, -"APAC (.16)",,6240,8000,11040,11920,12800 -"EMEA (.26)",,10140,13000,17940,19370,20800 -"LATAM (.16)",,6240,8000,11040,11920,12800 -"NA (.43)",,16380,21000,28980,31290,33600 -,,,,,, -"Historical Diff: R/4",,,,,, ---------------------,,,,,, -APAC,12650,9750,12500,17250,18625,20000 -,,-2900,-150,4600,5975,7350 -,,-0.23,,,,0.58 -,,,,,, -EMEA,27000,9750,12500,17250,18625,20000 -,,-17250,-14500,-9750,-8375,-7000 -,,-0.64,,,,-0.26 -,,,,,, -LATAM,16500,9750,12500,17250,18625,20000 -,,-6750,-4000,750,2125,3500 -,,-0.41,,,,0.21 -,,,,,, -NA,43850,9750,12500,17250,18625,20000 -,,-34100,-31350,-26600,-25225,-23850 -,,-0.78,,,,-0.54 -,,,,,, -,,,,,, -"Historical Diff: R*HS",,,,,, ----------------------,,,,,, -APAC,-0.16,6240,8000,11040,11920,12800 -,12650,-6410,-4650,-1610,-730,150 -,,-0.51,,,,0.01 -,,,,,, -EMEA,-0.26,10140,13000,17940,19370,20800 -,27000,-16860,-14000,-9060,-7630,-6200 -,,-0.62,,,,-0.23 -,,,,,, -LATAM,-0.16,6240,8000,11040,11920,12800 -,16500,-10260,-8500,-5460,-4580,-3700 -,,-0.62,,,,-0.22 -,,,,,, -NA,-0.42,16380,21000,28980,31290,33600 -,43850,-27470,-22850,-14870,-12560,-10250 -,,-0.63,,,,-0.23 diff --git a/FY17/adjustedannualbudgets/council/proposedadjustedbudgetfy17.gnumeric b/FY17/adjustedannualbudgets/council/proposedadjustedbudgetfy17.gnumeric deleted file mode 100644 index 4c14508..0000000 Binary files a/FY17/adjustedannualbudgets/council/proposedadjustedbudgetfy17.gnumeric and /dev/null differ diff --git a/FY17/adjustedannualbudgets/council/proposedadjustedbudgetfy17.ods b/FY17/adjustedannualbudgets/council/proposedadjustedbudgetfy17.ods deleted file mode 100644 index 416059a..0000000 Binary files a/FY17/adjustedannualbudgets/council/proposedadjustedbudgetfy17.ods and /dev/null differ diff --git a/FY17/adjustedannualbudgets/council/proposedadjustedbudgetfy17.txt b/FY17/adjustedannualbudgets/council/proposedadjustedbudgetfy17.txt deleted file mode 100644 index 8e9f0d5..0000000 --- a/FY17/adjustedannualbudgets/council/proposedadjustedbudgetfy17.txt +++ /dev/null @@ -1,78 +0,0 @@ -,,fF/fDI,fF/-DI,hF/DI,hF/hDI,hF/-DI -Events,,,,,, -------,,,,,, -"FUDCon LATAM",,15000,10000,10000,10000,10000 -"FUDCon APAC",,15000,15000,15000,15000,15000 -Flock,,75000,75000,75000,75000,75000 -FADs,,30000,30000,15000,15000,15000 -D&I,,11000,0,11000,5500,0 -,,,,,, -"Big Number",,195000,195000,195000,195000,195000 -subtotal,,156000,145000,126000,120500,115000 -Regional,,39000,50000,69000,74500,80000 -,,,,,, -"FADS Breakdown",,,,,, ---------------,,,,,, -Docs2016,,5000,5000,5000,5000,5000 -Design2016,,5000,5000,5000,5000,5000 -Cloud2016,,5000,5000,5000,5000,5000 -"FAD #1",,5000,0,0,0,0 -"FAD #2",,5000,0,0,0,0 -"FAD #3",,5000,0,0,0,0 -,,,,,, -"D&I Breakdown",,,,,, --------------,,,,,, -"Outreachy Winter",,5500,0,5500,2250,0 -"Outreachy Spring",,5500,0,5500,2250,0 -,,,,,, -,,,,,, -"Regions: R/4",,,,,, -------------,,,,,, -APAC,,9750,12500,17250,18625,20000 -EMEA,,9750,12500,17250,18625,20000 -LATAM,,9750,12500,17250,18625,20000 -NA,,9750,12500,17250,18625,20000 -,,,,,, -"Regions: R*HS",,,,,, --------------,,,,,, -"APAC (.16)",,6240,8000,11040,11920,12800 -"EMEA (.26)",,10140,13000,17940,19370,20800 -"LATAM (.16)",,6240,8000,11040,11920,12800 -"NA (.43)",,16380,21000,28980,31290,33600 -,,,,,, -"Historical Diff: R/4",,,,,, ---------------------,,,,,, -APAC,12650,9750,12500,17250,18625,20000 -,,-2900,-150,4600,5975,7350 -,,-0.23,,,,0.58 -,,,,,, -EMEA,27000,9750,12500,17250,18625,20000 -,,-17250,-14500,-9750,-8375,-7000 -,,-0.64,,,,-0.26 -,,,,,, -LATAM,16500,9750,12500,17250,18625,20000 -,,-6750,-4000,750,2125,3500 -,,-0.41,,,,0.21 -,,,,,, -NA,43850,9750,12500,17250,18625,20000 -,,-34100,-31350,-26600,-25225,-23850 -,,-0.78,,,,-0.54 -,,,,,, -,,,,,, -"Historical Diff: R*HS",,,,,, ----------------------,,,,,, -APAC,-0.16,6240,8000,11040,11920,12800 -,12650,-6410,-4650,-1610,-730,150 -,,-0.51,,,,0.01 -,,,,,, -EMEA,-0.26,10140,13000,17940,19370,20800 -,27000,-16860,-14000,-9060,-7630,-6200 -,,-0.62,,,,-0.23 -,,,,,, -LATAM,-0.16,6240,8000,11040,11920,12800 -,16500,-10260,-8500,-5460,-4580,-3700 -,,-0.62,,,,-0.22 -,,,,,, -NA,-0.42,16380,21000,28980,31290,33600 -,43850,-27470,-22850,-14870,-12560,-10250 -,,-0.63,,,,-0.23 diff --git a/FY17/adjustedannualbudgets/council/scenarios.txt b/FY17/adjustedannualbudgets/council/scenarios.txt deleted file mode 100644 index fef5b37..0000000 --- a/FY17/adjustedannualbudgets/council/scenarios.txt +++ /dev/null @@ -1,164 +0,0 @@ -=============================================================================== -Budget -=============================================================================== - -Scenario 1: Full FADs, Full Outreachy -Scenario 2: Full FADs, Zero Outreachy -Scenario 3: Half FADs, Full Outreachy -Scenario 4: Half FADs, Half Outreachy -Scenario 5: Half FADs, Zero Outreachy - -R/4: Regional budget, divided Evenly -R*HS: Historial Split (.16, .26, .16, .42) - -Legend: -------- - fF/FDI Full FADS, Full D&I - fF/-DI Full FADS, zero D&I - hF/DI half FADS, Full D&I - hF/hDI half FADS, Half D&I - hF/-DI half FADS, zero D&I - R/4 Regional budget, divided Evenly - R*HS Historical Split (.125, .27, .165, .438) - - - fF/fDI fF/-DI fF/hDI hF/DI hF/hDI hF/-DI -Events ------- - FUDCon LATAM 15000 10000 10000 10000 10000 10000 - FUDCon APAC 15000 15000 15000 15000 15000 15000 - Flock 75000 75000 75000 75000 75000 75000 - FADs 30000 30000 30000 15000 15000 15000 - D&I 11000 0 5500 11000 5500 0 - ---------------------------------------------------------------- - Big Number 195000 195000 195000 195000 195000 195000 - subtotal 156000 145000 135500 126000 120500 115000 - Regional 39000 50000 59500 69000 74500 80000 -FADS Breakdown - --------------- - Docs2016 5000 5000 5000 5000 5000 5000 - Design2016 5000 5000 5000 5000 5000 5000 - Cloud2016 5000 5000 5000 5000 5000 5000 - FAD #1 5000 0 5000 0 0 0 - FAD #2 5000 0 5000 0 0 0 - FAD #3 5000 0 5000 0 0 0 - -D&I Breakdown -------------- - Outreachy Winter 5500 0 2250 5500 2250 0 - Outreachy Spring 5500 0 2250 5500 2250 0 - - -Regions: R/4 ------------- - APAC 9750 12500 14875 17250 18625 20000 - EMEA 9750 12500 14875 17250 18625 20000 - LATAM 9750 12500 14875 17250 18625 20000 - -Regions: R*HS -------------- - APAC (.16) 6240 8000 9520 11040 11920 12800 - EMEA (.26) 10140 13000 15470 17940 19370 20800 - LATAM (.16) 6240 8000 9520 11040 11920 12800 - NA (.42) 16380 21000 24990 28980 31290 33600 - -Historical Diff: R/4 --------------------- - APAC (12650) 9750 12500 14875 17250 18625 20000 - -2900 -150 +2225 +4600 +5975 +7350 - -23% +18% +58% - - EMEA (27000) 9750 12500 14875 17250 18625 20000 - -17250 -14500 -12125 -9750 -8375 -7000 - -64% -45% -26% - - LATAM (16500) 9750 12500 14875 17250 18625 20000 - -6750 -4000 -1625 +750 +2125 +3500 - -41% -10% +21% - - NA (43850) 9750 12500 14875 17250 18625 20000 - -34100 -31350 -28975 -26600 -25225 -23850 - -78% -66% -54% - -Historical Diff: R*HS ---------------------- - APAC (.127) 6240 8000 9520 11040 11920 12800 - (12650) -6410 -4650 -3130 -1610 -730 +150 - -51% -25% +1% - - EMEA (.27) 10140 13000 15470 17940 19370 20800 - (27000) -16860 -14000 -11530 -9060 -7630 -6200 - -62% -43% -23% - - LATAM (.165) 6240 8000 9520 11040 11920 12800 - (16500) -10260 -8500 -6980 -5460 -4580 -3700 - -62% -42% -22% - - NA (.438) 16380 21000 24990 28980 31290 33600 - (43850) -27470 -22850 -18860 -14870 -12560 -10250 - -63% -43% -23% - -=============================================================================== -Notes -=============================================================================== - -19:33:36 #info Allocation of regional portion of budget over last -three years roughly APAC 16%, EMEA 26%, LATAM 16%, NA 42%. This is nominal, -not money actually spent. FY17 and future budgets not necessarily based on -this number. - - -Big Number ----------- - FY14 TOTAL 195,000 - FY15 TOTAL 195,000 - FY16 TOTAL 195,000 - FY17 TOTAL 195,000 - -Historical Percentages ----------------------- - APAC 16% - EMEA 26% - LATAM 16% - NA 42% - -Historical Allocated Numbers (FY15 + FY16) ------------------------------------------- - Region w/FE - APAC 12650 (222650) - Q1: 2900 - Q2: 10750 - Q3: 3000 - Q4: 6000 - FE: 10000 - - EMEA 27000 (102000) - Q1: 12000 - Q2: 80000 - Q3: 5000 - Q4: 5000 - FE: 75000 - - LATAM 16500 (26500) - Q1: 6000 - Q2: 3000 - Q3: 3750 - Q4: 3750 - FE: 10000 - - NA 43850 (43850) - Q1: 7850 - Q2: 15000 - Q3: 7000 - Q4: 14000 - - - -Final Reported FY16 -------------------- - Planned Adjusted Actual -APAC ??? ??? ??? -EMEA 35,670 31,746 29,014 -LATAM ??? ??? ??? -NA ??? ??? ??? diff --git a/FY17/adjustedannualbudgets/emea/FY17_EMEA_Adjusted_Budget.ods b/FY17/adjustedannualbudgets/emea/FY17_EMEA_Adjusted_Budget.ods deleted file mode 100644 index 4201472..0000000 Binary files a/FY17/adjustedannualbudgets/emea/FY17_EMEA_Adjusted_Budget.ods and /dev/null differ diff --git a/FY17/archive/Q1/apac/Q1-2017.ods b/FY17/archive/Q1/apac/Q1-2017.ods new file mode 100644 index 0000000..fb7f099 Binary files /dev/null and b/FY17/archive/Q1/apac/Q1-2017.ods differ diff --git a/FY17/archive/Q1/apac/apacq1report.txt b/FY17/archive/Q1/apac/apacq1report.txt new file mode 100644 index 0000000..8ff95cf --- /dev/null +++ b/FY17/archive/Q1/apac/apacq1report.txt @@ -0,0 +1 @@ +TODO: izhar diff --git a/FY17/archive/Q1/emea/EMEA-Q1-Budget-Report.ods b/FY17/archive/Q1/emea/EMEA-Q1-Budget-Report.ods new file mode 100644 index 0000000..a6064c8 Binary files /dev/null and b/FY17/archive/Q1/emea/EMEA-Q1-Budget-Report.ods differ diff --git a/FY17/archive/Q1/latam/latamq1report.txt b/FY17/archive/Q1/latam/latamq1report.txt new file mode 100644 index 0000000..974297b --- /dev/null +++ b/FY17/archive/Q1/latam/latamq1report.txt @@ -0,0 +1 @@ +TODO: potty diff --git a/FY17/archive/Q1/na/Fedora_FAmNA_Budget_FY2017.xlsx b/FY17/archive/Q1/na/Fedora_FAmNA_Budget_FY2017.xlsx new file mode 100644 index 0000000..ca134c8 Binary files /dev/null and b/FY17/archive/Q1/na/Fedora_FAmNA_Budget_FY2017.xlsx differ diff --git a/FY17/archive/Q1/na/naq1report.txt b/FY17/archive/Q1/na/naq1report.txt new file mode 100644 index 0000000..515f50d --- /dev/null +++ b/FY17/archive/Q1/na/naq1report.txt @@ -0,0 +1 @@ +TODO: award3535 diff --git a/FY17/archive/Q1/quarterlyreporttemplate.ods b/FY17/archive/Q1/quarterlyreporttemplate.ods new file mode 100644 index 0000000..2cbe50f Binary files /dev/null and b/FY17/archive/Q1/quarterlyreporttemplate.ods differ diff --git a/FY17/archive/Q2/emea/Fedora EMEA Quarterly Budget Report - Q2 FY17 - Report.pdf b/FY17/archive/Q2/emea/Fedora EMEA Quarterly Budget Report - Q2 FY17 - Report.pdf new file mode 100644 index 0000000..592ef9f Binary files /dev/null and b/FY17/archive/Q2/emea/Fedora EMEA Quarterly Budget Report - Q2 FY17 - Report.pdf differ diff --git a/FY17/archive/Q2/emea/Fedora EMEA Quarterly Budget Report - Q2 FY17.ods b/FY17/archive/Q2/emea/Fedora EMEA Quarterly Budget Report - Q2 FY17.ods new file mode 100644 index 0000000..cdac71d Binary files /dev/null and b/FY17/archive/Q2/emea/Fedora EMEA Quarterly Budget Report - Q2 FY17.ods differ diff --git a/FY17/archive/adjustedannualbudgets/council/council.2016-04-11-18.00.log.html b/FY17/archive/adjustedannualbudgets/council/council.2016-04-11-18.00.log.html new file mode 100644 index 0000000..f186c69 --- /dev/null +++ b/FY17/archive/adjustedannualbudgets/council/council.2016-04-11-18.00.log.html @@ -0,0 +1,474 @@ + + + + +#fedora-meeting log + + + + +
18:00:15 <mattdm> #startmeeting Council (2016-04-11)
+18:00:15 <zodbot> Meeting started Mon Apr 11 18:00:15 2016 UTC.  The chair is mattdm. Information about MeetBot at http://wiki.debian.org/MeetBot.
+18:00:15 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
+18:00:15 <zodbot> The meeting name has been set to 'council_(2016-04-11)'
+18:00:17 <mattdm> #meetingname council
+18:00:17 <zodbot> The meeting name has been set to 'council'
+18:00:19 <mattdm> #chair mattdm jkurik jwb cwickert langdon decause robyduck tatica
+18:00:19 <zodbot> Current chairs: cwickert decause jkurik jwb langdon mattdm robyduck tatica
+18:00:21 <mattdm> #topic Introductions, Welcomes
+18:00:25 <langdon> .hello langdon
+18:00:26 <zodbot> langdon: langdon 'Langdon White' <langdon@fishjump.com>
+18:00:31 <jwb> hi
+18:00:32 <jkurik> .hello jkurik
+18:00:34 <zodbot> jkurik: jkurik 'Jan Kurik' <jkurik@redhat.com>
+18:00:42 <mattdm> .hello mattdm
+18:00:43 <zodbot> mattdm: mattdm 'Matthew Miller' <mattdm@mattdm.org>
+18:00:44 <decause> .hello decause
+18:00:44 <robyduck> .fas robyduck
+18:00:45 <zodbot> decause: decause 'Remy DeCausemaker' <decause@redhat.com>
+18:00:48 <cwickert> .hello cwickert
+18:00:48 <zodbot> robyduck: robyduck 'Robert Mayr' <robyduck@gmail.com>
+18:00:51 <zodbot> cwickert: cwickert 'Christoph Wickert' <christoph.wickert@gmail.com>
+18:01:23 <mattdm> whoo, good crowd today :)
+18:02:23 <mattdm> well, let's get right to it...
+18:02:40 <mattdm> #topic Initial FY17 budget meeting
+18:02:47 * decause drumrolls
+18:03:12 <mattdm> ideally, this wouldn't be "initial" -- the initial meeting really should have been in September
+18:03:18 <mattdm> but we're getting a new process started
+18:03:20 <mattdm> see
+18:03:24 <mattdm> #link https://budget.fedoraproject.org/
+18:03:30 <mattdm> #info new budget process site
+18:03:48 <mattdm> we're currently at the "adjustment/allocation" stage
+18:04:01 <mattdm> having gotten the community budget numbers from our sponsor
+18:04:16 <mattdm> decause, you wanna take this?
+18:04:27 <decause> mattdm: the big number, yeah?
+18:04:31 <mattdm> yeah
+18:04:43 <decause> #topic The Big Number
+18:04:52 <mattdm> #link http://lists.fedoraproject.org/archives/list/council-discuss@lists.fedoraproject.org/message/TML72C4572A6FVK6UJDFCMUN56T4PKJ4/
+18:05:04 <decause> #info The Big Number this year, is the same as last year, at $195,000
+18:05:05 <mattdm> #info email from mattdm summarizing things from this morning
+18:05:34 <decause> the difference this year, is how we discuss and prioritize making that number stretch
+18:06:01 <mattdm> #info That covers events, swag, Fedora conferences, activity days, and any other community spending
+18:06:20 <decause> *everything*
+18:06:24 <mattdm> #info Does not include infrastructure, hardware, etc
+18:06:42 <decause> meant to put one * on that 'everything' ;)
+18:07:23 <decause> we should just take a moment to make sure everyone here has read mattdm's email to the council list today
+18:07:29 * mattdm quiets up and lets decause talk
+18:07:45 <mattdm> (although if anything was unclear, I can help explain)
+18:07:45 <decause> as it condenses all the history into one succinct place
+18:08:22 <decause> I've spent the past few weeks shaking the trees to get our regional information into one place, which mattdm has done a great job of compiling
+18:08:31 <decause> our new budget site
+18:08:40 <decause> #link http://budget.fedoraproject.org
+18:09:10 <decause> is where we'll announce the regional allocations
+18:09:29 <decause> as well as the central budget for Fedora events
+18:10:27 <decause> Regions are still responsible for crunching/reporting their own numbers, but they have additional support now via the Community Blog and CommOps team to help publicize and socialize their events
+18:10:40 <decause> as well as help with gathering some impact metrics for such activity
+18:11:24 <decause> a place where we're gathering all the budget information is the new fedora-budget repository hosted on pagure
+18:11:32 <decause> #link http://pagure.io/fedora-budget
+18:12:23 <decause> by treating the budget process the same way we treat other infrastructure within fedora, and use the same tools to wrangle it, we can make it much easier to distribute the load of reporting
+18:13:08 <decause> right now, there are directories for each fiscal year, and each region, but the data we have from year's past has not been fully committed to the repository
+18:13:40 <decause> which is a "nice-to-have" for historical reasons, but not entirely necessary for today's talks
+18:14:57 <decause> I'm going to be working with the delegates from each region to standardize on a reporting mechanism (spreadsheet) that we use on a quarterly basis to report on action and impact
+18:15:08 <decause> and then updating budget.fp.o accordingly with the numbers
+18:16:01 <decause> I am accountable for getting the numbers into "production" but regions are accountable for delivering their numbers to the repository
+18:16:07 <jwb> i have a question
+18:16:15 <decause> yes, now is a good time for questions
+18:16:31 <jwb> why would you use a spreadsheet and then manually transfer data to the repo, instead of just taking pull requests to the repo?
+18:17:19 <decause> preferably, all the data would come in as pull-requests; the same way we collaborate on other kinds of infrastructure
+18:17:33 <decause> currently, the most common way budget has been reported is via spreadsheet
+18:17:35 <cwickert> ?
+18:18:07 <decause> I'm more interested in having a central place where all the data can be seen, and working out the standard way it is reported across regions
+18:18:10 <decause> which we haven't tried before
+18:18:12 <decause> cwickert:
+18:18:27 <MarkDude> Standardizing regional things whilst we have special rules for India seems dubious at best. It sets the region in a non parity state, IMO. It'1 2016, can we still have "special rules for the brown folks in India?" (This is in context of parity of regions, reporting, making budgets, etc.)
+18:18:41 <jwb> a spreadsheet -> repo method seems like a lot of manual work that is error prone
+18:18:51 <cwickert> I wonder why there is this strong focus on tooling because I don't think we had a tooling problem in the past. AFAICS the problem was always manpower and I'm afraid with the different roles this will get worse.
+18:18:55 <mattdm> MarkDude: hold that for a second plase
+18:18:58 <MarkDude> And fed msg bus could help with at least parts of this. It's untapped to fully help us do things smoothly
+18:19:11 <cwickert> But this is just a side-question and has nothing to do with the actual numbers
+18:19:23 <MarkDude> No prob FPL :)
+18:19:44 <decause> cwickert: the problem before has been cycles, agreed
+18:20:18 <decause> the roles make sure that we know who is responsible for what
+18:20:35 <cwickert> decause: did you manage to fill all vacant roles?
+18:20:40 <decause> rather than all the ambassadors unofficially picking somone to carry the load of reporting expenses, we officially pick a person,a nd support them
+18:20:41 <mattdm> the main problem with tooling I saw was having everything in one place. even with the wiki before, it's really inconsistant
+18:21:45 <decause> cwickert: I have not gotten responses from all regions yet, no, but in light of there being actual numbers at stake, I expect an elevated level of attention and interest
+18:22:37 <cwickert> decause: ok, let's see. ignore my question and let's move on to crunching numbers then
+18:22:51 <decause> designating roles and having accountability is how we do #action items in meetings, and it is something I think will improve follow-through. we'll see how the experiment ends up :)
+18:23:06 <decause> cwickert: nod nod nod
+18:23:23 <decause> any other questions on process before we go forward with numbers?
+18:23:30 <mattdm> tools are the easy part; figuring out what to do with limited budget is much harder :-/
+18:23:36 <decause> mattdm: agreed.
+18:24:16 <MarkDude> mattdm: +1
+18:24:54 <decause> briefly, to markdude's question: The is no special policy for India. India is part of APAC, and their regional budget is what the scope of this meeting is about.
+18:25:13 <decause> other questions?
+18:25:14 <decause> going once
+18:25:16 <decause> going twice
+18:25:17 <decause> going thrice
+18:25:28 <decause> #topic Crunching the Numbers
+18:25:49 <decause> So, I think mattdm has characterized the crunch nicely in the update to council list
+18:26:02 <decause> and I would add some flavor
+18:26:57 <decause> keeping the budget at historical levels has been due to our ability to report on what we've spent, and how that expenditure creates value for the project.
+18:27:05 <decause> we want to grow
+18:27:09 <MarkDude> Process is same to join all parts of Fedora, minus rules for India. By definition special rules, tho Im dropping it due to not the time. Shutting up :)
+18:27:12 <decause> and growing means growing pains
+18:27:36 <decause> this year, we've already seen an increased demand for Fedora Events (FADs) that is up from historical levels
+18:27:50 <decause> so, we're probably not going to have enough budget to do all the thigns we want to do
+18:28:04 <decause> the important part to remember, is that a budget cycle is a full year
+18:28:14 <decause> and if we want to impact the budget, it takes months to do it
+18:28:36 <mattdm> (although note on FADs: it's not necessarily up hugely from earlier, just up from what the flat budget is based on, which leads to a dissonance)
+18:28:38 <decause> so this year, is going to be all about getting our metrics and numbers square, so that we can tell the story *next* year for increasing and growing our budget
+18:29:14 <mattdm> decause++
+18:29:22 <cwickert> !
+18:29:29 <decause> cwickert: you can just chime in ;)
+18:29:38 <cwickert> We've always had this problem and the only way to improve is with proper reporting
+18:29:45 <decause> 100% agreed
+18:29:46 <decause> yes
+18:29:49 <cprofitt> +1
+18:29:54 <cwickert> that also means: We (at least in EMEA) requested more then we got
+18:30:08 <cwickert> and at that point we just had to do a haircut
+18:30:17 <cwickert> trim all events by x percent
+18:30:25 <cwickert> and even skip some small ones
+18:30:26 <MarkDude> If we dont spend the money in a cycle, we may get less. This is partly responsible for "budget issues" we had in another region years ago. Funding needs change. Based on many things. I did NOT want to do release parties for a while, partly due to the Distro being not too usable. Following consistency model I should have had events, so I can do them now?
+18:31:02 <cwickert> I don't think this should be a problem, we just need to pay a little attention. But I'm all for making the FAds happen, even if this means spending less on other events
+18:31:20 <cprofitt> spending money to ensure the ability to spend it in the future is a bad way of running the ship.
+18:31:28 <robyduck> cwickert: +1
+18:32:10 <cprofitt> +1 cwickert
+18:32:27 <MarkDude> RH has the money, we made the product. Some regions choose not to do extra events due to monies. Things vary.
+18:32:30 <MarkDude> cprofitt: +1
+18:32:31 <decause> cwickert: and it is my hope that by improving the connection between ambassadors and commops, we don't ahve to leave event owners to do the reporting entirely on their own
+18:33:14 <decause> cprofitt: yes, budget is odd in this way, here or in other places. What we have not done before is keeping track of the "hair" that we left on the floor after trimming
+18:33:42 <mattdm> cprofitt: Agreed. We need to be able to show the impact of money spent.
+18:33:49 <decause> if there is an event/opportunity that we are *not* taking, we should record that opportunity cost somewhere so that next year, when we propose the budget, we can make the case for increase.
+18:34:08 <mattdm> MarkDude: Well, keep in mind that this is far from all of the money spent on Fedora
+18:34:29 <MarkDude> False choice, we can do FADs AND local events. We can do more, and more importantly not lower our high standards in process. Having a 20% reserve is a decent way to allow for extras, yet still gauge.
+18:34:54 <cprofitt> decause: yes, if we can track those 'not done' this year items that may come back that would be good. Budget is always a bit difficult... one idea I like is having a small percentage of the budget that is allocated towards 'initiatives' - spefically trying new things.
+18:35:02 <cwickert> I think it comes down to: How can we make sure we make the FADs happen? I see two options: 1) allocate a good chunk of the budget and cut the regional events on the other hand. 2) use the regional budgets to sponsor FAD attendees. While 2 is more flexible, 1 is cleaner and will (hopefully) help us getting more money for FADs next year.
+18:35:05 <MarkDude> Yes FPL. Ty for letting me speak here to bring these points up. I'll lurk now, and let you folks do your awesomeness. :)
+18:35:36 <cprofitt> mattdm: yes, we need to show the imapct.
+18:35:56 <cprofitt> +1 decause on recording opportunities missed.
+18:36:01 <decause> MarkDude: increasing/reserves anything that is dealing with increasing the "big number" is out of scope for today's discussion. It is important that we have those conversations some where, but the time for adjustment has passed. We have to spend the numbers we have.
+18:36:38 <cprofitt> decause++ budget page looks good.
+18:36:41 <decause> cwickert: this is helpful
+18:37:32 <mattdm> So... what are our next steps here?
+18:37:43 <decause> mattdm: right
+18:37:57 <mattdm> I'd _really_ like to see something like https://pagure.io/fedora-budget/raw/master/f/FY17/proposedannualbudgets/emea/FedoraEMEABudgetFY2017.ods from LATAM, NA, and APAC
+18:38:52 <jwb> perhaps we can take the overall budget, allocate money for flock, FUDCons, and FADs, and then divide the remaining amount among the regions once we have the budgets from the regional coordianators?
+18:38:54 <decause> I have a very simple task ahead: update the budget numbers here: https://budget.fedoraproject.org/#budgetnumbers
+18:38:59 <jwb> er, coordinators
+18:39:39 <cprofitt> mattdm: would you want that spreadsheet to containe impact data or just expenses?
+18:39:40 <decause> jwb: that sounds about right, yes
+18:39:49 <mattdm> cprofitt: awesome question :)
+18:40:01 <decause> cprofitt: the "impact" data is part of the event reportin that we're going to track going forward
+18:40:09 <cprofitt> jwb +1 that sounds like a good way to do it.
+18:40:11 <mattdm> I was thinking maybe each thing have a link to an event page, which would contain that?
+18:40:26 <mattdm> cprofitt: but if you have a better idea I'd love to hear it
+18:40:47 <decause> I don't think we can "ex post facto" reporting standards onto last year, but we can do some archeology to dig that up for some events
+18:40:55 <decause> mattdm: +1
+18:41:08 <cprofitt> mattdm: hmm... I know that the BrickHack event we had attendee badges...
+18:41:13 <mattdm> FWIW, the breakdown in the previous regional budgets (considering regional budgets alone) is about: 16% APAC, 26% EMEA, 16% LATAM, 42% NA
+18:41:30 <decause> and going forward, the event reports, even if they are hosted on personal blogs, will be aggregated on the commblug
+18:41:33 <decause> commblog
+18:41:39 <decause> so that we have them all in one place later
+18:41:54 <decause> and there are some bullet points that get addressed in each post
+18:41:59 * decause digs up link for impact metrics:
+18:42:02 <mattdm> cprofitt: fedora-badges badges? that's definitely useful, since we can do analytics on that later.
+18:42:11 <jwb> mattdm: i'm not sure that breakdown holds any longer to be honest
+18:42:15 <cprofitt> the event page would help with 'expected attendance', 'actual attendance'... but measuring impact might need to have multiple inputs. Different events like converting to Python 3 might have better metrics based on commits.
+18:42:20 <decause> #link https://fedoraproject.org/wiki/Budget.next#Reimbursement
+18:42:33 <mattdm> jwb Yeah, that's just the historical allocations
+18:42:43 <mattdm> (also not including FUDCons/Flock)
+18:42:48 <cprofitt> we likely need to take a closer look at all the possible sources of metrics based on event types... and help organizers of future events be aware that those tools exist.
+18:42:58 <jwb> mattdm: i mention it because i think people need to be aware that historical allocations are not likely to match to this year's allocations
+18:43:23 <decause> cprofitt: yes, we have a script that is a PoC on tracking fedmsg data in the fedora-stats-tools repo
+18:43:49 <cprofitt> decause: yes, going back might not be worth the effort. Looking forward we just have to make sure we take a look at how to measure an event... ensure we give as much support to the person coordinating the event as possible.
+18:44:15 <mattdm> cprofitt++
+18:44:15 <zodbot> mattdm: Karma for cprofitt changed to 9 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
+18:44:17 <decause> cprofitt: these are great discussions to have, and I'm def into it from the commops side of things for sure
+18:44:29 <decause> falls squarely within "metrics" areas
+18:44:49 <decause> jwb: yes, I think this is good to point out as well
+18:44:51 <cprofitt> decause: yeah, likley a side conversation as it is a little bit of a birdwalk for this conversations main topic...
+18:45:19 <decause> so, as a warning, I mentioned on the ambassador list that if we didn't have a proposed budget reported, that it would impact our ability to allocate budget for a region
+18:45:22 <mattdm> Council members: I want to highlight what jwb said a few minutes ago. I agree and want to make sure no one _disagrees_....
+18:45:42 <mattdm> That is: we won't use historical percentage as the baseline for regional allocation
+18:45:52 <mattdm> (It _might_ end up like that, but it might not.)
+18:46:04 <mattdm> Does anyone disagree with that?
+18:46:13 <decause> +1 history does not dictate future necesarily
+18:46:18 <cprofitt> mattdm: so we want people to agree upfront to the 'norm' for determining budget?
+18:46:32 <cprofitt> I do not disagree mattdm
+18:46:37 <mattdm> cprofitt: I'm not sure I understand that question....
+18:47:02 <decause> cprofitt: we just want to be clear that this year's numbers will not necessarily be the same as last year's numbers per region
+18:47:02 <cwickert> -1
+18:47:03 <cprofitt> we want peole to agree with the method of allocating funds -- ahead of allocation..
+18:47:22 <decause> cprofitt: hang back for a sec, this is a big question
+18:47:34 <decause> cwickert: ?
+18:47:34 <cprofitt> k
+18:47:36 <jwb> cwickert: you disagree that historical budget allocation is not how we're going to allocate this year's budget?
+18:47:45 <cwickert> I think historical allocations are the only thing we can actually rely on
+18:48:02 <decause> meh
+18:48:14 <cwickert> and if we don't, we will punish the regions who did good reporting in the past
+18:48:21 <langdon> this paticular year? or future years?
+18:48:27 <jwb> cwickert: i think doing so is not responsible.  the 42% allocation to NA seems excessive given the growth of the contributor bases in the other regions
+18:49:19 <cwickert> jwb: good point, but I don't see how an increase in user base translates into numbers
+18:49:21 <jkurik> if we do not use the historical allocations what will be the way how the budget is distributed ?
+18:49:32 <decause> cwickert: contributor, not user
+18:49:33 <langdon> so.. i definitely agree that this year might be weird.. but why wouldn't we use historical in future years?
+18:49:56 <jwb> jkurik: perhaps we can look at the submitted budget and attempt to gauge impact of the events and activites
+18:50:19 <cprofitt> We want to, as a group, agree on a method for determining funding. Keeping in mind that this may, or may not, reflect historical spending. The method of allocation is meant to maximize impact and regional spending may flucuate based on multiple factors. What I am having issues grasping is what the other method is.
+18:50:28 <robyduck> we shoud at least keep history in mind when it comes to decide whether cut one or another region. Not relying totally on it, but neither forget it
+18:50:40 <mattdm> robyduck: yeah, well put
+18:50:41 <decause> Question have we ever had a standard "percentage" for each region?
+18:50:45 <jwb> robyduck: yes that is certainly fair
+18:50:49 <decause> I don't think we have
+18:50:50 <mattdm> also cprofitt, well put :)
+18:50:56 <jwb> decause: mattdm listed them above
+18:51:03 <langdon> also .. what does "historical" mean here? do you mean "na always gets 42%" or do you mean "na spent 42% last year and had xyz growth, we shoudl give them more"?
+18:51:14 <decause> jwb: for every year?
+18:51:19 <mattdm> I was *just* looking at the nominal allocations
+18:51:25 <mattdm> not even actual-spent money
+18:51:35 <cprofitt> perhaps having a two part system.... part of the budget is historical, with a portion being allocated based on potential impact.
+18:51:44 <jwb> decause: yes?
+18:52:04 <decause> ok, good to know.
+18:52:18 <cwickert> ok, let me rephrase what I wrote earlier: we need to give all regions a chance. They are to submit a budget, that's the process we always followed. but when we need to decide on the submitted budgets, then we need to have history in mind to see how realistic a request is. We had this 3 or 4 years with the APAC regions: They were very enthusiastic and requested a lot of money, but did not spend much in the end.
+18:52:28 <jwb> look, the fact is that we've had a flat budget for the past 5 years but we've been doing more.  if we cannot sufficiently explain why that budget needs to go up, through both accurate _planning_ and accurate _reporting_, it won't go up
+18:52:50 <decause> jwb: this is def the reality
+18:52:52 <decause> yes
+18:53:03 <cprofitt> example: 70% is allocated by historical and 30% is allocated by potential impact. I agree with cwickert that we need to ensure all regions know we are doing this and have a chance to get their reporting in place.
+18:53:32 <robyduck> jwb++
+18:53:32 <mattdm> cwickert: I can agree with that.
+18:53:34 <jwb> cwickert: yeah.  unfortunately, enthusiasm does not trump actually doing things.
+18:53:41 <langdon> cprofitt, that proposal does not account for "poor planning" ... aka asked for 10 spent 5
+18:54:04 <decause> cwickert: I think you're trying to future-proof against the right things, yes
+18:54:38 <cprofitt> langdon: it was meant to be a rough proposal. I agree we need to adjust based on actually spent money not proposed, but unspent.
+18:55:01 <mattdm> I'm definitely suffering from lack of standarization of process in the past
+18:55:21 <decause> mattdm: agreed. aggregating this history has been challenging
+18:55:37 <cwickert> cprofitt: not sure if we can do a percentage, but more something along the lines: Let them request money, look at the requests when they come in and then say: "Ok, region X has a tendency to under-spend, so we cut their budget by 20%, while region Z does very good reporting and therefor we cut their budget by only 5%. That's what we did in FAmSCo all the years.
+18:55:54 <cprofitt> mattdm: agreed we need to standardize and let everyone know what the process will be.
+18:56:05 <cprofitt> cwickert: that works for me.
+18:56:06 <cwickert> s/reporting/reporting+budgeting
+18:56:35 <cprofitt> we can also work with regions that have had inconsistent reporting / planning and help them improve.
+18:56:38 <cwickert> decause: we don't have numbers from the regions yet, right?
+18:56:57 <mattdm> cwickert: yeah, by not following history, I don't mean throwing all that out.
+18:56:59 <jwb> cwickert: i can agree with that somewhat.  my main point is that past allocation does not ensure future allocation.  it has to be somewhat results driven, based on whatever we consider "results" to be (e.g. perceived or actual impact, accuracy, etc)
+18:57:04 <dzho> one sees in federal research grant funding decisions the use of proposals vetted by peer review, the results of which are consulted by ultimate decision makers. It involves a lot of poorly rewarded work by those doing the review, but I wonder if there's anything useful from that model?
+18:57:11 <decause> cwickert: we have EMEA numbers, and some LATAM numbers, some rought NA numbers, but I need APAC numbers most
+18:57:20 <cprofitt> +1 jwb
+18:57:39 <mattdm> as far as know only EMEA and APAC have planned/actual budget numbers for FY15 and FY14
+18:57:39 <cwickert> jwb: sure, we totally agree and I'm all for enabling new contributors in other regions because this is where we can grow
+18:57:56 <jwb> dzho: i think that is essentially what we are proposing here, yes.  the peers in this case are the council and the regions
+18:58:10 <cwickert> decause: we have two FAmSCo members in APAC, let me talk to them on Wednesday
+18:58:19 <decause> cwickert: awesome, thank you
+18:58:45 <decause> dzho: yes, what jwb said
+18:58:57 * dzho nods, continues lurking
+18:59:43 <decause> so, from what it looks like, we want the future allocations to be *informed* by historical percentages, but adjusted by results and ahereance to the process
+19:00:00 <langdon> decause, and actuals
+19:00:10 <mattdm> okay, so, here we are an hour in. We should be looking at next steps :)
+19:00:21 <mattdm> I definitely think we should continue next Monday....
+19:00:27 <cprofitt> decause: yes.
+19:00:35 <jwb> step 1 was suggested.  which is basically, put in the values for flock, FADs, and fudcons
+19:00:35 <cprofitt> +1 mattdm
+19:00:36 <decause> mattdm: I believe we allocated an extra hour today
+19:00:37 <mattdm> but we should be looking at concerete decisions at that point.
+19:00:42 <decause> I did at least on fedocal last time
+19:01:02 <mattdm> jwb: I did that in a spreadsheet right before the meeting, which I then failed to save properly :)
+19:01:08 <jwb> decause: if you've imported the ical from fedocal, it does not update
+19:01:26 <mattdm> An open question is whether we're going to put the proposed $17k into the APAC FAD
+19:01:34 <decause> jwb: I think I only added it statically last week, which we cancelled, and then didn't double-blcok this week
+19:01:37 <decause> that is my bad
+19:01:48 <jwb> decause: er, update in whatever calendar you imported it to.  so i'm not sure anyone noticed if you changed it even if you did
+19:02:02 <jwb> mattdm: i mean in the budget.fp.org site
+19:02:06 <decause> jwb: I'll post those types of updates to the council-discuss next time too, just in case
+19:02:15 <mattdm> jwb: oh, good call.
+19:02:19 <jwb> people really love spreadsheets when they are just extra manual steps..
+19:02:31 <decause> jwb: the formulas are nice
+19:02:40 <decause> I prefer csv myself, it is portable and human readable
+19:02:55 <mattdm> spreadsheets suck. however, they're really convenient to hack on without knowing what you're really doing :)
+19:03:08 <decause> aspirationally, I'd love ot paint a picture of what budget reporting could be like :P
+19:03:18 <langdon> i heard jwb propose creating a taiga card for autouploading
+19:03:54 <nb> 17k for a FAD?
+19:03:56 <jwb> the council doesn't use taiga.  it could though, and i'd probably be way happier than using trac
+19:04:02 * nb thought they were generally 5k
+19:04:06 <mattdm> nb: er, sorry. FUDCon
+19:04:06 <nb> or are you talking about fudcon?
+19:04:08 <nb> oh ok
+19:04:18 <mattdm> which is also quite high
+19:04:18 <decause> If we get more information from the regions as we go forward, I'm ok with adjusting, but I've given notice on the lists, and reached out individually too (as cwickert will also do this week with apac)
+19:04:28 <mattdm> but basically what we approved for LATAM
+19:05:05 <cwickert> 17k for a FAD?
+19:05:10 <cwickert> where does this come from?
+19:05:22 <mattdm> cwickert: from me mistyping "FUDCon" :)
+19:05:23 <cwickert> ah, sorry, FUDCon
+19:05:31 <cwickert> sorry, slow reading the backlog
+19:06:41 <mattdm> decause: you wanna #action yourself for putting up a proposal on the budget.fpo page?
+19:07:28 <decause> #action decause post a proposed budget scenario to council list, and upload the document (spreadsheet or otherwise) to the pagure.io repo
+19:07:46 <mattdm> decause++
+19:07:55 <decause> mattdm: what I need to know from council is the preferred contours of the scenario
+19:07:58 <decause> i will crunch a few of them
+19:08:12 <mattdm> decause yeah, I was just gonna say a few possibilities would be nice
+19:08:18 <decause> but mostly I have to make 7 numbers happen:
+19:08:23 <decause> the first one is done:
+19:08:28 <decause> Total: 195,000
+19:08:56 <decause> I think cwickert original observation about rolling the FUDCon funding into 'council' instead of 'each region' was a keen one
+19:09:20 <MarkDude> +1
+19:09:28 <cwickert> decause: actually, premiere events have always been handled globally
+19:09:28 <decause> so I will take the proposed FUDCon and FLock (and pending FAD requests) and roll those into council
+19:09:38 <nb> cwickert++
+19:09:38 <zodbot> nb: Karma for cwickert changed to 7 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
+19:10:03 <decause> i will follow up with OSAS to find out if we got dedicated OSAS funding for Outreachy
+19:10:11 <decause> #action decause follow up with OSAS to find out if we got dedicated OSAS funding for Outreachy
+19:10:16 <cwickert> decause: I think the first step is premiere events vs. regional budget and then we can further distribute the regional budget.
+19:10:26 <mattdm> cwickert: yeah, except for in the FY14 budget email, where they were divvyed up to the regions even though then later handled centrally
+19:10:27 <decause> otherwise, I'd like to request that we allocate one slot per quarter as one scenario
+19:10:39 <decause> ideally 2 (tech and non-tech)
+19:10:44 <decause> that'll be one scenario
+19:10:59 <decause> but the overarching scenario, of the regional percentages
+19:11:23 <decause> those should hold as a "base-line" then, but will not be 100% the same as history
+19:11:28 <cwickert> and we could as well say: premiere events = council, regional budget = FAmSCo. That's what we did in the past. It wasn't perfect (for technical events in a region such as FADs), but it worked.
+19:11:50 <robyduck> yup
+19:11:52 <mattdm> I'd like to see regional planning FADs budgeted in, and as line items for the regions
+19:12:26 <decause> #info regional budget planning FADs for each region, as part of the region's budget
+19:12:27 <cwickert> mattdm: if we fly the design team to the US for a FAD, how is that regional?
+19:12:40 <mattdm> there's some disparity in the docs on FADs about whether or not they regional events in general
+19:12:48 <decause> FAD is a centrally organized, not regionally organized event
+19:12:50 <cwickert> decause: I disagree with the #info
+19:12:53 <cwickert> right
+19:13:08 <mattdm> cwickert: but in what I meant above, I meant specifically region-focused planning FADs
+19:13:10 <nb> so we all should have a regional planning FAD now?
+19:13:19 <decause> cwickert: mattdm is talking about budte planning FADs, like what EMEA has been doing for years
+19:13:31 <decause> s/budte/budget
+19:13:36 * nb not opposed
+19:13:47 <mattdm> nb I think it's a good model. It makes sense to colocate it with other events (Flock, FUDCons) when possible
+19:13:51 <cwickert> mattdm, decause: that should be one FAD for each region, so easy to budget.
+19:14:00 <nb> mattdm, yeah
+19:14:03 <cwickert> s/budget/project
+19:14:03 <decause> nb: yes, we should, so that there are *always* numbers for the council to consider in the future, unlike today ;)
+19:14:21 <mattdm> cwickert: yeah, and that's why I was suggesting putting them as line items in the regions
+19:14:29 <nb> decause, mattdm good idea
+19:14:32 <nb> we did that a few years ago in NA
+19:14:34 <cwickert> mattdm: makes sense
+19:14:52 <nb> Blacksburg maybe, we had the FAD the day before fudcon, then more people got to stay for fudcon also
+19:15:01 <decause> mattdm: standard $5K FAD limit?
+19:15:03 <mattdm> nb exactly, yeah.
+19:15:10 <cwickert> mattdm: note we might not even need a planing FAD in some regions if they have FLOCK or a FUDCon
+19:15:10 <mattdm> decause: up in the air, I think
+19:15:19 <cwickert> decause: yes, 5k should be ok everywhere
+19:15:20 * mattdm squints at that bottom line
+19:15:26 <decause> mattdm: agreed. I can try to crunch a high and low scenario then
+19:15:34 * decause signs up for more work
+19:15:37 <decause> :P
+19:15:38 <mattdm> decause++
+19:15:39 <nb> cwickert, true, depending on how many people get funded for flock/fudcon otherwise
+19:15:52 * nb sees it more as "paying for more people to go to Flock, given that there is a planning session at flock"
+19:15:54 <mattdm> cwickert: I'd rather say "we have the planning FAD at Flock/FUDCon"
+19:15:54 <nb> or something like that
+19:15:59 <nb> mattdm++
+19:15:59 <zodbot> nb: Karma for mattdm changed to 12 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
+19:16:01 <decause> the good news is, Flock planning has given their number at $75K this year
+19:16:09 <cwickert> mattdm: that's what I meant
+19:16:09 <decause> same as last year
+19:16:18 <mattdm> cwickert: cool
+19:16:27 <decause> so, that is a nice 'not-dotted-line' item
+19:16:52 <jwb> that's an interesting way to put it :)
+19:17:10 <cwickert> decause: prices are highter are EMEA and NA, but travel is more expensive in APAC and LATAM. So 5k for a planning FAD should do everywhere and if it is co-located with another event, we just skip it in the budget.
+19:17:29 <robyduck> to avoid confusion, why don't we put those planning FAD events in the reginal budget and handle the other FADs globally? This way every region also can manage their budget better, doing the planing with other events like fudcon or flock.
+19:17:42 <robyduck> just a thought
+19:17:48 <jwb> cwickert: no... we show the that 5k was allocated to bring more people to Flock/FUDCon
+19:17:53 <jwb> we don't "skip" things any more
+19:17:56 <mattdm> robyduck: I think that's what we're saying
+19:18:08 <decause> robyduck: yeah, what mattdm said
+19:18:10 <nb> jwb++
+19:18:10 <zodbot> nb: Karma for jwboyer changed to 9 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
+19:18:13 <robyduck> we can name them differently
+19:18:30 <robyduck> but that's a detail
+19:18:33 <cwickert> jwb: ok, if you put it that way.
+19:19:02 <decause> we're going to be settling on a standard format for reporting these things (my vote is based off the very decent EMEA sheet)
+19:19:06 <mattdm> I am all for finding more ways to get involved, active people on the ground at Flock that don't involve them needing to give a talk
+19:19:22 <decause> #link https://docs.google.com/spreadsheets/d/11nWHrooCwoiWqGx4iEUnITQAWwQrQ6_2ito8GUtBk_g/edit#gid=0
+19:19:30 <nb> mattdm, i agree.  I mainly only submitted a talk so that I could hopefully get funding
+19:19:35 <robyduck> mattdm: would be nice
+19:19:47 * nb wnats to go to plan stuff for next year in NA
+19:19:54 <mattdm> that's probably a conversation for another time, though :)
+19:19:59 <decause> agreed
+19:20:13 <decause> I'm going to be pushing my updates to the pagure.io/fedora-budget repo
+19:20:20 <decause> they'll likely be spreadsheets/csv
+19:20:28 <decause> unless jwb, you have a better suggestion?
+19:20:45 * decause is *def* open to better ideas
+19:21:07 <jwb> i suggested just updating the website with pull requests, but whatever works for the people actually doing this is what will work best
+19:21:18 <mattdm> I saw whatever works, is consistent, and puts 'em all in the same place for later
+19:21:30 <decause> jwb: the website does not get granular down to the proposed budget levels (yet)
+19:21:52 <decause> standing up the entire 'fedora-websites' repo is a bit much to just twiddle a number
+19:21:55 <decause> imho
+19:22:25 <decause> jwb: but yeah, the future /could/ look like a webhook that updates the production site based on data in fedora-budget repo
+19:22:28 <decause> ideal bridge
+19:22:31 <decause> +1 jwb
+19:22:39 * cwickert needs to run now, it's already late here. I will read the log later, but so far I'm happy with decause's approach.
+19:23:03 <decause> cwickert: thank you for your support, and I'll be sure to add council to the pagure.io members with push/pull access
+19:23:17 <mattdm> thanks cwickert!
+19:23:20 <decause> doing budget with PR's is going to be *much* better than emailing spreadsheets
+19:23:31 <cwickert> #action cwickert to discuss the budget with FAMSCo, in particular from APAC and LATAM
+19:23:58 <cwickert> ok, bye
+19:25:13 <nb> decause, we could always make it a separate repo
+19:25:25 <decause> nb: http://pagure.io/fedora-budget
+19:25:30 <decause> ok
+19:25:31 <decause> so
+19:25:40 * mattdm isn't technically leaving but is starting to have wandering-brain syndrome....
+19:25:55 <decause> what were those percentages again? I can dig for them in the logs, but it'd be nice to have some consensus on what they are
+19:26:18 <nb> decause, oh ok
+19:26:36 <decause> nb: which, btw, there is a NA folder that could *totally* use some input ;)
+19:26:41 <mattdm> decause the historical fraction?
+19:26:42 <decause> nb++
+19:26:46 <decause> mattdm: yes
+19:26:55 * decause didn't know there was one before today
+19:27:15 <mattdm> decause: roughly: APAC 16% EMEA 26% LATAM 16% NA 42%
+19:27:28 <decause> I'll have a few scenarios for everyone to discuss next week
+19:27:33 <mattdm> it's not a rule -- it's an extrapolation from FY14, FY15, FY16
+19:27:56 <decause> mattdm: acknowleged, I think we all agreed that it is more of a 'guideline' than a rule
+19:28:02 <decause> +1
+19:28:17 <decause> next week we should still do a double block though, yeah?
+19:28:35 <mattdm> decause: well, I think we shouldn't even consider it a guideline -- more, another input into the process
+19:28:44 <mattdm> decause: yeah, I think double-book is good
+19:28:55 <decause> #action decause schedule double-block council meeting for budgeting on fedocal
+19:29:06 <langdon> literally dbl? or 2h?
+19:29:14 <mattdm> 2h = dbl
+19:29:29 <mattdm> or I guess we could also get #fedora-meeting-1 :)
+19:29:33 <decause> #help Ambassadors please submit your Budget Reports, Proposals, and Delegation Selections to decause ASAP
+19:30:10 <mattdm> #info where ASAP really means "this week, because we want to decide things next week, so we can actually spend money without fear"
+19:30:39 <langdon> probably should info those fy16 allocations too, no?
+19:31:17 <mattdm> langdon: maybe?
+19:31:32 <decause> langdon: I don't think they are supposed to be 'concrete'
+19:31:50 <langdon> decause, well.. they were for fy16, right?
+19:32:21 <mattdm> more info doesn't hurt
+19:32:24 <decause> langdon: I thought mattdm said they were conglomerated from history,not just last year
+19:32:25 * mattdm composes an info
+19:32:32 <langdon> ok
+19:32:39 <decause> yeah, since mattdm crunched, he knows best
+19:33:36 <mattdm> #info Allocation of regional portion of budget over last three years roughly APAC 16%, EMEA 26%, LATAM 16%, NA 42%. This is nominal, not money actually spent. FY17 and future budgets not necessarily based on this number.
+19:33:42 <decause> mattdm: since I'm going to be travelling on Thursday, and attending all-weekend events, the sooner the better. I'd like to have the scenarios posted by Wednesday in an ideal world
+19:33:57 <decause> mattdm++
+19:34:38 <mattdm> decause: hopefully that can happen :)
+19:35:29 <decause> mattdm: :)
+19:35:35 <decause> ok
+19:35:45 <decause> I think we're all in a good place here?
+19:36:00 <jwb> yes
+19:36:04 <mattdm> Good enough. Planning to be in a great place this time next year.
+19:36:09 <mattdm> Thanks, everyone!
+19:36:27 <mattdm> (esp. decause who did the bulk of the typing!)
+19:36:30 <mattdm> #endmeeting
+ diff --git a/FY17/archive/adjustedannualbudgets/council/council.2016-04-11-18.00.log.txt b/FY17/archive/adjustedannualbudgets/council/council.2016-04-11-18.00.log.txt new file mode 100644 index 0000000..a92fffa --- /dev/null +++ b/FY17/archive/adjustedannualbudgets/council/council.2016-04-11-18.00.log.txt @@ -0,0 +1,447 @@ +18:00:15 #startmeeting Council (2016-04-11) +18:00:15 Meeting started Mon Apr 11 18:00:15 2016 UTC. The chair is mattdm. Information about MeetBot at http://wiki.debian.org/MeetBot. +18:00:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. +18:00:15 The meeting name has been set to 'council_(2016-04-11)' +18:00:17 #meetingname council +18:00:17 The meeting name has been set to 'council' +18:00:19 #chair mattdm jkurik jwb cwickert langdon decause robyduck tatica +18:00:19 Current chairs: cwickert decause jkurik jwb langdon mattdm robyduck tatica +18:00:21 #topic Introductions, Welcomes +18:00:25 .hello langdon +18:00:26 langdon: langdon 'Langdon White' +18:00:31 hi +18:00:32 .hello jkurik +18:00:34 jkurik: jkurik 'Jan Kurik' +18:00:42 .hello mattdm +18:00:43 mattdm: mattdm 'Matthew Miller' +18:00:44 .hello decause +18:00:44 .fas robyduck +18:00:45 decause: decause 'Remy DeCausemaker' +18:00:48 .hello cwickert +18:00:48 robyduck: robyduck 'Robert Mayr' +18:00:51 cwickert: cwickert 'Christoph Wickert' +18:01:23 whoo, good crowd today :) +18:02:23 well, let's get right to it... +18:02:40 #topic Initial FY17 budget meeting +18:02:47 * decause drumrolls +18:03:12 ideally, this wouldn't be "initial" -- the initial meeting really should have been in September +18:03:18 but we're getting a new process started +18:03:20 see +18:03:24 #link https://budget.fedoraproject.org/ +18:03:30 #info new budget process site +18:03:48 we're currently at the "adjustment/allocation" stage +18:04:01 having gotten the community budget numbers from our sponsor +18:04:16 decause, you wanna take this? +18:04:27 mattdm: the big number, yeah? +18:04:31 yeah +18:04:43 #topic The Big Number +18:04:52 #link http://lists.fedoraproject.org/archives/list/council-discuss@lists.fedoraproject.org/message/TML72C4572A6FVK6UJDFCMUN56T4PKJ4/ +18:05:04 #info The Big Number this year, is the same as last year, at $195,000 +18:05:05 #info email from mattdm summarizing things from this morning +18:05:34 the difference this year, is how we discuss and prioritize making that number stretch +18:06:01 #info That covers events, swag, Fedora conferences, activity days, and any other community spending +18:06:20 *everything* +18:06:24 #info Does not include infrastructure, hardware, etc +18:06:42 meant to put one * on that 'everything' ;) +18:07:23 we should just take a moment to make sure everyone here has read mattdm's email to the council list today +18:07:29 * mattdm quiets up and lets decause talk +18:07:45 (although if anything was unclear, I can help explain) +18:07:45 as it condenses all the history into one succinct place +18:08:22 I've spent the past few weeks shaking the trees to get our regional information into one place, which mattdm has done a great job of compiling +18:08:31 our new budget site +18:08:40 #link http://budget.fedoraproject.org +18:09:10 is where we'll announce the regional allocations +18:09:29 as well as the central budget for Fedora events +18:10:27 Regions are still responsible for crunching/reporting their own numbers, but they have additional support now via the Community Blog and CommOps team to help publicize and socialize their events +18:10:40 as well as help with gathering some impact metrics for such activity +18:11:24 a place where we're gathering all the budget information is the new fedora-budget repository hosted on pagure +18:11:32 #link http://pagure.io/fedora-budget +18:12:23 by treating the budget process the same way we treat other infrastructure within fedora, and use the same tools to wrangle it, we can make it much easier to distribute the load of reporting +18:13:08 right now, there are directories for each fiscal year, and each region, but the data we have from year's past has not been fully committed to the repository +18:13:40 which is a "nice-to-have" for historical reasons, but not entirely necessary for today's talks +18:14:57 I'm going to be working with the delegates from each region to standardize on a reporting mechanism (spreadsheet) that we use on a quarterly basis to report on action and impact +18:15:08 and then updating budget.fp.o accordingly with the numbers +18:16:01 I am accountable for getting the numbers into "production" but regions are accountable for delivering their numbers to the repository +18:16:07 i have a question +18:16:15 yes, now is a good time for questions +18:16:31 why would you use a spreadsheet and then manually transfer data to the repo, instead of just taking pull requests to the repo? +18:17:19 preferably, all the data would come in as pull-requests; the same way we collaborate on other kinds of infrastructure +18:17:33 currently, the most common way budget has been reported is via spreadsheet +18:17:35 ? +18:18:07 I'm more interested in having a central place where all the data can be seen, and working out the standard way it is reported across regions +18:18:10 which we haven't tried before +18:18:12 cwickert: +18:18:27 Standardizing regional things whilst we have special rules for India seems dubious at best. It sets the region in a non parity state, IMO. It'1 2016, can we still have "special rules for the brown folks in India?" (This is in context of parity of regions, reporting, making budgets, etc.) +18:18:41 a spreadsheet -> repo method seems like a lot of manual work that is error prone +18:18:51 I wonder why there is this strong focus on tooling because I don't think we had a tooling problem in the past. AFAICS the problem was always manpower and I'm afraid with the different roles this will get worse. +18:18:55 MarkDude: hold that for a second plase +18:18:58 And fed msg bus could help with at least parts of this. It's untapped to fully help us do things smoothly +18:19:11 But this is just a side-question and has nothing to do with the actual numbers +18:19:23 No prob FPL :) +18:19:44 cwickert: the problem before has been cycles, agreed +18:20:18 the roles make sure that we know who is responsible for what +18:20:35 decause: did you manage to fill all vacant roles? +18:20:40 rather than all the ambassadors unofficially picking somone to carry the load of reporting expenses, we officially pick a person,a nd support them +18:20:41 the main problem with tooling I saw was having everything in one place. even with the wiki before, it's really inconsistant +18:21:45 cwickert: I have not gotten responses from all regions yet, no, but in light of there being actual numbers at stake, I expect an elevated level of attention and interest +18:22:37 decause: ok, let's see. ignore my question and let's move on to crunching numbers then +18:22:51 designating roles and having accountability is how we do #action items in meetings, and it is something I think will improve follow-through. we'll see how the experiment ends up :) +18:23:06 cwickert: nod nod nod +18:23:23 any other questions on process before we go forward with numbers? +18:23:30 tools are the easy part; figuring out what to do with limited budget is much harder :-/ +18:23:36 mattdm: agreed. +18:24:16 mattdm: +1 +18:24:54 briefly, to markdude's question: The is no special policy for India. India is part of APAC, and their regional budget is what the scope of this meeting is about. +18:25:13 other questions? +18:25:14 going once +18:25:16 going twice +18:25:17 going thrice +18:25:28 #topic Crunching the Numbers +18:25:49 So, I think mattdm has characterized the crunch nicely in the update to council list +18:26:02 and I would add some flavor +18:26:57 keeping the budget at historical levels has been due to our ability to report on what we've spent, and how that expenditure creates value for the project. +18:27:05 we want to grow +18:27:09 Process is same to join all parts of Fedora, minus rules for India. By definition special rules, tho Im dropping it due to not the time. Shutting up :) +18:27:12 and growing means growing pains +18:27:36 this year, we've already seen an increased demand for Fedora Events (FADs) that is up from historical levels +18:27:50 so, we're probably not going to have enough budget to do all the thigns we want to do +18:28:04 the important part to remember, is that a budget cycle is a full year +18:28:14 and if we want to impact the budget, it takes months to do it +18:28:36 (although note on FADs: it's not necessarily up hugely from earlier, just up from what the flat budget is based on, which leads to a dissonance) +18:28:38 so this year, is going to be all about getting our metrics and numbers square, so that we can tell the story *next* year for increasing and growing our budget +18:29:14 decause++ +18:29:22 ! +18:29:29 cwickert: you can just chime in ;) +18:29:38 We've always had this problem and the only way to improve is with proper reporting +18:29:45 100% agreed +18:29:46 yes +18:29:49 +1 +18:29:54 that also means: We (at least in EMEA) requested more then we got +18:30:08 and at that point we just had to do a haircut +18:30:17 trim all events by x percent +18:30:25 and even skip some small ones +18:30:26 If we dont spend the money in a cycle, we may get less. This is partly responsible for "budget issues" we had in another region years ago. Funding needs change. Based on many things. I did NOT want to do release parties for a while, partly due to the Distro being not too usable. Following consistency model I should have had events, so I can do them now? +18:31:02 I don't think this should be a problem, we just need to pay a little attention. But I'm all for making the FAds happen, even if this means spending less on other events +18:31:20 spending money to ensure the ability to spend it in the future is a bad way of running the ship. +18:31:28 cwickert: +1 +18:32:10 +1 cwickert +18:32:27 RH has the money, we made the product. Some regions choose not to do extra events due to monies. Things vary. +18:32:30 cprofitt: +1 +18:32:31 cwickert: and it is my hope that by improving the connection between ambassadors and commops, we don't ahve to leave event owners to do the reporting entirely on their own +18:33:14 cprofitt: yes, budget is odd in this way, here or in other places. What we have not done before is keeping track of the "hair" that we left on the floor after trimming +18:33:42 cprofitt: Agreed. We need to be able to show the impact of money spent. +18:33:49 if there is an event/opportunity that we are *not* taking, we should record that opportunity cost somewhere so that next year, when we propose the budget, we can make the case for increase. +18:34:08 MarkDude: Well, keep in mind that this is far from all of the money spent on Fedora +18:34:29 False choice, we can do FADs AND local events. We can do more, and more importantly not lower our high standards in process. Having a 20% reserve is a decent way to allow for extras, yet still gauge. +18:34:54 decause: yes, if we can track those 'not done' this year items that may come back that would be good. Budget is always a bit difficult... one idea I like is having a small percentage of the budget that is allocated towards 'initiatives' - spefically trying new things. +18:35:02 I think it comes down to: How can we make sure we make the FADs happen? I see two options: 1) allocate a good chunk of the budget and cut the regional events on the other hand. 2) use the regional budgets to sponsor FAD attendees. While 2 is more flexible, 1 is cleaner and will (hopefully) help us getting more money for FADs next year. +18:35:05 Yes FPL. Ty for letting me speak here to bring these points up. I'll lurk now, and let you folks do your awesomeness. :) +18:35:36 mattdm: yes, we need to show the imapct. +18:35:56 +1 decause on recording opportunities missed. +18:36:01 MarkDude: increasing/reserves anything that is dealing with increasing the "big number" is out of scope for today's discussion. It is important that we have those conversations some where, but the time for adjustment has passed. We have to spend the numbers we have. +18:36:38 decause++ budget page looks good. +18:36:41 cwickert: this is helpful +18:37:32 So... what are our next steps here? +18:37:43 mattdm: right +18:37:57 I'd _really_ like to see something like https://pagure.io/fedora-budget/raw/master/f/FY17/proposedannualbudgets/emea/FedoraEMEABudgetFY2017.ods from LATAM, NA, and APAC +18:38:52 perhaps we can take the overall budget, allocate money for flock, FUDCons, and FADs, and then divide the remaining amount among the regions once we have the budgets from the regional coordianators? +18:38:54 I have a very simple task ahead: update the budget numbers here: https://budget.fedoraproject.org/#budgetnumbers +18:38:59 er, coordinators +18:39:39 mattdm: would you want that spreadsheet to containe impact data or just expenses? +18:39:40 jwb: that sounds about right, yes +18:39:49 cprofitt: awesome question :) +18:40:01 cprofitt: the "impact" data is part of the event reportin that we're going to track going forward +18:40:09 jwb +1 that sounds like a good way to do it. +18:40:11 I was thinking maybe each thing have a link to an event page, which would contain that? +18:40:26 cprofitt: but if you have a better idea I'd love to hear it +18:40:47 I don't think we can "ex post facto" reporting standards onto last year, but we can do some archeology to dig that up for some events +18:40:55 mattdm: +1 +18:41:08 mattdm: hmm... I know that the BrickHack event we had attendee badges... +18:41:13 FWIW, the breakdown in the previous regional budgets (considering regional budgets alone) is about: 16% APAC, 26% EMEA, 16% LATAM, 42% NA +18:41:30 and going forward, the event reports, even if they are hosted on personal blogs, will be aggregated on the commblug +18:41:33 commblog +18:41:39 so that we have them all in one place later +18:41:54 and there are some bullet points that get addressed in each post +18:41:59 * decause digs up link for impact metrics: +18:42:02 cprofitt: fedora-badges badges? that's definitely useful, since we can do analytics on that later. +18:42:11 mattdm: i'm not sure that breakdown holds any longer to be honest +18:42:15 the event page would help with 'expected attendance', 'actual attendance'... but measuring impact might need to have multiple inputs. Different events like converting to Python 3 might have better metrics based on commits. +18:42:20 #link https://fedoraproject.org/wiki/Budget.next#Reimbursement +18:42:33 jwb Yeah, that's just the historical allocations +18:42:43 (also not including FUDCons/Flock) +18:42:48 we likely need to take a closer look at all the possible sources of metrics based on event types... and help organizers of future events be aware that those tools exist. +18:42:58 mattdm: i mention it because i think people need to be aware that historical allocations are not likely to match to this year's allocations +18:43:23 cprofitt: yes, we have a script that is a PoC on tracking fedmsg data in the fedora-stats-tools repo +18:43:49 decause: yes, going back might not be worth the effort. Looking forward we just have to make sure we take a look at how to measure an event... ensure we give as much support to the person coordinating the event as possible. +18:44:15 cprofitt++ +18:44:15 mattdm: Karma for cprofitt changed to 9 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any +18:44:17 cprofitt: these are great discussions to have, and I'm def into it from the commops side of things for sure +18:44:29 falls squarely within "metrics" areas +18:44:49 jwb: yes, I think this is good to point out as well +18:44:51 decause: yeah, likley a side conversation as it is a little bit of a birdwalk for this conversations main topic... +18:45:19 so, as a warning, I mentioned on the ambassador list that if we didn't have a proposed budget reported, that it would impact our ability to allocate budget for a region +18:45:22 Council members: I want to highlight what jwb said a few minutes ago. I agree and want to make sure no one _disagrees_.... +18:45:42 That is: we won't use historical percentage as the baseline for regional allocation +18:45:52 (It _might_ end up like that, but it might not.) +18:46:04 Does anyone disagree with that? +18:46:13 +1 history does not dictate future necesarily +18:46:18 mattdm: so we want people to agree upfront to the 'norm' for determining budget? +18:46:32 I do not disagree mattdm +18:46:37 cprofitt: I'm not sure I understand that question.... +18:47:02 cprofitt: we just want to be clear that this year's numbers will not necessarily be the same as last year's numbers per region +18:47:02 -1 +18:47:03 we want peole to agree with the method of allocating funds -- ahead of allocation.. +18:47:22 cprofitt: hang back for a sec, this is a big question +18:47:34 cwickert: ? +18:47:34 k +18:47:36 cwickert: you disagree that historical budget allocation is not how we're going to allocate this year's budget? +18:47:45 I think historical allocations are the only thing we can actually rely on +18:48:02 meh +18:48:14 and if we don't, we will punish the regions who did good reporting in the past +18:48:21 this paticular year? or future years? +18:48:27 cwickert: i think doing so is not responsible. the 42% allocation to NA seems excessive given the growth of the contributor bases in the other regions +18:49:19 jwb: good point, but I don't see how an increase in user base translates into numbers +18:49:21 if we do not use the historical allocations what will be the way how the budget is distributed ? +18:49:32 cwickert: contributor, not user +18:49:33 so.. i definitely agree that this year might be weird.. but why wouldn't we use historical in future years? +18:49:56 jkurik: perhaps we can look at the submitted budget and attempt to gauge impact of the events and activites +18:50:19 We want to, as a group, agree on a method for determining funding. Keeping in mind that this may, or may not, reflect historical spending. The method of allocation is meant to maximize impact and regional spending may flucuate based on multiple factors. What I am having issues grasping is what the other method is. +18:50:28 we shoud at least keep history in mind when it comes to decide whether cut one or another region. Not relying totally on it, but neither forget it +18:50:40 robyduck: yeah, well put +18:50:41 Question have we ever had a standard "percentage" for each region? +18:50:45 robyduck: yes that is certainly fair +18:50:49 I don't think we have +18:50:50 also cprofitt, well put :) +18:50:56 decause: mattdm listed them above +18:51:03 also .. what does "historical" mean here? do you mean "na always gets 42%" or do you mean "na spent 42% last year and had xyz growth, we shoudl give them more"? +18:51:14 jwb: for every year? +18:51:19 I was *just* looking at the nominal allocations +18:51:25 not even actual-spent money +18:51:35 perhaps having a two part system.... part of the budget is historical, with a portion being allocated based on potential impact. +18:51:44 decause: yes? +18:52:04 ok, good to know. +18:52:18 ok, let me rephrase what I wrote earlier: we need to give all regions a chance. They are to submit a budget, that's the process we always followed. but when we need to decide on the submitted budgets, then we need to have history in mind to see how realistic a request is. We had this 3 or 4 years with the APAC regions: They were very enthusiastic and requested a lot of money, but did not spend much in the end. +18:52:28 look, the fact is that we've had a flat budget for the past 5 years but we've been doing more. if we cannot sufficiently explain why that budget needs to go up, through both accurate _planning_ and accurate _reporting_, it won't go up +18:52:50 jwb: this is def the reality +18:52:52 yes +18:53:03 example: 70% is allocated by historical and 30% is allocated by potential impact. I agree with cwickert that we need to ensure all regions know we are doing this and have a chance to get their reporting in place. +18:53:32 jwb++ +18:53:32 cwickert: I can agree with that. +18:53:34 cwickert: yeah. unfortunately, enthusiasm does not trump actually doing things. +18:53:41 cprofitt, that proposal does not account for "poor planning" ... aka asked for 10 spent 5 +18:54:04 cwickert: I think you're trying to future-proof against the right things, yes +18:54:38 langdon: it was meant to be a rough proposal. I agree we need to adjust based on actually spent money not proposed, but unspent. +18:55:01 I'm definitely suffering from lack of standarization of process in the past +18:55:21 mattdm: agreed. aggregating this history has been challenging +18:55:37 cprofitt: not sure if we can do a percentage, but more something along the lines: Let them request money, look at the requests when they come in and then say: "Ok, region X has a tendency to under-spend, so we cut their budget by 20%, while region Z does very good reporting and therefor we cut their budget by only 5%. That's what we did in FAmSCo all the years. +18:55:54 mattdm: agreed we need to standardize and let everyone know what the process will be. +18:56:05 cwickert: that works for me. +18:56:06 s/reporting/reporting+budgeting +18:56:35 we can also work with regions that have had inconsistent reporting / planning and help them improve. +18:56:38 decause: we don't have numbers from the regions yet, right? +18:56:57 cwickert: yeah, by not following history, I don't mean throwing all that out. +18:56:59 cwickert: i can agree with that somewhat. my main point is that past allocation does not ensure future allocation. it has to be somewhat results driven, based on whatever we consider "results" to be (e.g. perceived or actual impact, accuracy, etc) +18:57:04 one sees in federal research grant funding decisions the use of proposals vetted by peer review, the results of which are consulted by ultimate decision makers. It involves a lot of poorly rewarded work by those doing the review, but I wonder if there's anything useful from that model? +18:57:11 cwickert: we have EMEA numbers, and some LATAM numbers, some rought NA numbers, but I need APAC numbers most +18:57:20 +1 jwb +18:57:39 as far as know only EMEA and APAC have planned/actual budget numbers for FY15 and FY14 +18:57:39 jwb: sure, we totally agree and I'm all for enabling new contributors in other regions because this is where we can grow +18:57:56 dzho: i think that is essentially what we are proposing here, yes. the peers in this case are the council and the regions +18:58:10 decause: we have two FAmSCo members in APAC, let me talk to them on Wednesday +18:58:19 cwickert: awesome, thank you +18:58:45 dzho: yes, what jwb said +18:58:57 * dzho nods, continues lurking +18:59:43 so, from what it looks like, we want the future allocations to be *informed* by historical percentages, but adjusted by results and ahereance to the process +19:00:00 decause, and actuals +19:00:10 okay, so, here we are an hour in. We should be looking at next steps :) +19:00:21 I definitely think we should continue next Monday.... +19:00:27 decause: yes. +19:00:35 step 1 was suggested. which is basically, put in the values for flock, FADs, and fudcons +19:00:35 +1 mattdm +19:00:36 mattdm: I believe we allocated an extra hour today +19:00:37 but we should be looking at concerete decisions at that point. +19:00:42 I did at least on fedocal last time +19:01:02 jwb: I did that in a spreadsheet right before the meeting, which I then failed to save properly :) +19:01:08 decause: if you've imported the ical from fedocal, it does not update +19:01:26 An open question is whether we're going to put the proposed $17k into the APAC FAD +19:01:34 jwb: I think I only added it statically last week, which we cancelled, and then didn't double-blcok this week +19:01:37 that is my bad +19:01:48 decause: er, update in whatever calendar you imported it to. so i'm not sure anyone noticed if you changed it even if you did +19:02:02 mattdm: i mean in the budget.fp.org site +19:02:06 jwb: I'll post those types of updates to the council-discuss next time too, just in case +19:02:15 jwb: oh, good call. +19:02:19 people really love spreadsheets when they are just extra manual steps.. +19:02:31 jwb: the formulas are nice +19:02:40 I prefer csv myself, it is portable and human readable +19:02:55 spreadsheets suck. however, they're really convenient to hack on without knowing what you're really doing :) +19:03:08 aspirationally, I'd love ot paint a picture of what budget reporting could be like :P +19:03:18 i heard jwb propose creating a taiga card for autouploading +19:03:54 17k for a FAD? +19:03:56 the council doesn't use taiga. it could though, and i'd probably be way happier than using trac +19:04:02 * nb thought they were generally 5k +19:04:06 nb: er, sorry. FUDCon +19:04:06 or are you talking about fudcon? +19:04:08 oh ok +19:04:18 which is also quite high +19:04:18 If we get more information from the regions as we go forward, I'm ok with adjusting, but I've given notice on the lists, and reached out individually too (as cwickert will also do this week with apac) +19:04:28 but basically what we approved for LATAM +19:05:05 17k for a FAD? +19:05:10 where does this come from? +19:05:22 cwickert: from me mistyping "FUDCon" :) +19:05:23 ah, sorry, FUDCon +19:05:31 sorry, slow reading the backlog +19:06:41 decause: you wanna #action yourself for putting up a proposal on the budget.fpo page? +19:07:28 #action decause post a proposed budget scenario to council list, and upload the document (spreadsheet or otherwise) to the pagure.io repo +19:07:46 decause++ +19:07:55 mattdm: what I need to know from council is the preferred contours of the scenario +19:07:58 i will crunch a few of them +19:08:12 decause yeah, I was just gonna say a few possibilities would be nice +19:08:18 but mostly I have to make 7 numbers happen: +19:08:23 the first one is done: +19:08:28 Total: 195,000 +19:08:56 I think cwickert original observation about rolling the FUDCon funding into 'council' instead of 'each region' was a keen one +19:09:20 +1 +19:09:28 decause: actually, premiere events have always been handled globally +19:09:28 so I will take the proposed FUDCon and FLock (and pending FAD requests) and roll those into council +19:09:38 cwickert++ +19:09:38 nb: Karma for cwickert changed to 7 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any +19:10:03 i will follow up with OSAS to find out if we got dedicated OSAS funding for Outreachy +19:10:11 #action decause follow up with OSAS to find out if we got dedicated OSAS funding for Outreachy +19:10:16 decause: I think the first step is premiere events vs. regional budget and then we can further distribute the regional budget. +19:10:26 cwickert: yeah, except for in the FY14 budget email, where they were divvyed up to the regions even though then later handled centrally +19:10:27 otherwise, I'd like to request that we allocate one slot per quarter as one scenario +19:10:39 ideally 2 (tech and non-tech) +19:10:44 that'll be one scenario +19:10:59 but the overarching scenario, of the regional percentages +19:11:23 those should hold as a "base-line" then, but will not be 100% the same as history +19:11:28 and we could as well say: premiere events = council, regional budget = FAmSCo. That's what we did in the past. It wasn't perfect (for technical events in a region such as FADs), but it worked. +19:11:50 yup +19:11:52 I'd like to see regional planning FADs budgeted in, and as line items for the regions +19:12:26 #info regional budget planning FADs for each region, as part of the region's budget +19:12:27 mattdm: if we fly the design team to the US for a FAD, how is that regional? +19:12:40 there's some disparity in the docs on FADs about whether or not they regional events in general +19:12:48 FAD is a centrally organized, not regionally organized event +19:12:50 decause: I disagree with the #info +19:12:53 right +19:13:08 cwickert: but in what I meant above, I meant specifically region-focused planning FADs +19:13:10 so we all should have a regional planning FAD now? +19:13:19 cwickert: mattdm is talking about budte planning FADs, like what EMEA has been doing for years +19:13:31 s/budte/budget +19:13:36 * nb not opposed +19:13:47 nb I think it's a good model. It makes sense to colocate it with other events (Flock, FUDCons) when possible +19:13:51 mattdm, decause: that should be one FAD for each region, so easy to budget. +19:14:00 mattdm, yeah +19:14:03 s/budget/project +19:14:03 nb: yes, we should, so that there are *always* numbers for the council to consider in the future, unlike today ;) +19:14:21 cwickert: yeah, and that's why I was suggesting putting them as line items in the regions +19:14:29 decause, mattdm good idea +19:14:32 we did that a few years ago in NA +19:14:34 mattdm: makes sense +19:14:52 Blacksburg maybe, we had the FAD the day before fudcon, then more people got to stay for fudcon also +19:15:01 mattdm: standard $5K FAD limit? +19:15:03 nb exactly, yeah. +19:15:10 mattdm: note we might not even need a planing FAD in some regions if they have FLOCK or a FUDCon +19:15:10 decause: up in the air, I think +19:15:19 decause: yes, 5k should be ok everywhere +19:15:20 * mattdm squints at that bottom line +19:15:26 mattdm: agreed. I can try to crunch a high and low scenario then +19:15:34 * decause signs up for more work +19:15:37 :P +19:15:38 decause++ +19:15:39 cwickert, true, depending on how many people get funded for flock/fudcon otherwise +19:15:52 * nb sees it more as "paying for more people to go to Flock, given that there is a planning session at flock" +19:15:54 cwickert: I'd rather say "we have the planning FAD at Flock/FUDCon" +19:15:54 or something like that +19:15:59 mattdm++ +19:15:59 nb: Karma for mattdm changed to 12 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any +19:16:01 the good news is, Flock planning has given their number at $75K this year +19:16:09 mattdm: that's what I meant +19:16:09 same as last year +19:16:18 cwickert: cool +19:16:27 so, that is a nice 'not-dotted-line' item +19:16:52 that's an interesting way to put it :) +19:17:10 decause: prices are highter are EMEA and NA, but travel is more expensive in APAC and LATAM. So 5k for a planning FAD should do everywhere and if it is co-located with another event, we just skip it in the budget. +19:17:29 to avoid confusion, why don't we put those planning FAD events in the reginal budget and handle the other FADs globally? This way every region also can manage their budget better, doing the planing with other events like fudcon or flock. +19:17:42 just a thought +19:17:48 cwickert: no... we show the that 5k was allocated to bring more people to Flock/FUDCon +19:17:53 we don't "skip" things any more +19:17:56 robyduck: I think that's what we're saying +19:18:08 robyduck: yeah, what mattdm said +19:18:10 jwb++ +19:18:10 nb: Karma for jwboyer changed to 9 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any +19:18:13 we can name them differently +19:18:30 but that's a detail +19:18:33 jwb: ok, if you put it that way. +19:19:02 we're going to be settling on a standard format for reporting these things (my vote is based off the very decent EMEA sheet) +19:19:06 I am all for finding more ways to get involved, active people on the ground at Flock that don't involve them needing to give a talk +19:19:22 #link https://docs.google.com/spreadsheets/d/11nWHrooCwoiWqGx4iEUnITQAWwQrQ6_2ito8GUtBk_g/edit#gid=0 +19:19:30 mattdm, i agree. I mainly only submitted a talk so that I could hopefully get funding +19:19:35 mattdm: would be nice +19:19:47 * nb wnats to go to plan stuff for next year in NA +19:19:54 that's probably a conversation for another time, though :) +19:19:59 agreed +19:20:13 I'm going to be pushing my updates to the pagure.io/fedora-budget repo +19:20:20 they'll likely be spreadsheets/csv +19:20:28 unless jwb, you have a better suggestion? +19:20:45 * decause is *def* open to better ideas +19:21:07 i suggested just updating the website with pull requests, but whatever works for the people actually doing this is what will work best +19:21:18 I saw whatever works, is consistent, and puts 'em all in the same place for later +19:21:30 jwb: the website does not get granular down to the proposed budget levels (yet) +19:21:52 standing up the entire 'fedora-websites' repo is a bit much to just twiddle a number +19:21:55 imho +19:22:25 jwb: but yeah, the future /could/ look like a webhook that updates the production site based on data in fedora-budget repo +19:22:28 ideal bridge +19:22:31 +1 jwb +19:22:39 * cwickert needs to run now, it's already late here. I will read the log later, but so far I'm happy with decause's approach. +19:23:03 cwickert: thank you for your support, and I'll be sure to add council to the pagure.io members with push/pull access +19:23:17 thanks cwickert! +19:23:20 doing budget with PR's is going to be *much* better than emailing spreadsheets +19:23:31 #action cwickert to discuss the budget with FAMSCo, in particular from APAC and LATAM +19:23:58 ok, bye +19:25:13 decause, we could always make it a separate repo +19:25:25 nb: http://pagure.io/fedora-budget +19:25:30 ok +19:25:31 so +19:25:40 * mattdm isn't technically leaving but is starting to have wandering-brain syndrome.... +19:25:55 what were those percentages again? I can dig for them in the logs, but it'd be nice to have some consensus on what they are +19:26:18 decause, oh ok +19:26:36 nb: which, btw, there is a NA folder that could *totally* use some input ;) +19:26:41 decause the historical fraction? +19:26:42 nb++ +19:26:46 mattdm: yes +19:26:55 * decause didn't know there was one before today +19:27:15 decause: roughly: APAC 16% EMEA 26% LATAM 16% NA 42% +19:27:28 I'll have a few scenarios for everyone to discuss next week +19:27:33 it's not a rule -- it's an extrapolation from FY14, FY15, FY16 +19:27:56 mattdm: acknowleged, I think we all agreed that it is more of a 'guideline' than a rule +19:28:02 +1 +19:28:17 next week we should still do a double block though, yeah? +19:28:35 decause: well, I think we shouldn't even consider it a guideline -- more, another input into the process +19:28:44 decause: yeah, I think double-book is good +19:28:55 #action decause schedule double-block council meeting for budgeting on fedocal +19:29:06 literally dbl? or 2h? +19:29:14 2h = dbl +19:29:29 or I guess we could also get #fedora-meeting-1 :) +19:29:33 #help Ambassadors please submit your Budget Reports, Proposals, and Delegation Selections to decause ASAP +19:30:10 #info where ASAP really means "this week, because we want to decide things next week, so we can actually spend money without fear" +19:30:39 probably should info those fy16 allocations too, no? +19:31:17 langdon: maybe? +19:31:32 langdon: I don't think they are supposed to be 'concrete' +19:31:50 decause, well.. they were for fy16, right? +19:32:21 more info doesn't hurt +19:32:24 langdon: I thought mattdm said they were conglomerated from history,not just last year +19:32:25 * mattdm composes an info +19:32:32 ok +19:32:39 yeah, since mattdm crunched, he knows best +19:33:36 #info Allocation of regional portion of budget over last three years roughly APAC 16%, EMEA 26%, LATAM 16%, NA 42%. This is nominal, not money actually spent. FY17 and future budgets not necessarily based on this number. +19:33:42 mattdm: since I'm going to be travelling on Thursday, and attending all-weekend events, the sooner the better. I'd like to have the scenarios posted by Wednesday in an ideal world +19:33:57 mattdm++ +19:34:38 decause: hopefully that can happen :) +19:35:29 mattdm: :) +19:35:35 ok +19:35:45 I think we're all in a good place here? +19:36:00 yes +19:36:04 Good enough. Planning to be in a great place this time next year. +19:36:09 Thanks, everyone! +19:36:27 (esp. decause who did the bulk of the typing!) +19:36:30 #endmeeting \ No newline at end of file diff --git a/FY17/archive/adjustedannualbudgets/council/proposedadjustedbudgetfy17.csv b/FY17/archive/adjustedannualbudgets/council/proposedadjustedbudgetfy17.csv new file mode 100644 index 0000000..8e9f0d5 --- /dev/null +++ b/FY17/archive/adjustedannualbudgets/council/proposedadjustedbudgetfy17.csv @@ -0,0 +1,78 @@ +,,fF/fDI,fF/-DI,hF/DI,hF/hDI,hF/-DI +Events,,,,,, +------,,,,,, +"FUDCon LATAM",,15000,10000,10000,10000,10000 +"FUDCon APAC",,15000,15000,15000,15000,15000 +Flock,,75000,75000,75000,75000,75000 +FADs,,30000,30000,15000,15000,15000 +D&I,,11000,0,11000,5500,0 +,,,,,, +"Big Number",,195000,195000,195000,195000,195000 +subtotal,,156000,145000,126000,120500,115000 +Regional,,39000,50000,69000,74500,80000 +,,,,,, +"FADS Breakdown",,,,,, +--------------,,,,,, +Docs2016,,5000,5000,5000,5000,5000 +Design2016,,5000,5000,5000,5000,5000 +Cloud2016,,5000,5000,5000,5000,5000 +"FAD #1",,5000,0,0,0,0 +"FAD #2",,5000,0,0,0,0 +"FAD #3",,5000,0,0,0,0 +,,,,,, +"D&I Breakdown",,,,,, +-------------,,,,,, +"Outreachy Winter",,5500,0,5500,2250,0 +"Outreachy Spring",,5500,0,5500,2250,0 +,,,,,, +,,,,,, +"Regions: R/4",,,,,, +------------,,,,,, +APAC,,9750,12500,17250,18625,20000 +EMEA,,9750,12500,17250,18625,20000 +LATAM,,9750,12500,17250,18625,20000 +NA,,9750,12500,17250,18625,20000 +,,,,,, +"Regions: R*HS",,,,,, +-------------,,,,,, +"APAC (.16)",,6240,8000,11040,11920,12800 +"EMEA (.26)",,10140,13000,17940,19370,20800 +"LATAM (.16)",,6240,8000,11040,11920,12800 +"NA (.43)",,16380,21000,28980,31290,33600 +,,,,,, +"Historical Diff: R/4",,,,,, +--------------------,,,,,, +APAC,12650,9750,12500,17250,18625,20000 +,,-2900,-150,4600,5975,7350 +,,-0.23,,,,0.58 +,,,,,, +EMEA,27000,9750,12500,17250,18625,20000 +,,-17250,-14500,-9750,-8375,-7000 +,,-0.64,,,,-0.26 +,,,,,, +LATAM,16500,9750,12500,17250,18625,20000 +,,-6750,-4000,750,2125,3500 +,,-0.41,,,,0.21 +,,,,,, +NA,43850,9750,12500,17250,18625,20000 +,,-34100,-31350,-26600,-25225,-23850 +,,-0.78,,,,-0.54 +,,,,,, +,,,,,, +"Historical Diff: R*HS",,,,,, +---------------------,,,,,, +APAC,-0.16,6240,8000,11040,11920,12800 +,12650,-6410,-4650,-1610,-730,150 +,,-0.51,,,,0.01 +,,,,,, +EMEA,-0.26,10140,13000,17940,19370,20800 +,27000,-16860,-14000,-9060,-7630,-6200 +,,-0.62,,,,-0.23 +,,,,,, +LATAM,-0.16,6240,8000,11040,11920,12800 +,16500,-10260,-8500,-5460,-4580,-3700 +,,-0.62,,,,-0.22 +,,,,,, +NA,-0.42,16380,21000,28980,31290,33600 +,43850,-27470,-22850,-14870,-12560,-10250 +,,-0.63,,,,-0.23 diff --git a/FY17/archive/adjustedannualbudgets/council/proposedadjustedbudgetfy17.gnumeric b/FY17/archive/adjustedannualbudgets/council/proposedadjustedbudgetfy17.gnumeric new file mode 100644 index 0000000..4c14508 Binary files /dev/null and b/FY17/archive/adjustedannualbudgets/council/proposedadjustedbudgetfy17.gnumeric differ diff --git a/FY17/archive/adjustedannualbudgets/council/proposedadjustedbudgetfy17.ods b/FY17/archive/adjustedannualbudgets/council/proposedadjustedbudgetfy17.ods new file mode 100644 index 0000000..416059a Binary files /dev/null and b/FY17/archive/adjustedannualbudgets/council/proposedadjustedbudgetfy17.ods differ diff --git a/FY17/archive/adjustedannualbudgets/council/proposedadjustedbudgetfy17.txt b/FY17/archive/adjustedannualbudgets/council/proposedadjustedbudgetfy17.txt new file mode 100644 index 0000000..8e9f0d5 --- /dev/null +++ b/FY17/archive/adjustedannualbudgets/council/proposedadjustedbudgetfy17.txt @@ -0,0 +1,78 @@ +,,fF/fDI,fF/-DI,hF/DI,hF/hDI,hF/-DI +Events,,,,,, +------,,,,,, +"FUDCon LATAM",,15000,10000,10000,10000,10000 +"FUDCon APAC",,15000,15000,15000,15000,15000 +Flock,,75000,75000,75000,75000,75000 +FADs,,30000,30000,15000,15000,15000 +D&I,,11000,0,11000,5500,0 +,,,,,, +"Big Number",,195000,195000,195000,195000,195000 +subtotal,,156000,145000,126000,120500,115000 +Regional,,39000,50000,69000,74500,80000 +,,,,,, +"FADS Breakdown",,,,,, +--------------,,,,,, +Docs2016,,5000,5000,5000,5000,5000 +Design2016,,5000,5000,5000,5000,5000 +Cloud2016,,5000,5000,5000,5000,5000 +"FAD #1",,5000,0,0,0,0 +"FAD #2",,5000,0,0,0,0 +"FAD #3",,5000,0,0,0,0 +,,,,,, +"D&I Breakdown",,,,,, +-------------,,,,,, +"Outreachy Winter",,5500,0,5500,2250,0 +"Outreachy Spring",,5500,0,5500,2250,0 +,,,,,, +,,,,,, +"Regions: R/4",,,,,, +------------,,,,,, +APAC,,9750,12500,17250,18625,20000 +EMEA,,9750,12500,17250,18625,20000 +LATAM,,9750,12500,17250,18625,20000 +NA,,9750,12500,17250,18625,20000 +,,,,,, +"Regions: R*HS",,,,,, +-------------,,,,,, +"APAC (.16)",,6240,8000,11040,11920,12800 +"EMEA (.26)",,10140,13000,17940,19370,20800 +"LATAM (.16)",,6240,8000,11040,11920,12800 +"NA (.43)",,16380,21000,28980,31290,33600 +,,,,,, +"Historical Diff: R/4",,,,,, +--------------------,,,,,, +APAC,12650,9750,12500,17250,18625,20000 +,,-2900,-150,4600,5975,7350 +,,-0.23,,,,0.58 +,,,,,, +EMEA,27000,9750,12500,17250,18625,20000 +,,-17250,-14500,-9750,-8375,-7000 +,,-0.64,,,,-0.26 +,,,,,, +LATAM,16500,9750,12500,17250,18625,20000 +,,-6750,-4000,750,2125,3500 +,,-0.41,,,,0.21 +,,,,,, +NA,43850,9750,12500,17250,18625,20000 +,,-34100,-31350,-26600,-25225,-23850 +,,-0.78,,,,-0.54 +,,,,,, +,,,,,, +"Historical Diff: R*HS",,,,,, +---------------------,,,,,, +APAC,-0.16,6240,8000,11040,11920,12800 +,12650,-6410,-4650,-1610,-730,150 +,,-0.51,,,,0.01 +,,,,,, +EMEA,-0.26,10140,13000,17940,19370,20800 +,27000,-16860,-14000,-9060,-7630,-6200 +,,-0.62,,,,-0.23 +,,,,,, +LATAM,-0.16,6240,8000,11040,11920,12800 +,16500,-10260,-8500,-5460,-4580,-3700 +,,-0.62,,,,-0.22 +,,,,,, +NA,-0.42,16380,21000,28980,31290,33600 +,43850,-27470,-22850,-14870,-12560,-10250 +,,-0.63,,,,-0.23 diff --git a/FY17/archive/adjustedannualbudgets/council/scenarios.txt b/FY17/archive/adjustedannualbudgets/council/scenarios.txt new file mode 100644 index 0000000..fef5b37 --- /dev/null +++ b/FY17/archive/adjustedannualbudgets/council/scenarios.txt @@ -0,0 +1,164 @@ +=============================================================================== +Budget +=============================================================================== + +Scenario 1: Full FADs, Full Outreachy +Scenario 2: Full FADs, Zero Outreachy +Scenario 3: Half FADs, Full Outreachy +Scenario 4: Half FADs, Half Outreachy +Scenario 5: Half FADs, Zero Outreachy + +R/4: Regional budget, divided Evenly +R*HS: Historial Split (.16, .26, .16, .42) + +Legend: +------- + fF/FDI Full FADS, Full D&I + fF/-DI Full FADS, zero D&I + hF/DI half FADS, Full D&I + hF/hDI half FADS, Half D&I + hF/-DI half FADS, zero D&I + R/4 Regional budget, divided Evenly + R*HS Historical Split (.125, .27, .165, .438) + + + fF/fDI fF/-DI fF/hDI hF/DI hF/hDI hF/-DI +Events +------ + FUDCon LATAM 15000 10000 10000 10000 10000 10000 + FUDCon APAC 15000 15000 15000 15000 15000 15000 + Flock 75000 75000 75000 75000 75000 75000 + FADs 30000 30000 30000 15000 15000 15000 + D&I 11000 0 5500 11000 5500 0 + ---------------------------------------------------------------- + Big Number 195000 195000 195000 195000 195000 195000 + subtotal 156000 145000 135500 126000 120500 115000 + Regional 39000 50000 59500 69000 74500 80000 +FADS Breakdown + +-------------- + Docs2016 5000 5000 5000 5000 5000 5000 + Design2016 5000 5000 5000 5000 5000 5000 + Cloud2016 5000 5000 5000 5000 5000 5000 + FAD #1 5000 0 5000 0 0 0 + FAD #2 5000 0 5000 0 0 0 + FAD #3 5000 0 5000 0 0 0 + +D&I Breakdown +------------- + Outreachy Winter 5500 0 2250 5500 2250 0 + Outreachy Spring 5500 0 2250 5500 2250 0 + + +Regions: R/4 +------------ + APAC 9750 12500 14875 17250 18625 20000 + EMEA 9750 12500 14875 17250 18625 20000 + LATAM 9750 12500 14875 17250 18625 20000 + +Regions: R*HS +------------- + APAC (.16) 6240 8000 9520 11040 11920 12800 + EMEA (.26) 10140 13000 15470 17940 19370 20800 + LATAM (.16) 6240 8000 9520 11040 11920 12800 + NA (.42) 16380 21000 24990 28980 31290 33600 + +Historical Diff: R/4 +-------------------- + APAC (12650) 9750 12500 14875 17250 18625 20000 + -2900 -150 +2225 +4600 +5975 +7350 + -23% +18% +58% + + EMEA (27000) 9750 12500 14875 17250 18625 20000 + -17250 -14500 -12125 -9750 -8375 -7000 + -64% -45% -26% + + LATAM (16500) 9750 12500 14875 17250 18625 20000 + -6750 -4000 -1625 +750 +2125 +3500 + -41% -10% +21% + + NA (43850) 9750 12500 14875 17250 18625 20000 + -34100 -31350 -28975 -26600 -25225 -23850 + -78% -66% -54% + +Historical Diff: R*HS +--------------------- + APAC (.127) 6240 8000 9520 11040 11920 12800 + (12650) -6410 -4650 -3130 -1610 -730 +150 + -51% -25% +1% + + EMEA (.27) 10140 13000 15470 17940 19370 20800 + (27000) -16860 -14000 -11530 -9060 -7630 -6200 + -62% -43% -23% + + LATAM (.165) 6240 8000 9520 11040 11920 12800 + (16500) -10260 -8500 -6980 -5460 -4580 -3700 + -62% -42% -22% + + NA (.438) 16380 21000 24990 28980 31290 33600 + (43850) -27470 -22850 -18860 -14870 -12560 -10250 + -63% -43% -23% + +=============================================================================== +Notes +=============================================================================== + +19:33:36 #info Allocation of regional portion of budget over last +three years roughly APAC 16%, EMEA 26%, LATAM 16%, NA 42%. This is nominal, +not money actually spent. FY17 and future budgets not necessarily based on +this number. + + +Big Number +---------- + FY14 TOTAL 195,000 + FY15 TOTAL 195,000 + FY16 TOTAL 195,000 + FY17 TOTAL 195,000 + +Historical Percentages +---------------------- + APAC 16% + EMEA 26% + LATAM 16% + NA 42% + +Historical Allocated Numbers (FY15 + FY16) +------------------------------------------ + Region w/FE + APAC 12650 (222650) + Q1: 2900 + Q2: 10750 + Q3: 3000 + Q4: 6000 + FE: 10000 + + EMEA 27000 (102000) + Q1: 12000 + Q2: 80000 + Q3: 5000 + Q4: 5000 + FE: 75000 + + LATAM 16500 (26500) + Q1: 6000 + Q2: 3000 + Q3: 3750 + Q4: 3750 + FE: 10000 + + NA 43850 (43850) + Q1: 7850 + Q2: 15000 + Q3: 7000 + Q4: 14000 + + + +Final Reported FY16 +------------------- + Planned Adjusted Actual +APAC ??? ??? ??? +EMEA 35,670 31,746 29,014 +LATAM ??? ??? ??? +NA ??? ??? ??? diff --git a/FY17/archive/adjustedannualbudgets/emea/FY17_EMEA_Adjusted_Budget.ods b/FY17/archive/adjustedannualbudgets/emea/FY17_EMEA_Adjusted_Budget.ods new file mode 100644 index 0000000..4201472 Binary files /dev/null and b/FY17/archive/adjustedannualbudgets/emea/FY17_EMEA_Adjusted_Budget.ods differ diff --git a/FY17/archive/delegations/apac.yaml b/FY17/archive/delegations/apac.yaml new file mode 100644 index 0000000..4e9cd1e --- /dev/null +++ b/FY17/archive/delegations/apac.yaml @@ -0,0 +1,7 @@ +apac_delegates: + treasurer_name: "Mohd Izhar Firdaus Ismail (izhar)" + treasurer_email: "kagesenshi.87@gmail.com" + logistician_name: "PJ Pandit (Pjp)" + logistician_email: "pj.pandit@yahoo.co.in" + storyteller_name: "Gerard Braad - 吉拉德 (gbraad)" + storyteller_email: "me+fedora@gbraad.nl" diff --git a/FY17/archive/delegations/council.yaml b/FY17/archive/delegations/council.yaml new file mode 100644 index 0000000..f1212f7 --- /dev/null +++ b/FY17/archive/delegations/council.yaml @@ -0,0 +1,7 @@ +council_delegates: + treasurer_name: "Remy DeCausemaker" + treasurer_email: "decause@redhat.com" + logistician_name: "Remy DeCausemaker" + logistician_email: "decause@redhat.com" + storyteller_name: "Remy DeCausemaker" + storyteller_email: "decause@redhat.com" diff --git a/FY17/archive/delegations/emea.yaml b/FY17/archive/delegations/emea.yaml new file mode 100644 index 0000000..a6f1c8b --- /dev/null +++ b/FY17/archive/delegations/emea.yaml @@ -0,0 +1,7 @@ +emea_delegates: + treasurer_name: "Zacharias Mitzelos (mitzie)" + treasurer_email: "mitzie@mitzelos.com" + logistician_name: "Jiri Eischmann (sesivany)" + logistician_email: "eischmann@redhat.com" + storyteller_name: "Elijah Hanson (edgates)" + storyteller_email: "pkwesihanson@yahoo.com" diff --git a/FY17/archive/delegations/latam.yaml b/FY17/archive/delegations/latam.yaml new file mode 100644 index 0000000..f56954f --- /dev/null +++ b/FY17/archive/delegations/latam.yaml @@ -0,0 +1,7 @@ +latam_delegates: + treasurer_name: "Abdel G. Martínez L." + treasurer_email: "abdel.g.martinez.l@gmail.com" + logistician_name: "Eduardo J. Echeverria A." + logistician_email: "echevemaster@gmail.com" + storyteller_name: "William Moreno Reyes" + storyteller_email: "williamjmorenor@gmail.com" diff --git a/FY17/archive/delegations/na.yaml b/FY17/archive/delegations/na.yaml new file mode 100644 index 0000000..c7b4248 --- /dev/null +++ b/FY17/archive/delegations/na.yaml @@ -0,0 +1,7 @@ +na_delegates: + treasurer_name: "Andrew Ward" + treasurer_email: "award3535@tds.net" + logistician_name: "Ben Williams" + logistician_email: "vaioof@yahoo.com" + storyteller_name: "Brian Monroe" + storyteller_email: "briancmonroe@gmail.com" diff --git a/FY17/archive/events/README.md b/FY17/archive/events/README.md new file mode 100644 index 0000000..7013373 --- /dev/null +++ b/FY17/archive/events/README.md @@ -0,0 +1,10 @@ +Events +====== + +As we have made the budget process more transparent as part of the Budget.next +initiative (http://fedoraproject.org/wiki/Budget.next) this repository has +served as a resource for documents and files related to spending, reporting, +and planning. Fedora Events, a component of the public budget, may also benefit +from the existence of this repository. + +Events tracked here could include: Flock, FUDCon LATAM, FUDCon APAC, and our FADs. diff --git a/FY17/archive/events/flock/todo.md b/FY17/archive/events/flock/todo.md new file mode 100644 index 0000000..b0d2b69 --- /dev/null +++ b/FY17/archive/events/flock/todo.md @@ -0,0 +1,43 @@ +Proposal +======== +https://fedoraproject.org/wiki/Flock2016-Krakow-proposal + +Tasks +===== + +- create proposal (bex) +- book venue (bex and jmad) +- book evening events (bex and decause) +- book keynotes +- book sponsors (spot) +- establish budget (decause) + +Budget +====== +The total budget for Flock was approved by the Fedora Council to be **$75,000USD** + +The components of budget will include: + +- venue +- Travel +- Evening Event 1 +- Evening Event 2 +- Swag +- Food/meals +- A/V Equipment +- other things not yet on this list + + +Evening Events +============== +http://etherpad.osuosl.org/flock2016-evening + + +Flock Talks Voting +================== +Selection committee members contact jwb@fp.o if you need more information. + + +More details +------------ +This is a working document, and will be updated going forward. diff --git a/FY17/archive/proposedannualbudgets/apac/apac.txt b/FY17/archive/proposedannualbudgets/apac/apac.txt new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/FY17/archive/proposedannualbudgets/apac/apac.txt diff --git a/FY17/archive/proposedannualbudgets/emea/FedoraEMEABudgetFY2017-Budget.csv b/FY17/archive/proposedannualbudgets/emea/FedoraEMEABudgetFY2017-Budget.csv new file mode 100644 index 0000000..47eeb5f --- /dev/null +++ b/FY17/archive/proposedannualbudgets/emea/FedoraEMEABudgetFY2017-Budget.csv @@ -0,0 +1,79 @@ +Expense,Planned,Adjusted,Actual,Tickets/Recipts +,,Quarter 1 (March-May 2016),, +Events,,,, +Mozilla & Fedora Activity Day,$80,,, +PyCon SK,$400,,,"#551, #552 (~180$, unconfirmed)" +Open Source Weekend,$50,,, +Chemnitzer Linux Tage 2016,"$1,300",,,"#549(~210 euros unconfirmed), #559(~43$ unconfirmed)" +3D Expo,$120,,, +LinuxWochen Vienna,$500,`,, +Fosscomm,$400,,, +DORS/CLUC,$700,,,#558: Travel for Jona +OSCAL,$800,,,#557: Travel for Jiri +,"$4,350",$0,$0.00, +SWAG,,,, +Booth Material Initiative,"$1,000",,, +Other Swag,"$2,000",,, +,"$3,000",$0,$0.00, +Shipping,,,, +Swag & Media shipping,$500,,, +,$500,$0,$0.00, +,,,, +Total for Quarter,"$7,850",$0,$0.00, +,,,, +,,Quarter 2 (June-August 2015),, +Events,,,, +FrOSCon,"$1,500",,, +EuroPython,"$2,000",,, +Flock 2016,$800,,, +,"$4,300",$0,$0.00, +Swag,,,, +F24 Media production,"$1,000",,, +Other Swag,"$1,200",,, +,"$2,200",$0,$0.00, +Shipping,,,, +Swag & Media Shipping,"$1,300",,, +,"$1,300",$0,$0.00, +,,,, +Total for Quarter,"$7,800",$0,$0.00, +,,,, +,,Quarter 3 (September-November 2015),, +Events,,,, +LinuxCon Europe,"$2,000",,, +Bar Camp Manchester,$800,,, +FSCONS,"$1,400",,, +OSOL Conference,$500,,, +BalCCon_2k16,$800,,, +SFK16,$300,,, +PyCon CZ ,$200,,, +LinuxDays Prague,$50,,, +,"$6,050.00",$0,$0.00, +Swag,,,, +Other Swag,"$1,200",,, +,"$1,200",$0,$0.00, +Shipping,,,, +Swag & Media shipping,$400,,, +,$400,$0,$0.00, +,,,, +Total for Quarter,"$7,650",$0,$0.00, +,,,, +,,Quarter 4 (December 2015 - February 2016),, +Events,,,, +Chaos Communication Congress,"$2,500",,, +FOSDEM,"$3,000",,, +Fedora 25 Release Parties,$150,,, +,"$5,650",$0,$0.00, +Swag,,,, +F25 media production,"$1,000",,, +Other Swag,"$1,800",,, +,"$2,800",$0,$0.00, +Shipping,,,, +Swag & Media shipping,"$1,500",,, +,"$1,500",$0,$0.00, +,,,, +Total for Quarter,"$9,950",$0,$0.00, +,,,, +Total for Fiscal Year,"$33,250",$0,$0.00, +,,,, +% of adjustment,,0.00%,, +Absolute % of adjustment,,0.00%,, \ No newline at end of file diff --git a/FY17/archive/proposedannualbudgets/emea/FedoraEMEABudgetFY2017.ods b/FY17/archive/proposedannualbudgets/emea/FedoraEMEABudgetFY2017.ods new file mode 100644 index 0000000..7478756 Binary files /dev/null and b/FY17/archive/proposedannualbudgets/emea/FedoraEMEABudgetFY2017.ods differ diff --git a/FY17/archive/proposedannualbudgets/latam/fy17.csv b/FY17/archive/proposedannualbudgets/latam/fy17.csv new file mode 100644 index 0000000..887a3fa --- /dev/null +++ b/FY17/archive/proposedannualbudgets/latam/fy17.csv @@ -0,0 +1,8 @@ +Quarter,Planned,Actual +Q1,8780,0 +Q2,6600,0 +Q3,5400,0 +Q4,2400,0 +Total,23180,0 +Tally,,23180 +Usage Percentage,,0% \ No newline at end of file diff --git a/FY17/archive/proposedannualbudgets/latam/q1.csv b/FY17/archive/proposedannualbudgets/latam/q1.csv new file mode 100644 index 0000000..bbee072 --- /dev/null +++ b/FY17/archive/proposedannualbudgets/latam/q1.csv @@ -0,0 +1,41 @@ +Event,Planned,Actual,Tickets,Reports +1. Events,4430,,, +1.1 FLISOL,1630,,, +1.1.1 Peru - Cusco,120,,, +1.1.2 Peru - Puno,120,,, +1.1.3 Peru - Lima,200,,, +1.1.4 Joinville,120,,, +1.1.5 Venezuela,200,,, +1.1.6 Panama,150,,, +1.1.7 CryptoRave,150,,, +1.1.8 Ciudad de Mexico,250,,, +1.1.9 Colombia,200,,, +1.1.10 Bolivia,120,,, +1.2 Fedora 24 Release Party,1250,,, +1.2.1 Peru - Cusco,100,,, +1.2.2 Peru - Puno,100,,, +1.2.3 Peru - Lima,100,,, +1.2.4 Venezuela,100,,, +1.2.5 Nicaragua,100,,, +1.2.6 Panama,100,,, +1.2.7 Uruguay,100,,, +1.2.8 Ciudad de Mexico,250,,, +1.2.9 TESCHA Edo - Mexico,100,,, +1.2.10 Bolivia - La Paz,100,,, +1.2.11 Bolivia - Cochabamba,100,,, +1.3 Foro de Software Libre UCR,800,,, +1.4 Document Freedom Day - Panama,150,,, +1.5 Solisc,500,,, +1.6 Mini Workshop - Uruguay,100,,, +2. Swag,4350,,, +2.1 Nicaragua,620,,, +2.2 Panama,500,,, +2.3 Mexico,650,,, +2.4 Colombia,650,,, +2.5 Bolivia,650,,, +2.6 Peru,680,,, +2.7 Uruguay,600,,, +3. Shipping,0,,, +Total,8780,0,, +Tally,,8780,, +Usage Percentage,,0%,, \ No newline at end of file diff --git a/FY17/archive/proposedannualbudgets/latam/q2.csv b/FY17/archive/proposedannualbudgets/latam/q2.csv new file mode 100644 index 0000000..165db5d --- /dev/null +++ b/FY17/archive/proposedannualbudgets/latam/q2.csv @@ -0,0 +1,16 @@ +Event,Planned,Actual,Tickets,Reports +1. Events,6600,,, +1.1 CONEISC,900,,, +1.2 Fedora Week,100,,, +1.3 Fedora Day,100,,, +1.4 ECSL,1000,,, +1.5 Fedora Day: UIP Panama,100,,, +1.6 Fedora Day: UDI Panama,1000,,, +1.7 FISL 17,2000,,, +1.8 Campus Party 2016 - Mexico,400,,, +1.9 Fedora Meeting Sucre,1000,,, +2. Swag,0,,, +3. Shipping,0,,, +Total,6600,0,, +Tally,,6600,, +Usage Percentage,,0%,, \ No newline at end of file diff --git a/FY17/archive/proposedannualbudgets/latam/q3.csv b/FY17/archive/proposedannualbudgets/latam/q3.csv new file mode 100644 index 0000000..70b92e8 --- /dev/null +++ b/FY17/archive/proposedannualbudgets/latam/q3.csv @@ -0,0 +1,21 @@ +Event,Planned,Actual,Tickets,Reports +1. Events,5300,,, +1.1 Software Freedom Day,650,,, +1.1.1 Cusco,100,,, +1.1.2 San Cristobal,50,,, +1.1.3 Nicaragua,100,,, +1.1.4 Mexico,150,,, +1.1.5 Panama,150,,, +1.1.6 La Paz,100,,, +1.2 Linux Day,150,,, +1.3 FTSL,500,,, +1.4 Latinoware,2000,,, +1.5 Hackmeeting - Mexico,500,,, +1.6 Fedora Day - Colombia,250,,, +1.7 Conasol - Bolivia,600,,, +1.8 Hackmeeting - Bolivia,650,,, +2. Swag,100,,, +2.1 Colombia,100,,, +Total,5400,0,, +Tally,,5400,, +Usage Percentage,,0%,, \ No newline at end of file diff --git a/FY17/archive/proposedannualbudgets/latam/q4.csv b/FY17/archive/proposedannualbudgets/latam/q4.csv new file mode 100644 index 0000000..f201460 --- /dev/null +++ b/FY17/archive/proposedannualbudgets/latam/q4.csv @@ -0,0 +1,22 @@ +Event,Planned,Actual,Tickets,Reports +1. Events,2400,,, +1.1 Fedora 25 Release Party,1150,,, +1.1.1 Cusco - Peru,100,,, +1.1.2 Puno - Peru,100,,, +1.1.3 Lima - Peru,100,,, +1.1.4 San Cristobal,100,,, +1.1.5 Nicaragua,100,,, +1.1.6 Ciudad de Mexico,250,,, +1.1.7 Panama,100,,, +1.1.8 TESCHA Mexico,100,,, +1.1.9 Bolivia - La Paz,100,,, +1.1.10 Bolivia - Cochabamba,100,,, +1.2 SOFLI Seoane,100,,, +1.3 Hardware Freedom Day,150,,, +1.4 FGSL,500,,, +1.5 IFBA,500,,, +2. Swag,0,,, +3. Shipping,0,,, +Total,2400,0,, +Tally,,2400,, +Usage Percentage,,0%,, \ No newline at end of file diff --git a/FY17/archive/proposedannualbudgets/na/famnaproposedbudget.xls.ods b/FY17/archive/proposedannualbudgets/na/famnaproposedbudget.xls.ods new file mode 100644 index 0000000..71ff693 Binary files /dev/null and b/FY17/archive/proposedannualbudgets/na/famnaproposedbudget.xls.ods differ diff --git a/FY17/archive/regional-budget-template.ods b/FY17/archive/regional-budget-template.ods new file mode 100644 index 0000000..cdb1498 Binary files /dev/null and b/FY17/archive/regional-budget-template.ods differ diff --git a/FY17/council.ldg b/FY17/council.ldg new file mode 100644 index 0000000..d8c0d3b --- /dev/null +++ b/FY17/council.ldg @@ -0,0 +1,31 @@ +;---------------------------------------------------------------------- +; Budgets and Movements +;---------------------------------------------------------------------- +~ every 2 years + ; 2015/03/01 Opening Balance + APAC Budget -$11,500.00 + EMEA Budget -$21,650.00 + LATAM Budget -$11,950.00 + NA Budget -$29,400.00 + FUDCon LATAM -$10,000.00 + FUDCon APAC -$15,000.00 + Flock -$75,000.00 + FADs Budget -$15,000.00 + D&I -$6,500.00 + Annual Budget $196,000 + +~ every 2 years + ;2016-12-27 Transfer of excess FUDCon Budget to FADs (proposed) + ; Transfers - proposed + FUDCon APAC $3330.09 ; underspend + FUDCon LATAM -$2197.90 ; overspend covered by FUDCon LATAM + FADs Budget -$1132.19 ; Needed to balance + +;------------------------------------------------------------------------------- +; One-off Transactions +;------------------------------------------------------------------------------- + +2016-12-20 Outreachy 2016 Intern + ; Payment: PO 10100650- 25885 + Expense:Outreachy $6500 + D&I -$6500 diff --git a/FY17/delegations/apac.yaml b/FY17/delegations/apac.yaml deleted file mode 100644 index 4e9cd1e..0000000 --- a/FY17/delegations/apac.yaml +++ /dev/null @@ -1,7 +0,0 @@ -apac_delegates: - treasurer_name: "Mohd Izhar Firdaus Ismail (izhar)" - treasurer_email: "kagesenshi.87@gmail.com" - logistician_name: "PJ Pandit (Pjp)" - logistician_email: "pj.pandit@yahoo.co.in" - storyteller_name: "Gerard Braad - 吉拉德 (gbraad)" - storyteller_email: "me+fedora@gbraad.nl" diff --git a/FY17/delegations/council.yaml b/FY17/delegations/council.yaml deleted file mode 100644 index f1212f7..0000000 --- a/FY17/delegations/council.yaml +++ /dev/null @@ -1,7 +0,0 @@ -council_delegates: - treasurer_name: "Remy DeCausemaker" - treasurer_email: "decause@redhat.com" - logistician_name: "Remy DeCausemaker" - logistician_email: "decause@redhat.com" - storyteller_name: "Remy DeCausemaker" - storyteller_email: "decause@redhat.com" diff --git a/FY17/delegations/emea.yaml b/FY17/delegations/emea.yaml deleted file mode 100644 index a6f1c8b..0000000 --- a/FY17/delegations/emea.yaml +++ /dev/null @@ -1,7 +0,0 @@ -emea_delegates: - treasurer_name: "Zacharias Mitzelos (mitzie)" - treasurer_email: "mitzie@mitzelos.com" - logistician_name: "Jiri Eischmann (sesivany)" - logistician_email: "eischmann@redhat.com" - storyteller_name: "Elijah Hanson (edgates)" - storyteller_email: "pkwesihanson@yahoo.com" diff --git a/FY17/delegations/latam.yaml b/FY17/delegations/latam.yaml deleted file mode 100644 index f56954f..0000000 --- a/FY17/delegations/latam.yaml +++ /dev/null @@ -1,7 +0,0 @@ -latam_delegates: - treasurer_name: "Abdel G. Martínez L." - treasurer_email: "abdel.g.martinez.l@gmail.com" - logistician_name: "Eduardo J. Echeverria A." - logistician_email: "echevemaster@gmail.com" - storyteller_name: "William Moreno Reyes" - storyteller_email: "williamjmorenor@gmail.com" diff --git a/FY17/delegations/na.yaml b/FY17/delegations/na.yaml deleted file mode 100644 index c7b4248..0000000 --- a/FY17/delegations/na.yaml +++ /dev/null @@ -1,7 +0,0 @@ -na_delegates: - treasurer_name: "Andrew Ward" - treasurer_email: "award3535@tds.net" - logistician_name: "Ben Williams" - logistician_email: "vaioof@yahoo.com" - storyteller_name: "Brian Monroe" - storyteller_email: "briancmonroe@gmail.com" diff --git a/FY17/events/README.md b/FY17/events/README.md deleted file mode 100644 index 7013373..0000000 --- a/FY17/events/README.md +++ /dev/null @@ -1,10 +0,0 @@ -Events -====== - -As we have made the budget process more transparent as part of the Budget.next -initiative (http://fedoraproject.org/wiki/Budget.next) this repository has -served as a resource for documents and files related to spending, reporting, -and planning. Fedora Events, a component of the public budget, may also benefit -from the existence of this repository. - -Events tracked here could include: Flock, FUDCon LATAM, FUDCon APAC, and our FADs. diff --git a/FY17/events/flock/todo.md b/FY17/events/flock/todo.md deleted file mode 100644 index b0d2b69..0000000 --- a/FY17/events/flock/todo.md +++ /dev/null @@ -1,43 +0,0 @@ -Proposal -======== -https://fedoraproject.org/wiki/Flock2016-Krakow-proposal - -Tasks -===== - -- create proposal (bex) -- book venue (bex and jmad) -- book evening events (bex and decause) -- book keynotes -- book sponsors (spot) -- establish budget (decause) - -Budget -====== -The total budget for Flock was approved by the Fedora Council to be **$75,000USD** - -The components of budget will include: - -- venue -- Travel -- Evening Event 1 -- Evening Event 2 -- Swag -- Food/meals -- A/V Equipment -- other things not yet on this list - - -Evening Events -============== -http://etherpad.osuosl.org/flock2016-evening - - -Flock Talks Voting -================== -Selection committee members contact jwb@fp.o if you need more information. - - -More details ------------- -This is a working document, and will be updated going forward. diff --git a/FY17/fad.ldg b/FY17/fad.ldg new file mode 100644 index 0000000..467e9c1 --- /dev/null +++ b/FY17/fad.ldg @@ -0,0 +1,108 @@ +;------------------------------------------------------------------------------- +; Budget needs to be fixed see council proposal) +;------------------------------------------------------------------------------- + +~ every 2 years + ; FAD Budgets + FADs Budget $15000 + FADs:Cloud -$3380 + FADs:Design -$5000 + FADs:Docs -$4800 + FADs -$1820 + +~ every 2 years + ; Diversity FAD + FADs $2872 + FADs:Diversity:Travel -$1792 + FADs:Diversity:Lodging -$780 + FADs:Diversity:Meals -$300 + +~ every 2 years + ;2016-12-25 Transfer remaining budget from completed FADs back to pool + FADs:Cloud $407.77 + FADs:Design $46.63 + FADs:Docs $637.87 + FADs -$1092.27 + +~ every 2 years + ;2016-12-27 Transfer of excess FUDCon Budget to FADs (proposed) + ; Transfers - proposed + FADs Budget $1132.19 + FADs -$1132.19 + +;------------------------------------------------------------------------------- +; Below here are best guesses +;------------------------------------------------------------------------------- + +2016-05-31 * Fedora Activity Day travel for Ryan Lerch Approved by Fedora Council) + ; Payment: AU657598 + Expense:Unknown $1,470.34 ; AU657598 AUS $1,882.96. + FADs:Docs -$1,470.34 + +2016-05-31 * Fedora Docs FAD 2016 US681276 + ; Payment: US681276 + Expense:Unknown $717.18 ; Docs FAD Expenses + FADs:Docs -$717.18 + +2016-08-30 * Shaun Docs FAD US722299 + ; Payment: US722299 + Expense:Unknown $1140 + FADs:Docs -$1140 + +2016-08-30 * Fedora Cloud FAD expenses Dinner -US766732 + ; Payment: US766732 + Expense:Unknown $334.17 + FADs:Cloud -$334.17 + +2016-08-30 * Fedora Atomic FAD Catering) US793303 + ; Payment: US793303 + Expense:Unknown $496.86 + FADs:Cloud -$496.86 + +2016-08-30 * Jason Cloud FAD) US907740 + ; Payment: US907740 + Expense:Unknown $1087.85 + FADs:Cloud -$1087.85 + +2016-08-30 * Expense US914969 for Brockmeier, Joe 483.55 USD -US914439 + ; Payment: US914439 + Expense:Unknown $483.55 ; Fedora FAD groupmeals + FADs:Cloud -$483.55 + +2016-08-30 * FAD Airfare for Silas Hensley) IE923694 + ; Payment: IE923694 + Expense:Unknown $834.61 ; Filed by Silas, it's under the 1K limit, but will try to transfer. It's 758 EUR. This was for the Documentation FAD. + FADs:Docs -$834.61 + +;------------------------------------------------------------------------------- +; Has been validated below here +;------------------------------------------------------------------------------- + +2016-10-19 * Kushal Das Reimbursement from Cloud FAD + ; Payment: CC bex:IE1220306 + Expense:Paypal Fee $21.66 + Expense:Taxi $20.79 + Expense:Taxi $44.39 + Expense:Airfare $482.59 + Expense:Currency Conversion Costs $0.37 + FADs:Cloud -$569.80 + +2016-11-16 * Hotel Rooms for Cloud FAD in Jan 2017 + ; Payment: CC bex:IE1241036 + Expense:Lodging $743.4 ; @ 709.64 EUR + Expense:Currency Conversion Costs $10.73 + FADs:Diversity:Lodging -$754.13 + +2016-08-30 * Fedora FAD Design) + Flock (gnokii and riecatnor -US914408 + ; Payment: US914408 + Expense:Airfare $2755.33 ; Categories are aggregated across all related transactions + Expense:Lodging $821.03 ; Categories are aggregated across all related transactions + Expense:Travel $474.14 ; Categories are aggregated across all related transactions + Expense:Food $685.28 ; Categories are aggregated across all related transactions + FADs:Design -$4735.78 + +2016-08-16 * Fedora Design FAD xfer Mo Duffy -US957354 + ; Payment: US957354 + Expense:Airfare $217.59 ; Categories are aggregated across all related transactions + FADs:Design -$217.59 + diff --git a/FY17/fedora.ledger b/FY17/fedora.ledger new file mode 100644 index 0000000..904d23e --- /dev/null +++ b/FY17/fedora.ledger @@ -0,0 +1,4 @@ +include validator.ledger + + +include *.ldg diff --git a/FY17/flock.ldg b/FY17/flock.ldg new file mode 100644 index 0000000..b6912a8 --- /dev/null +++ b/FY17/flock.ldg @@ -0,0 +1,166 @@ +;------------------------------------------------------------------------------- +; uncleared transactions are not in the master sheet +;------------------------------------------------------------------------------- + +;------------------------------------------------------------------------------- +;These are the non-USD invoices I know of - they need to be updated to reflect no VAT +;------------------------------------------------------------------------------- + +2016-08-30 Purchase Requisition 7484 for Machova, Dana 7,505.03 EUR), (Account Code:411.708.764400.000.000.00.537.0000.0000), Vendor/Location :STER EWA BIGOSZ I PIOTR WISNIEWSKI SPOLK/KRAKOW - IE7484 + ; Meeting catering at FLOCK 7,505.03 EUR) - 10000 PLN ; 22800 PLN + ; This appears to be the 10000 PLN only + ; Payment: IE7484 + Expense:Entertainment $3284 ; Cruise and Dinner + Flock -$3284 + +2016-08-30 Expense US918509 for Brockmeier, Joe 125.00 USD) sched.org payment - US918509 + ; Payment: US918509 + Expense:Conference Supplies $125 + Flock -$125 + +2016-08-30 Purchase Requisition 7466 for Machova, Dana 11,437.20 EUR), (Account Code:411.708.764400.000.000.00.680.0000.0000), Vendor/Location :Lider Hotel Sp. z o.o./KRAKOW - IE7466 + ; Payment: IE7466 + ; assuming this is 51750 PLN on 2016-07-04 + ; Y17Q2 additional payment for catering and conference rooms at Flock conference in Krakow higher price is due to additional 100 people); 11,437.20 EUR + Expense:Conference Space $3504 ; 14400 PLN + Expense:Conference Space $633 ; 2600 PLN - extra tables + Expense:Internet $2604 ; 10700 PLN - extra bandwidth + Expense:Food $5851 ; 24050 PLN - Lunch partial) + Flock -$12592 + +2016-08-30 Purchase Requisition 7483 for Machova, Dana 7,665.20 EUR), (Account Code:411.708.764400.000.000.00.537.0000.0000), Vendor/Location :Browar Lubicz Sp. z o.o./KRAKOW - IE7483 + ; Meeting catering at FLOCK 7,665.20 EUR + ; This might be both payments of 22383 & 14922 PLN + ; Payment: IE7483 + Expense:Entertainment $8440 + Flock -$8440 + +2016-08-30 Purchase Requisition 7507 for Machova, Dana 1,700.00 EUR), (Account Code:411.708.764400.000.000.00.537.0000.0000), Vendor/Location :City Tours GmbH - Deutschland/DUISBURG - IE7507 + ; FY17Q2 - bus service - relating to the Flock conference in Krakow - 1700 EU + ; Payment: IE7507 + Expense:Entertainment $1900 ; inter-city transport Tour and Cruise) + Flock -$1900 + +2016-08-30 Purchase Requisition 7623 for Mazurkovicova, Alzbeta Account Code:411.708.712500.000.000.00.680.0000.0000), Vendor/Location :ROZSIVAL TRAVEL - IE7623 + ; Payment: IE7623 + Expense:Travel $1460 ; 1,295.00 EUR), chartered transport from Brno to Krackov for FLOCK + Flock -$1460 + +2016-08-30 Additional Hotel Payments + ; 51750 PLN on 2016-07-04 already in flock.ldg + ; 2016-01-26 22680 PLN + ; 2016-07-18 28880 PLN + ; Final Bill 30305 PLN + ; Payment: Missing + Expense:Entertainment $71 ; 290 PLN - hotel room for Retro-Arcade people + Expense:Entertainment $282 ; 1160 PLN - hotel room for Board Games provider + Expense:Food $6326 ; 26000 PLN Coffee Breaks) + Expense:Food $8747 ; 35950 PLN Lunch balance) + Expense:Lodging $4493 ; 18465 PLN Various Funded people + Flock -$19919 + +2016-08-30 MPK Bus + ; Transport for Brewery + ; Payment: Missing + Expense:Entertainment $219 ; 900 PLN + Flock -$219 + +2016-08-30 Tour Guides + ; Payment: Missing + Expense:Entertainment $292 ; 1200 PLN + Flock -$292 + +2016-08-30 DKIG + ; Payment: Missing + Expense:Entertainment $195 ; 800 PLN Retro Arcade + Flock -$195 + +2016-08-30 Purchase Requisition 7484 for Machova, Dana 7,505.03 EUR), (Account Code:411.708.764400.000.000.00.537.0000.0000), Vendor/Location :STER EWA BIGOSZ I PIOTR WISNIEWSKI SPOLK/KRAKOW - IE7484 + ; Meeting catering at FLOCK 7,505.03 EUR) - 10000 PLN ; 22800 PLN + ; This is the missing 22800 PLN only + ; Payment: Missing + Expense:Entertainment $5561 ; Cruise and Dinner + Flock -$5561 + +;------------------------------------------------------------------------------- +; Below here needs to be validated for details +;------------------------------------------------------------------------------- + +2016-08-30 * Expense US918526 for Brockmeier, Joe 1,629.76 USD) FLock airfare - US918526 + ; Payment: US918526 + Expense:Unknown $1629.76 + Flock -$1629.76 + +2016-08-30 * Tom Flock) US922247 + ; Payment: US922247 + Expense:Unknown $1937.76 + Flock -$1937.76 + +2016-08-30 * Expense US936974 for Brockmeier, Joe 227.48 USD - US936974 + ; Payment: US936974 + Expense:Unknown $227.48 ; PayPal Reimbursement for Bhagyashree Padalkar + Flock -$227.48 + +2016-08-30 * Fedora Flock badges - IE947775 + ; Payment: IE947775 + Expense:Unknown $643 + Flock -$643 + +2016-08-30 * Mariia Leonova Flock Travel - IE957700 + ; Payment: IE957700 + Expense:Unknown $464.6 ; 415.92 EUR + Flock -$464.6 + +2016-08-30 * Tom Flock travel - US955249 + ; Payment: US955249 + Expense:Unknown $557.33 + Flock -$557.33 + +2016-08-30 * Flock booklet Tiskarna v Dubi Supplier - + ; Payment: Direct + Expense:Unknown $267.39 ; Supplier: Tiskarna v Dubi 16000736) Amount: 6,413.01 CZK + Flock -$267.39 + +2016-08-30 * Flock travel sponsored Dominik Perpeet - IE964659 + ; Payment: IE964659 + Expense:Unknown $232.21 ; 206.01 EUR + Flock -$232.21 + +2016-08-30 * Expense US941554 for Suehle, Ruth 651.89 USD - US941554 + ; Payment: US941554 + Expense:Unknown $651.89 ; flock + Flock -$651.89 + +2016-11-30 * Expense US974285 for Brockmeier, Joe 291.24 USD - US974285 + ; Payment: US974285 + Expense:Unknown $291.24 ; Flock travel related expenses + Flock -$291.24 + +2016-11-30 * Expense US974301 for Brockmeier, Joe 777.09 USD - US974301 + ; Payment: US974301 + Expense:Unknown $777.09 ; Flock travel related expenses on behalf of others + Flock -$777.09 + +2016-11-30 * Tom Flock) US1012598 + ; Payment: US1012598 + Expense:Unknown $7.54 + Flock -$7.54 + +;------------------------------------------------------------------------------- +; Below here has been validated +;------------------------------------------------------------------------------- + +2016-08-16 * Fedora Design FAD xfer Mo Duffy -US957354 - Flock Flight cost share + ; Payment: US957354 + Expense:Airfare $1554.87 ; Categories are aggregated across all related transactions + Flock -$1554.87 + +2016-08-16 * Additional Flock costs xfer Mo Duffy - US914968 + ; Payment: US914968 + Expense:Airfare $1057.85 ; Categories are aggregated across all related transactions + Flock -$1057.85 + +2016-08-30 Airfare for lots of people + ; Payment: Missing + Expense:Airfare $16996.78 ; Multiple people + Flock -$16996.78 diff --git a/FY17/fudcon-apac.ldg b/FY17/fudcon-apac.ldg new file mode 100644 index 0000000..601cf14 --- /dev/null +++ b/FY17/fudcon-apac.ldg @@ -0,0 +1,215 @@ +2016-10-19 * Mohan Prakash + ; Payment: CC bex:IE1220329 + Expense:Airfare $478 + FUDCon APAC -$478 + +2016-11-22 * Siddesh Poyarekar + ; Payment: CC bex:IE1257998 + Expense:Airfare $679 + FUDCon APAC -$679 + +2016-11-22 * Estu Fardani + ; Payment: CC bex:IE1257998 + Expense:Airfare $295.72 + FUDCon APAC -$295.72 + +2016-10-14 * Robert Mayr Airfare + ; Payment: CC bex:IE1220329 + Expense:Airfare $636.92 + FUDCon APAC -$636.92 + +2016-10-19 * Parag Nemade + ; Payment: CC bex:IE1220329 + Expense:Airfare $626.65 + FUDCon APAC -$626.65 + +2016-10-22 * Sayan Chowdhury + ; Payment: Reimb bex:IE1238771 + Expense:Airfare $671.48 + FUDCon APAC -$671.48 + +2016-11-22 * Alex Eng + ; Payment: CC bex:IE1257998 + Expense:Airfare $678.37 + FUDCon APAC -$678.37 + +2016-11-22 * Noriko Mizumoto + ; Payment: CC bex:IE1257998 + Expense:Airfare $678.37 + FUDCon APAC -$678.37 + +2016-10-22 * Sumantro Mukherjee + ; Payment: Reimb bex:IE1238771 + Expense:Airfare $477.51 + FUDCon APAC -$477.51 + +2016-10-22 * Anwesha Das + ; Payment: Reimb bex:IE1238771 + Expense:Airfare $671.66 + FUDCon APAC -$671.66 + +2016-10-22 * Kushal Das + ; Payment: Reimb bex:IE1238771 + Expense:Airfare $671.66 + FUDCon APAC -$671.66 + +2016-11-06 * Invoice for Venue - ticket 711 + ; Payment: CC bex:IE1241028 + Expense:Venue $1039.3 + FUDCon APAC -$1039.30 + +2016-10-29 * Kanika Murarka + ; Payment: Reimb bex:IE1238771 + Expense:Airfare $679.88 + FUDCon APAC -$679.88 + +2016-11-02 * Airport Sign + ; Payment: Reimb bex:IE1238771 + Expense:Other $0.5 + FUDCon APAC -$0.50 + +2016-11-04 * Water and supplies – no receipts + ; Payment: Reimb bex:IE1238771 + Expense:Food $7.25 + FUDCon APAC -$7.25 + +2016-11-05 * Water + ; Payment: Reimb bex:IE1238771 + Expense:Food $7.5 + FUDCon APAC -$7.5 + +2016-11-05 * Group Lunch + ; Payment: Reimb bex:IE1238771 + Expense:Food $36 + FUDCon APAC -$36 + +2016-11-05 * Group Breakfast + ; Payment: Reimb bex:IE1238771 + Expense:Food $38.5 + FUDCon APAC -$38.5 + +2016-11-06 * Tuk Tuk – Food Delivery rainy days are always making me sad) + ; Payment: Reimb bex:IE1238771 + Expense:Food $2.5 + FUDCon APAC -$2.5 + +2016-11-06 * Group Lunch + ; Payment: Reimb bex:IE1238771 + Expense:Food $38.75 + FUDCon APAC -$38.75 + +2016-11-06 * Group Breakfast 3 receipts) + ; Payment: Reimb bex:IE1238771 + Expense:Food $50.5 + FUDCon APAC -$50.5 + +2016-11-07 * Group Breakfast + ; Payment: Reimb bex:IE1238771 + Expense:Food $35.75 + FUDCon APAC -$35.75 + +2016-11-02 * Taxi – Airport to Hotel + ; Payment: Reimb bex:IE1238771 + Expense:Other $10 + FUDCon APAC -$10 + +2016-11-03 * Taxi – Airport to Hotel + ; Payment: Reimb bex:IE1238771 + Expense:Other $11 + FUDCon APAC -$11 + +2016-11-03 * Tuk Tuk – Airport to Hotel + ; Payment: Reimb bex:IE1238771 + Expense:Other $16 + FUDCon APAC -$16 + +2016-11-03 * Tuk Tuk – Airport to Hotel + ; Payment: Reimb bex:IE1238771 + Expense:Other $16 + FUDCon APAC -$16 + +2016-11-03 * Cake for Noriko's BDAY + ; Payment: CC bex:IE1241028 + Expense:Other $14.8 + FUDCon APAC -$14.8 + +2016-11-04 * Tuk Tuk – Airport to Hotel + ; Payment: Reimb bex:IE1238771 + Expense:Other $16 + FUDCon APAC -$16 + +2016-11-04 * APAC Group Dinner + ; Payment: Reimb bex:IE1238771 + Expense:Food $55 + FUDCon APAC -$55 + +2016-11-05 * APAC FUDCon T-shirts + ; Payment: Reimb bex:IE1238771 + Expense:T-Shirts $376 + FUDCon APAC -$376 + +2016-11-06 * Bus to/from FUDPub + ; Payment: Reimb bex:IE1238771 + Expense:FUDPub $35 + FUDCon APAC -$35 + +2016-11-06 * APAC Hotel + ; Payment: Reimb bex:IE1238771 + Expense:Hotel $864 + FUDCon APAC -$864 + +2016-11-07 * Hotel Deposit – to be collected by Ryan Lerch + ; Payment: Reimb bex:n-a + Expense:Hotel $100 + FUDCon APAC -$100 + +2016-11-14 * Ticket 713 FUDPub) + ; Payment: CC bex:IE1241028 + Expense:FUDPub $623.7 + FUDCon APAC -$623.7 + +2016-11-16 * Refund of Hotel Deposit received from Ryan Kathryn) Lerch + ; Payment: Reimb bex:n-a + Expense:Hotel -$100 + FUDCon APAC $100 + +2016-11-16 * Fee refund for Ryan Kathryn) Lerch – he collected the hotel deposit back as he left last and he sent it to me via Paypal + ; Payment: Reimb bex:IE1238771 + Expense:Hotel $3.2 + FUDCon APAC -$3.2 + +2016-12-01 * Zongyuan Tommy) He + ; Payment: CC bex:IE1257998 + Expense:Airfare $487.16 + FUDCon APAC -$487.16 + +2016-11-28 * Gerad Braad + ; Payment: CC bex:IE1257998 + Expense:Airfare $360.51 + FUDCon APAC -$360.51 + +2016-12-01 * Mohan Prakash + ; Payment: CC bex:IE1257998 + Expense:Airfare $125.39 ; Additional Airfare + FUDCon APAC -$125.39 + +2016-11-16 Currency Conversion Fees - RH CC bex is in EUR not USD + ; Payment: CC bex:IE1220329 + Expense:Currency Conversion Costs -$0.68 ; yes, minus + FUDCon APAC $0.68 + +2016-11-21 Currency Conversion Fees - RH Reimb bex is in CZK not USD + ; Payment: Reimb bex:IE1238771 + Expense:Currency Conversion Costs $58.83 + FUDCon APAC -$58.83 + +2016-11-23 Currency Conversion Fees - RH CC bex is in EUR not USD + ; Payment: CC bex:IE1241028 + Expense:Currency Conversion Costs -$0.76 ; yes, minus + FUDCon APAC $0.76 + +2016-12-05 Currency Conversion Fees - RH CC bex is in EUR not USD + ; Payment: CC bex:IE1257998 + Expense:Currency Conversion Costs $96.99 + FUDCon APAC -$96.99 + diff --git a/FY17/fudcon-latam.ldg b/FY17/fudcon-latam.ldg new file mode 100644 index 0000000..6632308 --- /dev/null +++ b/FY17/fudcon-latam.ldg @@ -0,0 +1,175 @@ +2016-10-08 * Ticket 672 antoniosalles – Chile) + ; Payment: Reimb bex:IE1220254 + Expense:Airfare $260.05 + FUDCon LATAM -$260.05 + +2016-10-08 * Ticket 667 itamarjp – Brazil) + ; Payment: Reimb bex:IE1220254 + Expense:Airfare $569.01 + FUDCon LATAM -$569.01 + +2016-10-11 ribeiro@fedoraproject.org - Brazil + ; Payment: Unknown + Expense:Airfare $1107.09 + FUDCon LATAM -$1107.09 + +2016-10-11 mayorga@fedoraproject.org - Nicaragua + ; Payment: Unknown + Expense:Airfare $902.2 + FUDCon LATAM -$902.2 + +2016-10-11 asoliard@fedoraproject.org - Argentina + ; Payment: Unknown + Expense:Airfare $782.79 + FUDCon LATAM -$782.79 + +2016-10-11 josereyesjdi@fedoraproject.org - Panamá + ; Payment: Unknown + Expense:Airfare $808.37 + FUDCon LATAM -$808.37 + +2016-10-11 lbazan@fedoraproject.org - Panamá + ; Payment: Unknown + Expense:Airfare $808.37 + FUDCon LATAM -$808.37 + +2016-10-11 sophiekovalevsky@fedoraproject.org - Panamá + ; Payment: Unknown + Expense:Airfare $605.56 + FUDCon LATAM -$605.56 + +2016-10-11 echevemaster@fedoraproject.org - Colombia + ; Payment: Unknown + Expense:Airfare $453.09 + FUDCon LATAM -$453.09 + +2016-10-11 yograterol@fedoraproject.org - Colombia + ; Payment: Unknown + Expense:Airfare $453.09 + FUDCon LATAM -$453.09 + +2016-10-11 jmlaya@fedoraproject.org - Colombia + ; Payment: Unknown + Expense:Airfare $453.09 + FUDCon LATAM -$453.09 + +2016-10-12 * Bus JUL→Puno group of 7) + ; Payment: Reimb bex:IE1238723 + Expense:Other $7.5 + FUDCon LATAM -$7.5 + +2016-10-13 * Ticket 671 wolnei – Brazil) + ; Payment: Reimb bex:IE1238723 + Expense:Airfare $518.24 + FUDCon LATAM -$518.24 + +2016-10-13 * FUDCon Group Lunch 3 receipts) + ; Payment: CC bex:IE1220327 + Expense:Food $217.46 + FUDCon LATAM -$217.46 + +2016-10-13 * FUDCon Group Dinner RH Contribution + ; Payment: CC bex:IE1220327 + Expense:Food $33.58 + FUDCon LATAM -$33.58 + +2016-10-14 * 6 people airport xfer JUL→Puno + ; Payment: Reimb bex:IE1238723 + Expense:Other $18.38 + FUDCon LATAM -$18.38 + +2016-10-14 * FUDCon LATAM) Lunch + ; Payment: CC bex:IE1220327 + Expense:Food $190.81 + FUDCon LATAM -$190.81 + +2016-10-15 * Airport xfer + ; Payment: Reimb bex:IE1238723 + Expense:Other $9.19 + FUDCon LATAM -$9.19 + +2016-10-15 * Airport xfer + ; Payment: Reimb bex:IE1238723 + Expense:Other $24.5 + FUDCon LATAM -$24.5 + +2016-10-15 * Shipping for T-shirts + ; Payment: Reimb bex:IE1238723 + Expense:T-Shirts $58.19 + FUDCon LATAM -$58.19 + +2016-10-15 * T-shirts 2 receipts of 750 PEN) + ; Payment: Reimb bex:IE1238723 + Expense:T-Shirts $459.4 + FUDCon LATAM -$459.4 + +2016-10-15 * FUDCon LATAM) Lunch + ; Payment: CC bex:IE1220327 + Expense:Food $195.05 + FUDCon LATAM -$195.05 + +2016-10-15 * Ticket 679 bernardoha) + ; Payment: Reimb bex:IE1238723 + Expense:Airfare $75 + FUDCon LATAM -$75 + +2016-10-15 * Ticket 683 Gonzalo – lorddemon) + ; Payment: Reimb bex:IE1238723 + Expense:Bus $77 + FUDCon LATAM -$77 + +2016-10-16 * Ticket 690 Barto – Freddy) + ; Payment: Reimb bex:IE1238723 + Expense:Bus $18 + FUDCon LATAM -$18 + +2016-10-17 * Ticket 674 dgilmore) + ; Payment: CC bex:IE1220327 + Expense:Airfare $865.79 + FUDCon LATAM -$865.79 + +2016-10-18 * Hotel for LATAM + ; Payment: Reimb bex:IE1238723 -$1314.21 ; Part of larger transaction for $1314.21 + + Expense:Lodging $1314.21 + FUDCon LATAM -$1314.21 + +2016-11-22 * Ticket 687 rigerbersol) via Paypal + ; Payment: CC bex:IE1258006 + Expense:Bus $20.14 + FUDCon LATAM -$20.14 + +2016-09-20 yulytas - Peru + ; Payment: Unknown + Expense:Airfare $416.55 + FUDCon LATAM -$416.55 + +2016-09-20 ZodiacFireworks - Peru + ; Payment: Unknown + Expense:Airfare $416.55 + FUDCon LATAM -$416.55 + +2016-09-07 Berroteran Da Silva/Omar Dani + ; Payment: Unknown + Expense:Airfare $38 + FUDCon LATAM -$38 + +2016-11-16 Currency Conversion Fees - RH CC bex is in EUR not USD + ; Payment: CC bex:IE1220327 + Expense:Currency Conversion Costs $7.72 + FUDCon LATAM -$7.72 + +2016-11-16 Currency Conversion Fees - RH Reimb bex is in CZK not USD + ; Payment: Reimb bex:IE1220254 + Expense:Currency Conversion Costs -$20.94 ; yes minus + FUDCon LATAM $20.94 + +2016-11-21 Currency Conversion Fees - RH Reimb bex is in CZK not USD + ; Payment: Reimb bex:IE1238723 + Expense:Currency Conversion Costs $33.82 + FUDCon LATAM -$33.82 + +2016-11-22 Currency Conversion Fees - RH CC bex is in EUR not USD + ; Payment: CC bex:IE1258006 + Expense:Currency Conversion Costs $1.05 + FUDCon LATAM -$1.05 + diff --git a/FY17/na.ldg b/FY17/na.ldg new file mode 100644 index 0000000..ae625c4 --- /dev/null +++ b/FY17/na.ldg @@ -0,0 +1,216 @@ +~ every 2 years + ; Budget + NA Budget $29400 + NA:Q1 -$7350 + NA:Q2 -$7350 + NA:Q3 -$7350 + NA:Q4 -$7350 + NA:stamps.com -$0 + NA:Unallocated -$0 + +2016-12-09 * Paypal JPSANDYS + ; Payment: CC-NA + Expense:Travel $431.84 + NA:Q4 -$431.84 + +2016-12-12 PAYPAL *JBWILLIA + ; Payment: CC-NA + Expense:Travel -$546.04 + NA:Unallocated $546.04 + +2016-12-20 * Paypal VAIOOF + ; Payment: CC-NA + Expense:Travel $546.14 + NA:Q4 -$546.14 + +2016-12-20 * Paypal MIKEDEP333 + ; Payment: CC-NA + Expense:Travel $646.08 + NA:Q4 -$646.08 + +2016-06-13 SHERATON CHARLOTTE AIRPOR + ; Payment: CC-NA + Expense:Travel $352.68 + NA:Q2:SE Linux Fest -$352.68 + +2016-06-13 SPRINGHILL SUITES + ; Payment: CC-NA + Expense:Travel $339.98 + NA:Q2 -$339.98 + +2016-06-13 PAYPAL *JFLORY7 JFLORY7 + ; Payment: CC-NA + Expense:Travel $51.95 + NA:Q2 -$51.95 + +2016-06-14 PAYPAL *AVJAWARD AVJAWA + ; Payment: CC-NA + Expense:Travel $66 + NA:Q2 -$66 + +2016-06-14 PAYPAL *VAIOOF VAIOOF + ; Payment: CC-NA + Expense:Travel $22.95 + NA:Q2 -$22.95 + +2016-06-14 PAYPAL *MIKEDEP333 MIKE + ; Payment: CC-NA + Expense:Travel $18.21 + NA:Q2 -$18.21 + +2016-06-18 PAYPAL *STRIKER + ; Payment: CC-NA + Expense:Travel $141.66 + NA:Q2 -$141.66 + +2016-07-01 LINUX EXPO + ; Payment: CC-NA + Expense:Travel $500 + NA:Q2 -$500 + +2016-07-15 PAYPAL *JUGGLER + ; Payment: CC-NA + Expense:Travel $26.01 + NA:Q2 -$26.01 + +2016-08-11 OHIO LINUXFEST CORPO + ; Payment: CC-NA + Expense:Travel $750 + NA:Q2 -$750 + +2016-08-12 STICKER MULE + ; Payment: CC-NA + Expense:Travel $950 + NA:Q2 -$950 + +2016-09-12 LINUX EXPO + ; Payment: CC-NA + Expense:Conference $500 + NA:Q2:SEAGul -$500 + +2016-09-28 PAYPAL *JFLORY7 + ; Payment: CC-NA + Expense:Travel $414.08 + NA:Q3 -$414.08 + +2016-09-28 PAYPAL *RUBYOFOZ + ; Payment: CC-NA + Expense:Travel $85.18 + NA:Unallocated -$85.18 + +2016-10-11 PAYPAL *JBWILLIA + ; Payment: CC-NA + Expense:Travel $546.04 + NA:Unallocated -$546.04 + +2016-09-05 * UPS + ; Payment: CC-NA + Expense:Postage $117.80 + NA:Q3:Postage -$117.80 + +2016-09-05 * UPS + ; Payment: CC-NA + Expense:Postage $37.84 + NA:Q3:Postage -$37.84 + +2016-07-26 DVDs - Merch Hero + ; Payment: Direct + Expense:Swag:DVDs $2048.80 + NA:Q2 -$2048.80 + +2016-11-03 DVDs - Merch Hero + ; Ticket: https://fedorahosted.org/famna/ticket/158 + ; Payment: PO 25027 + Expense:Swag:DVDs $2048.80 + NA:Q4 -$2048.80 + +2016-05-31 Expense US706356 for Brockmeier, Joe 128.93 USD travel for Fedora ambassador Williams - US706356 + ; Payment: US706356 + Expense:Unknown $128.93 + NA:Q1 -$128.93 + +2016-08-30 Purchase Requisition 23151 for Madriaga, Jennifer 2,028.25 USD, Vendor/Location :MERCH HERO/Salt Lake - US23151 + ; Payment: US23151 + Expense:Unknown $2028.25 ; Fedora CDs for Ambassadors + NA:Q2 -$2028.25 + +2016-08-30 Jon Disnard Ambassador attending OSCON for Fedora - US914382 + ; Payment: US914382 + Expense:Unknown $1248.04 ; Cost transfer - internal RHT employee attending OSCON for Fedora ambassadors. + NA:Q2 -$1248.04 + +2016-11-30 LFNW Sponsorship NA Ambassadors - + ; Payment: CC-NA + Expense:Unknown $2000 ; Paid by Jen M. by CC / PayPal. + NA:Q3 -$2000 + +2016-05-31 John Rose Fedora Corp Card - April + ; Payment: CC-NA + Expense:Unknown $249.79 + NA:Q1 -$249.79 + +2016-05-31 Fedora Ambassadors May: Rose - + ; Payment: CC-NA + Expense:Unknown $130.62 ; John Rose Fedora corp card + NA:Q1 -$130.62 + +2016-08-30 Fedora Ambassador Card July: Rose - + ; Payment: CC-NA + Expense:Unknown $11.12 + NA:Q2 -$11.12 + +2016-11-30 John Rose Community Card Oct. - + ; Payment: CC-NA + Expense:Unknown $117.2 + NA:Q3 -$117.2 + +;------------------------------------------------------------------------------- +; postage charges +;------------------------------------------------------------------------------- +2016-05-31 * Postage US651413 + ; Payment: US651413 + Expense:stamps.com $15.99 + NA:stamps.com -$15.99 + +2016-05-31 * Postage US643701 + ; Payment: CC-NA + Expense:stamps.com $15.99 + NA:stamps.com -$15.99 + +2016-08-30 * Expense US968318 for Suehle, Ruth 15.99 USD - US968318 + ; Payment: CC-NA + Expense:stamps.com $15.99 ; Fedora postage + NA:stamps.com -$15.99 + +2016-11-30 * Expense US1054446 for Suehle, Ruth 15.99 USD - US1054446 + ; Payment: CC-NA + Expense:stamps.com $15.99 ; Fedora postage + NA:stamps.com -$15.99 + +2016-08-30 * Expense for Suehle, Ruth - USUS914392 + ; Payment: CC-NA + Expense:stamps.com $31.98 ; Fedora postage + NA:stamps.com -$31.98 + +2016-11-30 * Expense US1240277 for Suehle, Ruth 115.99 USD - US1240277 + ; Payment: CC-NA + Expense:stamps.com $15.99 ; Fedora postage + Expense:postage $100 ; Fedora postage + NA:stamps.com -$115.99 + +2016-05-31 * Expense for Suehle, Ruth Fedora postage - US701627 + ; Payment: CC-NA + Expense:stamps.com $31.98 ; based on estimation - not available data + NA:stamps.com -$31.98 + +2016-05-31 * US567263 Postage + ; Payment: US567263 + Expense:stamps.com $15.99 ; based on estimation - not available data + NA:stamps.com -$15.99 + +2016-12-20 Final two months of stamps.com + ; paid by nb and reimbursed + ; Payment: IE1275580 + Expense:stamps.com $31.98 + Expense:Paypal Fee $1.55 + NA:stamps.com -$33.53 diff --git a/FY17/pending.ldg b/FY17/pending.ldg new file mode 100644 index 0000000..218dcbd --- /dev/null +++ b/FY17/pending.ldg @@ -0,0 +1,24 @@ +;------------------------------------------------------------------------------- +; Transactions to show encumbered budgets +;------------------------------------------------------------------------------- + + +2016-12-20 Diversity FAD Encumberance + Expense:Encumberance $1792 + FADs:Diversity:Travel -$1792 + Expense:Encumberance $300 + FADs:Diversity:Meals -$300 + +2017-01-09 NA Encumberance + NA:Q4 -$1000 ; :WiCHacks 25-26 Feb 2017 + NA:Q4 -$2000 ; BrickHack 11-12 Feb 2017 + NA:Q4 -$1500 ; Banners/Table cloths + Expense:Encumberance + +;------------------------------------------------------------------------------- +; Pending Transactions +;------------------------------------------------------------------------------- + +2016-12-31 Refund from stamps.com of unspent balance to nb - account closed on 9 Dec 2016 + Expense:Postage -$85.17 + NA:stamps.com $85.17 diff --git a/FY17/proposedannualbudgets/apac/apac.txt b/FY17/proposedannualbudgets/apac/apac.txt deleted file mode 100644 index e69de29..0000000 --- a/FY17/proposedannualbudgets/apac/apac.txt +++ /dev/null diff --git a/FY17/proposedannualbudgets/emea/FedoraEMEABudgetFY2017-Budget.csv b/FY17/proposedannualbudgets/emea/FedoraEMEABudgetFY2017-Budget.csv deleted file mode 100644 index 47eeb5f..0000000 --- a/FY17/proposedannualbudgets/emea/FedoraEMEABudgetFY2017-Budget.csv +++ /dev/null @@ -1,79 +0,0 @@ -Expense,Planned,Adjusted,Actual,Tickets/Recipts -,,Quarter 1 (March-May 2016),, -Events,,,, -Mozilla & Fedora Activity Day,$80,,, -PyCon SK,$400,,,"#551, #552 (~180$, unconfirmed)" -Open Source Weekend,$50,,, -Chemnitzer Linux Tage 2016,"$1,300",,,"#549(~210 euros unconfirmed), #559(~43$ unconfirmed)" -3D Expo,$120,,, -LinuxWochen Vienna,$500,`,, -Fosscomm,$400,,, -DORS/CLUC,$700,,,#558: Travel for Jona -OSCAL,$800,,,#557: Travel for Jiri -,"$4,350",$0,$0.00, -SWAG,,,, -Booth Material Initiative,"$1,000",,, -Other Swag,"$2,000",,, -,"$3,000",$0,$0.00, -Shipping,,,, -Swag & Media shipping,$500,,, -,$500,$0,$0.00, -,,,, -Total for Quarter,"$7,850",$0,$0.00, -,,,, -,,Quarter 2 (June-August 2015),, -Events,,,, -FrOSCon,"$1,500",,, -EuroPython,"$2,000",,, -Flock 2016,$800,,, -,"$4,300",$0,$0.00, -Swag,,,, -F24 Media production,"$1,000",,, -Other Swag,"$1,200",,, -,"$2,200",$0,$0.00, -Shipping,,,, -Swag & Media Shipping,"$1,300",,, -,"$1,300",$0,$0.00, -,,,, -Total for Quarter,"$7,800",$0,$0.00, -,,,, -,,Quarter 3 (September-November 2015),, -Events,,,, -LinuxCon Europe,"$2,000",,, -Bar Camp Manchester,$800,,, -FSCONS,"$1,400",,, -OSOL Conference,$500,,, -BalCCon_2k16,$800,,, -SFK16,$300,,, -PyCon CZ ,$200,,, -LinuxDays Prague,$50,,, -,"$6,050.00",$0,$0.00, -Swag,,,, -Other Swag,"$1,200",,, -,"$1,200",$0,$0.00, -Shipping,,,, -Swag & Media shipping,$400,,, -,$400,$0,$0.00, -,,,, -Total for Quarter,"$7,650",$0,$0.00, -,,,, -,,Quarter 4 (December 2015 - February 2016),, -Events,,,, -Chaos Communication Congress,"$2,500",,, -FOSDEM,"$3,000",,, -Fedora 25 Release Parties,$150,,, -,"$5,650",$0,$0.00, -Swag,,,, -F25 media production,"$1,000",,, -Other Swag,"$1,800",,, -,"$2,800",$0,$0.00, -Shipping,,,, -Swag & Media shipping,"$1,500",,, -,"$1,500",$0,$0.00, -,,,, -Total for Quarter,"$9,950",$0,$0.00, -,,,, -Total for Fiscal Year,"$33,250",$0,$0.00, -,,,, -% of adjustment,,0.00%,, -Absolute % of adjustment,,0.00%,, \ No newline at end of file diff --git a/FY17/proposedannualbudgets/emea/FedoraEMEABudgetFY2017.ods b/FY17/proposedannualbudgets/emea/FedoraEMEABudgetFY2017.ods deleted file mode 100644 index 7478756..0000000 Binary files a/FY17/proposedannualbudgets/emea/FedoraEMEABudgetFY2017.ods and /dev/null differ diff --git a/FY17/proposedannualbudgets/latam/fy17.csv b/FY17/proposedannualbudgets/latam/fy17.csv deleted file mode 100644 index 887a3fa..0000000 --- a/FY17/proposedannualbudgets/latam/fy17.csv +++ /dev/null @@ -1,8 +0,0 @@ -Quarter,Planned,Actual -Q1,8780,0 -Q2,6600,0 -Q3,5400,0 -Q4,2400,0 -Total,23180,0 -Tally,,23180 -Usage Percentage,,0% \ No newline at end of file diff --git a/FY17/proposedannualbudgets/latam/q1.csv b/FY17/proposedannualbudgets/latam/q1.csv deleted file mode 100644 index bbee072..0000000 --- a/FY17/proposedannualbudgets/latam/q1.csv +++ /dev/null @@ -1,41 +0,0 @@ -Event,Planned,Actual,Tickets,Reports -1. Events,4430,,, -1.1 FLISOL,1630,,, -1.1.1 Peru - Cusco,120,,, -1.1.2 Peru - Puno,120,,, -1.1.3 Peru - Lima,200,,, -1.1.4 Joinville,120,,, -1.1.5 Venezuela,200,,, -1.1.6 Panama,150,,, -1.1.7 CryptoRave,150,,, -1.1.8 Ciudad de Mexico,250,,, -1.1.9 Colombia,200,,, -1.1.10 Bolivia,120,,, -1.2 Fedora 24 Release Party,1250,,, -1.2.1 Peru - Cusco,100,,, -1.2.2 Peru - Puno,100,,, -1.2.3 Peru - Lima,100,,, -1.2.4 Venezuela,100,,, -1.2.5 Nicaragua,100,,, -1.2.6 Panama,100,,, -1.2.7 Uruguay,100,,, -1.2.8 Ciudad de Mexico,250,,, -1.2.9 TESCHA Edo - Mexico,100,,, -1.2.10 Bolivia - La Paz,100,,, -1.2.11 Bolivia - Cochabamba,100,,, -1.3 Foro de Software Libre UCR,800,,, -1.4 Document Freedom Day - Panama,150,,, -1.5 Solisc,500,,, -1.6 Mini Workshop - Uruguay,100,,, -2. Swag,4350,,, -2.1 Nicaragua,620,,, -2.2 Panama,500,,, -2.3 Mexico,650,,, -2.4 Colombia,650,,, -2.5 Bolivia,650,,, -2.6 Peru,680,,, -2.7 Uruguay,600,,, -3. Shipping,0,,, -Total,8780,0,, -Tally,,8780,, -Usage Percentage,,0%,, \ No newline at end of file diff --git a/FY17/proposedannualbudgets/latam/q2.csv b/FY17/proposedannualbudgets/latam/q2.csv deleted file mode 100644 index 165db5d..0000000 --- a/FY17/proposedannualbudgets/latam/q2.csv +++ /dev/null @@ -1,16 +0,0 @@ -Event,Planned,Actual,Tickets,Reports -1. Events,6600,,, -1.1 CONEISC,900,,, -1.2 Fedora Week,100,,, -1.3 Fedora Day,100,,, -1.4 ECSL,1000,,, -1.5 Fedora Day: UIP Panama,100,,, -1.6 Fedora Day: UDI Panama,1000,,, -1.7 FISL 17,2000,,, -1.8 Campus Party 2016 - Mexico,400,,, -1.9 Fedora Meeting Sucre,1000,,, -2. Swag,0,,, -3. Shipping,0,,, -Total,6600,0,, -Tally,,6600,, -Usage Percentage,,0%,, \ No newline at end of file diff --git a/FY17/proposedannualbudgets/latam/q3.csv b/FY17/proposedannualbudgets/latam/q3.csv deleted file mode 100644 index 70b92e8..0000000 --- a/FY17/proposedannualbudgets/latam/q3.csv +++ /dev/null @@ -1,21 +0,0 @@ -Event,Planned,Actual,Tickets,Reports -1. Events,5300,,, -1.1 Software Freedom Day,650,,, -1.1.1 Cusco,100,,, -1.1.2 San Cristobal,50,,, -1.1.3 Nicaragua,100,,, -1.1.4 Mexico,150,,, -1.1.5 Panama,150,,, -1.1.6 La Paz,100,,, -1.2 Linux Day,150,,, -1.3 FTSL,500,,, -1.4 Latinoware,2000,,, -1.5 Hackmeeting - Mexico,500,,, -1.6 Fedora Day - Colombia,250,,, -1.7 Conasol - Bolivia,600,,, -1.8 Hackmeeting - Bolivia,650,,, -2. Swag,100,,, -2.1 Colombia,100,,, -Total,5400,0,, -Tally,,5400,, -Usage Percentage,,0%,, \ No newline at end of file diff --git a/FY17/proposedannualbudgets/latam/q4.csv b/FY17/proposedannualbudgets/latam/q4.csv deleted file mode 100644 index f201460..0000000 --- a/FY17/proposedannualbudgets/latam/q4.csv +++ /dev/null @@ -1,22 +0,0 @@ -Event,Planned,Actual,Tickets,Reports -1. Events,2400,,, -1.1 Fedora 25 Release Party,1150,,, -1.1.1 Cusco - Peru,100,,, -1.1.2 Puno - Peru,100,,, -1.1.3 Lima - Peru,100,,, -1.1.4 San Cristobal,100,,, -1.1.5 Nicaragua,100,,, -1.1.6 Ciudad de Mexico,250,,, -1.1.7 Panama,100,,, -1.1.8 TESCHA Mexico,100,,, -1.1.9 Bolivia - La Paz,100,,, -1.1.10 Bolivia - Cochabamba,100,,, -1.2 SOFLI Seoane,100,,, -1.3 Hardware Freedom Day,150,,, -1.4 FGSL,500,,, -1.5 IFBA,500,,, -2. Swag,0,,, -3. Shipping,0,,, -Total,2400,0,, -Tally,,2400,, -Usage Percentage,,0%,, \ No newline at end of file diff --git a/FY17/proposedannualbudgets/na/famnaproposedbudget.xls.ods b/FY17/proposedannualbudgets/na/famnaproposedbudget.xls.ods deleted file mode 100644 index 71ff693..0000000 Binary files a/FY17/proposedannualbudgets/na/famnaproposedbudget.xls.ods and /dev/null differ diff --git a/README.md b/README.md index 6352046..ba1814e 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,9 @@ Fedora Budget ============= This repository is where budget data and information is shared publicly | http://pagure.io/fedora-budget + +The Fedora Fiscal Year is from March 1 to February 28. Fiscal years are numbered by the year in which they **end**. For example, the fiscal year from March 1, 2016 to February 28, 2017 is FY17. + +FY16 and FY15 are historical data from before the adoption of ledger. FY17 contains an archive file from before the adoption of ledger. The ledger files are in FY17. + +More details are coming. diff --git a/common/cc-report.sh b/common/cc-report.sh new file mode 100644 index 0000000..384dcbd --- /dev/null +++ b/common/cc-report.sh @@ -0,0 +1,7 @@ +echo $1 +ledger r \ + -f emea.ldg \ + --uncleared \ + --invert \ + --limit "tag('Payment') =~ /CC/" \ + --format '%(format_date(d,"%Y-%m-%d")) Amount: %t\n Payee Note: %P\n%(has_tag("TICKET") ? " Ticket: " : "")%(has_tag("TICKET") ? tag("TICKET") : "")%(has_tag("TICKET") ? "\n" : "")%(has_tag("DESC") ? " Description: " : "")%(has_tag("DESC") ? tag("DESC") : "")%(has_tag("DESC") ? "\n" : "")\n' diff --git a/common/notes.txt b/common/notes.txt new file mode 100644 index 0000000..8170841 --- /dev/null +++ b/common/notes.txt @@ -0,0 +1 @@ +reconfigure expenses to use RH categories diff --git a/common/validator.ledger b/common/validator.ledger new file mode 100644 index 0000000..f9d3278 --- /dev/null +++ b/common/validator.ledger @@ -0,0 +1,36 @@ +account APAC +account EMEA +account LATAM +account NA +account FUDCon LATAM +account FUDCon APAC +account Flock +account FADs +account D&I +account Equity:Red Hat + +commodity $ + +account Expense:Transportation +account Expense:Mileage +account Expense:Fuel +account Expense:Car Rental +account Expense:Parking/Tolls +account Expense:Taxi/Limo +account Expense:Lodging +account Expense:Meals +account Expense:Business Meeting +account Expense:Courier/Shipping +account Expense:Office Supplies +account Expense:Dues/Subscriptions/Books +account Expense:Mobile Phone +account Expense:Internet +account Expense:Late Fees +account Expense:Finance Charges +account Expense:Trade Show +account Expense:Outside Services/Training +account Expense:Employee Relations (flowers) +account Expense:Contributions/Donations +account Expense:Other Marketing Costs +account Expense:On-line Advertising +account Expense:Printing/Reproduction diff --git a/regional-budget-template.ods b/regional-budget-template.ods deleted file mode 100644 index cdb1498..0000000 Binary files a/regional-budget-template.ods and /dev/null differ