-
Notifications
You must be signed in to change notification settings - Fork 11
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
Adopt and integrate Open Collective #24
Comments
Realizing this project is now being surfaced during team meetings (for example), I wanted to provide some additional context for those able to attend... ...basically to say that we can't actually move forward with next steps before leadership approves the proposal.
You'll see the first implementation step has been checked off as I shared this Canvas with @josephahaden + other leaders/decision-makers several months ago and have been periodically following up ever since. |
Noting for the record - rather than news - I'm sure this has been discussed but I wanted to log it here:
|
Noting for news: |
@meeware While the dissolution of Open Collective Foundation affected a few (I think just one WP focused collective), most projects and programs in Open Collective's open source ecosystem (https://discover.opencollective.com/?tag=open+source) have used/continue to use Open Source Collective (https://oscollective.org/) as their fiscal sponsor. This post from Lauren Gardner, Executive Director of Open Source Collective may help alleviate the confusion between the two entities https://opencollective.com/opensource/updates/regarding-the-announcement-to-dissolve-open-collective-foundation |
I should also point out we've been recommending Open Source Collective as the fiscal sponsor/host not only for the official WordPress project/community but programs like Five for the Future #39 for quite some time. This is because the platform benefits (outlined in the issue description) combined with the services OSC provides (https://docs.oscollective.org/what-we-offer) could alleviate issues with capacity, governance, and transparency while creating more financial and career opportunities for contributors. |
Open Collective provides a platform for financial transparency and collective funding, offering a structured way to support the WordPress project and its community. It allows individuals and organizations to contribute funds toward various aspects of the WordPress ecosystem, such as core development, community events, plugins, documentation, and more.
Benefits
Ways WordPress can adopt and integrate
Top-level WordPress collective
There are several WordPress collectives for a variety of projects and purposes, but nothing 'official' to sustain core and grow the community. While there's been discussion about adoption and integration (several mentions in Open Source and how we sustain ourselves - WordPress.org Project), there's no centralized way to fund community projects, teams, working groups, and contributors (and recognize those contributions).
One of the main reasons (for lack of widespread adoption/success) is murkiness around Open Collective as it's both an open source platform (https://github.com/opencollective) and fiscal sponsorship service (fiscal hosting in Open Collective speak).
We recommend using Open Collective's entity specifically set up to sustain open source projects to remove the burden/responsibility of WPF handling funds. OSC also provides a variety of services - including providing employment, payroll, and benefits to contributors.
Implementation steps
"Five for the Future" Fund
A Fund is a profile designed for one or a few large sponsor companies to move chunks of money and frictionlessly distribute it to as many collectives as they want.
Implementation steps include:
"WordPress" Project on the FundOSS Fund
Projects are a lightweight way for collectives to manage budgets for initiatives independent of their parent collectives. The FundOSS team (in collaboration with WordPress community admins) would create a project to
Implementation steps include:
Related Issues and Discussions
Reference/Resources
The text was updated successfully, but these errors were encountered: