Skip to content
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

Budget 2025 #1681

Open
derberg opened this issue Feb 6, 2025 · 3 comments
Open

Budget 2025 #1681

derberg opened this issue Feb 6, 2025 · 3 comments
Labels
enhancement New feature or request

Comments

@derberg
Copy link
Member

derberg commented Feb 6, 2025

2024 Recap

We did update on budget 2024 on October. So let's first see summary of budget, to get an idea how much left.

Numbers 💵

Some figures:

  • Budgeted expenses: ~$102,000
  • Expenses:
    • Actual expenses: ~$84,850
    • Expenses for 2025: $19,980 //some costs are reimbursed next year, like mentorship program for example
    • Total expenses: $104,830

$ 2 830 above budget because of underestimated very large costs of shipping swags from USA

We could cover all the costs because we had much more sponsors than expected:

  • Planned income $78,300.00
  • Actual net income $121,670.50

Left for 2025: $84,787.84

Full info on 2024 budget

Conference

Conference is always managed outside main budget as the sponsors there are separated to have clean books, and dedicated investment.

  • We had 2 sponsors ($5k each)
  • We spent $7198.11 - visa/travel/shippments

The remaining budget is transferred to AsyncAPI Conference 2025 budget: $1,851.18

2025

Since there are works toward introducing Governance Board to replace Executive Director. I decided:

  • I'm not gonna make any special improvements to how the budget is planned for 2025
  • I alone do not want to fight with thoughts if the fiscal year budget is better or the calendar year budget is better. I have an opinion but, still just an opinion.

We are not a company where budget is supercritical, we are more like an organizations/government. We need more or less what we are able to spend money on. If throughout a year some expected sponsors do not contribute, we simply adjust spending plans.

Budget technique proposal

My proposal for now is to basically:

  • Do budget as it is now, at the beginning of the year for 2025
  • Apply an approach called Carryover Budget which means, that if in 2026 we need to spend some money in Q1, and for some reason budget is not yet approved/prepared, we simply apply the 2025 budget and related approvals. This way we assure for example that topics like Bounty for example can continue without issues

carryover you can see in your local countries, where parties argue on budget and do not want to approve it for a long time. The country is not bankrupt, it simply follows the budget agreed upon for the previous year to make sure the country runs as expected

Plans

  • Budgeted expenses: $141,480.00
  • Left from 2024: $84,787.84
  • Planned net income $99,188.60

23% not planned, as a security pillow and budget security for 2026.

Plans overview

Feel free to have a deeper look and add a comment directly: Budget 2025

Image

Items walkthrough

  • Community Manager - community work done by @thulieblack
  • Community Marketing Specialist - marketing work done by @iambami
  • AsyncAPI Mentorship 2025 - continuation of our commitment to having own mentorship program to bring new talents to project
  • Mentorships coordination - new item. @AceTheCreator who was doing mentorship in the past as a Postman employee, wants to continue supporting the community. He commits to apply/organize few mentorships (like GSoC or AsyncAPI Mentorship). The estimated cost, including all the support hours for the mentors and mentees, is $2k per program. We secure a budget for 3 programs.
  • Bounty Program - continuation of the program, a bit more money as coordination work is now planned separately
  • Bounty Program Coordination - separated costs from program budget, for clarity
  • Swags - much smaller amount. The main focus is on stickers and cheat sheets production and distribution. I will distribute old swags to different events from my home for much cheaper.
  • 3rd Party Services - Zoom and Buffer licenses
  • AsyncAPI Grant - new item. In community goals for 2025. I bet that the first half of the year we will be working on the concept and figuring out how to spend first $15k
  • JSON Schema sponsorship - continuing supporting our friend project and main dependency

Sponsors plans

Large part of sponsors pay monthly and have not reported they will terminate their support at some point in time. The assumption in budget is that they will pay every month until the end of 2025.

Some sponsors made a one-time payment in 2024 and I'm sure they will renew - just do not know on what level. I also plan to reach out to each and introduce another sponsor level called Diamond.

Summary tl;dr

  • we are financially secure for 2025 🚀
  • as usual, the conference budget is managed separately with extra sponsorship
  • sponsorship renewal is in progress
  • you can notice new sponsors already: GitHub (one-time $600 donation), APIDeck moving to Bronze level, Mercedes-Benz joining with $300 monthly ❤
  • 2 new items in expenses: mentorship coordination work and AsyncAPI Grant
  • I propose that for next years, until new Govenance Board decides differently, follow the carryover budget to avoid situations when budget is not yet approved and we have to cover some pre-approved expenses
  • learning: the investment in swag store failed as too expensive. FedEx costs for shipping outside USA was extremely expensive and nobody was buying things ( I once tried, and for items worth $50, shipping was also $50). Shipping free swags to mentors/mentees or conferences reached ridiculous prices (sometimes on the tiny package to India was like $80) and closing the store and shipping a few boxes of swags to my place reached $6500 👀 . This year we focus on localized ordering and working on a list of network of merchants around the world for cost optimization.
@derberg derberg added the enhancement New feature or request label Feb 6, 2025
@derberg
Copy link
Member Author

derberg commented Feb 6, 2025

@asyncapi/tsc_members please have a look at this budget 2024 summary and 2025 budget plan

we are not voting yet - I first would like to have your eyes on it, ask questions, maybe suggest adjustments - and then next week we can vote.

I want to kick off voting next friday.

some items from budget were already consulted with: @iambami (swags), @thulieblack (grant), bounty (@aeworxet) and @AceTheCreator (mentorships)

@akshatnema
Copy link
Member

@derberg I've a couple of questions as:

Large part of sponsors pay monthly and now reported they will terminate their support at some point in time. Assumption in budget is that they will pay every month until the end of 2025.

Why will sponsors terminate their support?

Since there are #1634 to replace Executive Director.

Why are we replacing the Executive Director? 🤯 We have a very nice Executive Director right now 😊

If Executive Director won't be there, who will be the central person, handling all the accounts of AsyncAPI?

@derberg
Copy link
Member Author

derberg commented Feb 6, 2025

@akshatnema

Why will sponsors terminate their support?

sorry, spelling mistake, not now but have not.
assumption is that they will continue to pay

Why are we replacing the Executive Director? 🤯 We have a very nice Executive Director right now 😊 If Executive Director won't be there, who will be the central person, handling all the accounts of AsyncAPI?

well it is a good step as we do not remove the director, we replace the director, and replace the director with 3 people and goal is to have 5 people -> #1634. The plan is to not rely on one person, but split responsibility (one person can be responsible for account, one for sponsorship, etc). You know, we need to avoid the bus factor

I encourage you to join the discussion

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants