This is an automated email from the git hooks/post-receive script.
bex pushed a change to branch master in repository fedora-budget.
from 942b081 Adding budget ticket to NA Q3 budget new f91f476 Added faq about events with costs in mult quarters
The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: docs/faq_budgeting.adoc | 10 ++++++++++ 1 file changed, 10 insertions(+)
This is an automated email from the git hooks/post-receive script.
bex pushed a commit to branch master in repository fedora-budget.
commit f91f476441a720536de6b32bd9a3f04fdc42b708 Author: Brian (bex) Exelbierd bex@pobox.com Date: Tue Jul 11 10:16:05 2017 +0200
Added faq about events with costs in mult quarters --- docs/faq_budgeting.adoc | 10 ++++++++++ 1 file changed, 10 insertions(+)
diff --git a/docs/faq_budgeting.adoc b/docs/faq_budgeting.adoc index 7fdedaf..e451790 100644 --- a/docs/faq_budgeting.adoc +++ b/docs/faq_budgeting.adoc @@ -88,6 +88,16 @@ In this case $53 was moved from events in Quarter 1 to an event in Quarter 3. T
The other option is to just edit the budget entries. This is less preferred as it means you would have to go through the file's history to discover there had been a change.
+What if we have a budget item (event) that has expenses in multiple quarters? +----------------------------------------------------------------------------- + +In Fedora we budget our events and items by the quarter in which they are expected to occur. In general, our budget items are small enough that it won't change anything. Exceptions are large events like Flock. Doing this lets us make one budget entry for something like an event instead of having to make guesses about how much of the expense will fall in each quarter. + +The goal of the budget is to make sure you have roughly allocated your expenses to occur in equal parts year round. There will definitely be exceptions as some things just naturally bunch up and some quarters are low on events/items. However, it should all roughly even out. Therefore we don't need to worry about budgeting the exact costs in each quarter as long as the quarter where the item happens is accurate. + +If we think about an event that will occur during Q3, we consider, from a budget perspective that all costs related to the event will occur in Q3. If we want to see when they really occurred we can look at the date of the associated transactions. This is kind of split brain, but doing it this way prevents us from having to budget the same event in two quarters or leave long non-machine parseable comments. + + What are the best practices or best ideas for Ambassador Regions? -----------------------------------------------------------------
budget-devel@lists.fedoraproject.org
-
git repository hosting