-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
2024 budget refresh and request for urgent pre-approval of some 2025 costs #1598
Comments
I would strongly suggest defining a set date on which AsyncAPI will have the TSC-approved budget to avoid urgent budget votings in the future. It may or may not correspond to the calendar year, but the idea I'm suggesting is to have the budget TSC-approved no less than 45 calendar days prior to the start of the budgetary period. Considering that AsyncAPI relies on donations from legal entities with fiscal years that do not necessarily end on December 31st, I would propose having the main budget correspond to the calendar year and be TSC-approved before November 15th, BUT to also have a mandatory six-month review period that will trigger each next TSC budget voting (primarily to reapprove the previously approved expenses, while also allowing for timely adjustments in case of newly discovered circumstances) before May 15th. Six-month budgetary TSC votings will give much greater flexibility to AsyncAPI in financial planning. |
@aeworxet definitely such urgent calls should be avoided in the future - 100% - I'll do my best to find the right schedule also to address the topic of salaries |
/vote |
Vote created@derberg has called for a vote on The members of the following teams have binding votes:
Non-binding votes are also appreciated as a sign of support! How to voteYou can cast your vote by reacting to
Please note that voting for multiple options is not allowed and those votes won't be counted. The vote will be open for |
@asyncapi/tsc_members kind reminder to take a vote: #1598 (comment) |
Sounds good! Always nice when you can afford to give raises to folks. 😺 |
The preliminary result of 18 out of 38 votes, with 18 'In favor' and zero 'Against,' indicates the possibility of starting preparations for the Bounty Program calendar quarter round |
Vote statusSo far Summary
Binding votes (20)
|
User | Vote | Timestamp |
---|---|---|
aeworxet | In favor | 2024-11-26 9:14:31.0 +00:00:00 |
Vote closedThe vote passed! 🎉
Summary
Binding votes (22)
|
User | Vote | Timestamp |
---|---|---|
@aeworxet | In favor | 2024-11-26 9:14:31.0 +00:00:00 |
Huge thanks to all folks that voted 🙏🏼 @thulieblack congrats!!! |
Budget situation
In January 2024, we planned to spend $102,088.27 while expecting an income of $78,300.00 (plus having $47,962.31 in the account from the previous year). We projected to leave $24,174.04 for 2025.
View of budget January 2024
As of November 2024, we already know that our 2024 expenses will be lower than estimated: $84,000 (potentially around $86,000 due to closing the swag store and some extra shipping costs). Income was $121,585.20—much higher than expected. This leaves us with approximately $86,000 for 2025, though the exact amount will be confirmed in January.
View of budget November 2024
The budget for 2025 is not yet finalized, as we need to wait until the end of the year to account for all expenses.
However, some expenses require immediate approval due to time constraints:
Thulie's Contract Renewal:
This must take place around February, and we must ensure we don't keep her waiting until the last minute.
Bounty Program for Q1 2025:
The program requires maintainers to submit proposed issues before the start of the "Bounty Quarter," meaning we need to initiate Q1 2025 planning in early December.
Proposal for Approval
Given the current budget situation, we can confidently afford the following costs for 2025:
AsyncAPI Bounty 2025 Q1
Allocate the budget of $5,000
Thulie's Contract Renewal
Renew Thulie's contract with a salary increase from $24,000 to $30,000, along with a role change to Senior Community Manager
Summary
Please vote to approve the following 2025 expenditures:
The text was updated successfully, but these errors were encountered: