I’ve replied to some of your proposals, and for #4, as written, I will look into providing some more details. For the other proposals, at this time of the year and stage of the budget, it is tough to add something that neither has someone who drives it, nor a concrete budget sum. We urgently need to finalize the budget now.
Several months ago, I think @italovignoli reached out the various projects asking for budget proposals, it’s not that everything happened in just 6 days. That would be ambitious.
If there is a great, actionable idea that comes up after the budget is done, we can always look into it and make it happen, but I would not propose to further delay the budget, otherwise we’ll never finish it.
That depends on how the project is structured and how the candidates apply. Some tasks fit short-term, project-based roles, other fit long-term roles. The developer hiring is in discussion and not finalized, so can’t make a binding answer to that. However, I understand our goal is to retain competence in house, which advocates a bit against too short-term commitments.
See the PDF in this thread.
That’s the proposal for a tax office-compatible description if the item, yes.
That project has been ongoing work for a longer time, probably even predates your membership at TDF: Tender to implement the new TDF Membership Committee’s web-based tooling (#202105-01) - The Document Foundation Blog
The budget we spend, although the description is by now a bit outdated maybe.
Will you send a candidacy for coordinating this and let the members vote on it? Information on experience in German tax regulations as well as the insurance coverage sum would be helpful too.
We remove this item indeed.
- Carbon compensation is just that, we compensate for our travels and running infrastructure.
- Hardware for members is hardware members can use, e.g. for QA and development. In the past we bought e.g. HiDPI screens for people working on 4K elements.
- On LibreTranslate, @sophi can give some details.
- We run our hardware on Hetzner cloud, and as I understand, the plan was to connect our Jenkins instance to their cloud API to monitor, create and remove machines on the fly.
- The Japanese community sent budget requests, which we’ve merged into the community and marketing budgets.
- Five tenders were proposed (I think by @htietze or @x1sc0) and we considered those, but withdrew them, so did we withdrew the cost for external experts to independently assess these tenders.
- Two legal items are things that cannot be disclosed yet. One is about a domain name, another one about registering one trademark.
- Two HR items are items concerning freelancers or employees.
- For the LibreOffice roadshow, I think @elianedomingos can give some detials.
Well, it’s mid-June, the year is halfway over, we’ve seen not many proposals yet, so increasing it does not make much sense, because it’s unlikely we will actually spend the money in 2025.
Remotely is even more demanding due to the timezones, but even organizing a virtual meeting for like 20-30 people is nearly impossible at the moment.
We actually do have trademarks in the foundation assets, but over the course of time, new ideas and therefore ideas for registering trademarks come to mind.
Was intended for board, MC and team, and it’s removed from the budget, as indeed hard to conduct right now.
That’s why it is in the budget actually.
@italovignoli proposed this. I proposed to remove it for now, because I think it’s unlikely to happen in 2025.
We don’t have enough insight on it, so we might need an external consultancy on it if we are to implement it.
That’s why it has been removed from the budget.
These are conferences organized by our community, so they are less likely to happen if we don’t fund them. It’s not a third-party conference that happens anyways.
Neither does the board, this is why the budget item was removed.