This is an automated email from the git hooks/post-receive script.
bex pushed a change to branch master
in repository fedora-budget.
from f8fed09 Adding quarter separation for LATAM
new 2fe8d1c Adding new budget FAQ
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 | 54 +++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 54 insertions(+)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
Show replies by date
This is an automated email from the git hooks/post-receive script.
bex pushed a commit to branch master
in repository fedora-budget.
commit 2fe8d1c60b9717b86d24cf35e6a6466f6456e531
Author: Brian (bex) Exelbierd <bex(a)pobox.com>
Date: Fri Jul 7 16:02:49 2017 +0200
Adding new budget FAQ
---
docs/faq_budgeting.adoc | 54 +++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 54 insertions(+)
diff --git a/docs/faq_budgeting.adoc b/docs/faq_budgeting.adoc
index 4747ded..7fdedaf 100644
--- a/docs/faq_budgeting.adoc
+++ b/docs/faq_budgeting.adoc
@@ -87,3 +87,57 @@ There are two ways to fix this. Option 1, which is preferred, is to
create anot
In this case $53 was moved from events in Quarter 1 to an event in Quarter 3. The
comments make everything extra clear.
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 are the best practices or best ideas for Ambassador Regions?
+-----------------------------------------------------------------
+
+The budget is here to help everyone plan both the regions and the council.
+Therefore, it is helpful to think of the budget as your "notes about
+the future." Specifically, it is a good idea to immediately put things
+into the budget when they are approved. This way you can see reports of
+how much money you have left to allocate. When spending happens you'll
+be able to see if the budgets were accurate and if there is any overage
+or underspend.
+
+Here is an example, Using LATAM and some ficticious numbers:
+
+```
+~ every 2 years
+ ; Budget
+ LATAM:Unallocated $12000
+ LATAM:Q1 -$4000
+ LATAM:Q2 -$4000
+ LATAM:Q3 -$4000
+ LATAM:Q4 -$4000
+```
+
+The entry above divides the LATAM budget into quarterly budgets.
+Each quarter is broken down as follows
+
+```
+~ every 2 years
+ ; Budget
+ LATAM:Q1 $4000
+ LATAM:Q1:UNSACC LinuxPlaya -$606
+ LATAM:Q1:Cs50xni -$1020
+ LATAM:Q1:Flisol -$750
+ LATAM:Q1:CryptoRave -$0 ; event cancelled
+ LATAM:Q1:SASO Conf -$1000 ; we usually do this - not
yet approved
+ LATAM:Q1:Unallocated ; Leave blank it will
calculate automatically
+```
+
+Here we have broken down a single budget quarter. Three events have
+been voted on and approved by the LATAM ambassadors. These are UNSACC
+LinuxPlaya, Cs50xni, and Flisol.
+
+CryptoRave was originally approved (or considered) but then the event
+got canceled or we decided not to participate. Leaving the note here
+like this makes it easy to remember the event in the future or in next
+year's planning.
+
+SASO Conf is an event that LATAM has traditionally done. When the yearly
+planning was done a tentative $1000 was going to be used for this event.
+This event isn't approved yet and hasn't got a LATAM sponsor. It exists
+in this entry as a planning reminder. If the LATAM ambassadors start to
+run out of money making decisions on these kinds of events can help make
+decision about what trade-offs to make or whether to ask for more money.
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.