-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Community Travel Fund in 2017 #151
Comments
Going to drop this in here for reference, the template for expense reimbursement https://drive.google.com/previewtemplate?id=0Ak7JTr_5ZgQBdHVEOG5rX0FYdTNzak5IQnh6cnp0dXc |
I have a few questions about this. I don't expect answers- I guess they really serve to provoke though. So here is my brain dump:
|
We felt pretty over-extended this year so the only we've committed to so far in next year is a single, large, Node.js Interactive in North America. Not sure which city yet but it will be a relatively low cost city for budgetary reasons. Keep in mind that the event budget includes money to bring in some selected speakers so it's not entirely on this budget to get people there if they are speaking. Also, if we want to bring in a bunch of people just for that event we could get the board to dedicate specific funds in addition to the regular Community Travel Fund.
No, we shouldn't. If we want to have one of these next year we'll just pass a new budget allocation for the whole event (including venue, food, travel, etc). |
@mikeal ... does this need to remain open? |
This does not need to remain open but you may want to request an allocation for additional funds since the TSC has already spent more than 50% of this year's allocation. |
@mikeal ... let's include a discussion of this during the private section of this week's TSC call. |
Heya,
It's nice to finally see that the community travel fund is being used.
I'd like to know how much money the TSC would like to see allocated into this fund in 2017 and if there are any scope or process changes to be considered. I'm working on the budget now, so feedback would be greatly appreciated.
The text was updated successfully, but these errors were encountered: