2016-01-02 3:17 GMT+01:00 Bryce Harrington <bryce@...2...>:
A majority vote of the current board members is required for approving this budget.
Proposal:
Adoption of the Rev1 budget in the attached spreadsheet for use as guidance in 2016 finances.
Align the 2016 budget to the Software Freedom Conservancy's fiscal year, which runs 3/1/2016 to 2/28/2017. We will stretch the 2015 budget to cover expenses through 2/29/2016.
Formalize the division of Inkscape's funds into distinct "pools", each carrying balances year to year, and registered in Paypal to allow donors to directly target the pool they wish to fund, as we did in 2015 for hackfest:2015 donations. We will still have a General Fund for general expenses and untargeted donations.
In general, having a little more structure in the budget is a good idea. However, I am not entirely sure about splitting the SVG WG budget into a separate item. It is really important that we keep participating in the WG, and that Tav can get the money to get to the WG meetings with a minimum amount of fuss, so I just want to make sure that we are not painting ourselves into a corner financially.
My proposal here is to allow funding SVG WG participation from the Hackfests pool, which can actually be called Developer Events or something like that. The end result of our participation in WG meetings is very similar to the hackfests (they lead to new features), so I think this is reasonable and most hackfest donors would approve of such use of their donations.
Generalize last year's Hackfest:2015 pool to cover future Hackfests. The money in this pool will be used exclusively for Hackfest sponsorship and related organizational costs. Assume an increase of 150% in the budgeted amounts over last year, to make provision for increased attendance. Since the hackfest-targeted fundraising has proven successful, no additional money is being allocated from the General Fund; we'll rely on the balance from last year and ongoing fundraising to cover these expenses.
Establish a new SVG Working Group funding pool. Seed this pool with $2250 from the General Fund, usable retroactively (i.e. the pool can be used to cover the Feb 3-6 meeting in Sydney, Australia.)
Allocate $250 each to the three existing funded project proposals, and to three new funded projects (to be determined in a subsequent board vote). Each funded project will have its own pool, in order to track per-project donations.
Sounds good. What happens with this money when someone comes in and just does stuff (Marc's case)? Do we vote as a board to reward them with the allocated money, or does it go into the general fund?
Other budgeted expenses follow the 2015 budget. An OSUOSL grant, Developer Education (details tbd), and sponsorship for LGM and SCALE are budgeted with the same amounts as 2015. The Contingency line item from 2015 is eliminated since we didn't have a use for it, and its $500 is lumped into Other Events.
Board chairman will document the budget on the Inkscape website, and follow up with subsequent votes on individual expenses as appropriate or as they come up.
[ ] a. Yes, adopt budget as described in "Rev #1" (below) [ ] b. Revise budget with the following changes recommended: _____________________________________________________ _____________________________________________________ [ ] c. Do not establish a budget for 2016
Vote: b. Revisions: merge SVG WG and Hackfest pools.
Best regards, Krzysztof