Problem/Motivation
We need to find a simple, efficient solution to have joint finances without an official, incorporated new organisation, as NEDA is meant to be an informal network of local associations. We identify at least two recurrent needs: the funding of the LA_EU shared codebase development, and the funding the DrupalCon Europe booths. In the future there might be other uses for this shared money.
Proposed resolution
Many open source projects like the PHP Foundation use Open Collective, which offers transparency in the funding and spending of the money, reduces administrative overhead by offering a fiscal host in Europe, and allows easy fundraising from organisations and individuals.
Remaining tasks
Explore the terms of use and legal requirements to create an Open Collective to assess if this is the right tool for us.
Marine Gandy (mupsi) and Nicolas Loye (nicoloye) have volunteered for this task.
Comments
Comment #2
mupsiOptions
There are two main ways to use Open Collective:
Cost
In our case, the best fiscal host option is Open Collective Europe, incorporated in Belgium. There are fees when we received money through them:
If we round it up to say 10%, it might seem like a lot but when you think about how much time and money it would cost us to incorporate NEDA and handle our own bank account, it feels like a reasonable expense.
Especially as organisers, it would make our lives so much easier. Instead of chasing after each association each year for the booth, we could have a simple process, for example: each board decides the amount they want to contribue for NEDA for the year and makes 1 single payment. Then we can decide based on the funds available how many hours we want to spend with Lemberg on maintenance or new feature development, or what the budget for the booth is. We could also then set goals and have fundraising campaigns for specific features.
Another good feature is that we can name several administrators who have the power to handle invoices and spend the money for the collective. That is great to allow for shared workload instead of overworking one single treasurer from one association. It also means more control over that money so that if an association pulls out, we still have enough people to move on.
Application
It takes about seven business days to get an answer once we have submitted an application.
https://docs.opencollective.com/oceurope/getting-started/how-to-apply
Next steps
Comment #3
mupsiComment #4
borisson_This looks good, I read this page, as well as most of the page from the fiscal host. I think we can go ahead with this. I will discuss with Sven if we can be one of the admins.
Comment #5
svendecabooterIf there are no objections, you can add me as an administrator for Drupal BE:
name: Sven Decabooter
email: info@drupal.be
Comment #6
nicoloye commentedIf that's alright, I'd like to be admin to help on this topic too. Thanks:!
Comment #7
esmoves commentedDutch Association agrees
Comment #8
mupsiI will start the application process on Monday with Sven and Nicolas as admins, if someone else wants to join let me know. We can always add more admins later anyway so it's not a blocker at the moment.
Comment #9
grienauerWe had multiple meetings and calls and finally we managed it.
https://opencollective.com/drupal-europe
Kraut and me also had a meeting in Brussels and then with Open Source Europe again online. We managed to get a discount of the fees. "Carrier Fees" are normally 8% our Collection is down to 5%. Just a small win, but at least something :)
Please see also https://drupal.slack.com/archives/C09DHEET61W/p1778073037508419 to get involved.
This should be our LA_EU project, where money should go in for development/support for the platform and also payouts should be done there.
Comment #10
grienauerComment #11
svendecabooterComment #12
borisson_Is there a reason why this issue is still open? Is there anything we can do about this still?
If not, I'd like to open a new issues specifically for a few followup items:
1. We should create a page on drupal.eu to describe what is going to be paid with the open collective.
2. Create a page on drupal.eu with a process on how to add/remove people from the open collective.
3. Create an issue in this issue queue that people can use to have their own associations added to the open collective.