@hestenet Thanks again for the update and for our continued Slack discussions. I wanted to share a couple more thoughts and ideas after considering all the feedback:
First, I want to clarify (again) that we’re not proposing the DA:
- replace its current tools and processes with Open Collective
- use https://opencollective.com/drupalassoc as the fiscal sponsor
- administer the (Open Collective) fund
If the DA is currently managing an Innovation Fund through its own tools and processes, we could avoid potential confusion by not creating a fund with the same name. Instead, we could enable the community to manage the following:
- Drupal project on FundOSS (see #3412386-23: Leverage Drupal Innovation Fund on Open Collective → )
- Top level Drupal collective (see #3377002: Leverage top-level Drupal collective (Open Collective) → )
In summary, these recommendations present a complementary, community-driven approach that aligns with DA’s mission without conflicting with its core processes. Empowering the community to manage these initiatives through FundOSS or the Drupal collective on Open Collective would broaden Drupal’s funding options, opening new engagement opportunities within Open Collective's extensive open source ecosystem and reinforcing the DA’s long-term strategic goals.
@hestenet Thanks for the update! Can you remind us if this deck was previously shared with IWG earlier this year (see #3452747-10: Innovation Hub on drupal.org → )?
Also just to be clear -
This has been raised to the provisional new DA Innovation Working Group lead for input and consideration for the DA's engineering roadmap.
Assuming that means potential engineering resources but not necessarily funding?
If the Drupal Association (DA) isn’t interested in creating the Innovation Fund directly, we could set it up as a “Drupal Innovation” or “Drupal Innovation Fund” project within FundOSS on Open Collective, which is itself a Fund with Open Source Collective (OSC) as the fiscal host.
This approach would provide the same operational benefits as a DA-created fund, with OSC handling all fiscal responsibilities and administration. FundOSS would serve as the primary project hub, requiring only approval from the DA and other FundOSS admins to proceed. By partnering with FundOSS and OSC, the Innovation Fund could support Drupal projects with minimal additional demands on the DA.
Following up to address recent concerns regarding the use of an Open Collective Fund for the Drupal Association’s Innovation Fund. The Open Collective Fund model is an efficient and transparent way for the DA to manage and distribute funds without administrative burden, complementing the DA’s current fundraising and crediting systems.
Key benefits include:
- Simplified Contributions: Corporate supporters make a single, large contribution to the Innovation Fund, which Open Source Collective (OSC) then distributes across projects. This reduces procurement complexities and repetitive invoicing.
- Efficient Disbursement: With OSC as the fiscal host, funds can be transferred directly to specific projects like Starshot, Automatic Updates, or Project Browser. This setup enables efficient resource allocation without requiring DA staff to manage each disbursement.
- Flexibility and Transparency: The Innovation Fund supports both on- and off-platform projects, providing flexibility to fund a diverse range of initiatives. Open Collective’s transparency ensures contributors can see fund use, while privacy options protect sensitive information where needed.
Moreover, by inviting knowledgeable community members to help administer the Innovation Fund, we create a collaborative, shared responsibility model that aligns with the DA’s goals and resource needs. This approach allows the DA to support open-source initiatives sustainably, with OSC handling fiscal and logistical details.
During an Innovation Initiative Meeting on June 25th, 2024, we discussed steps for moving forward with the Innovation Hub proposal for Drupal.org. Participants included Gus Austin (gusaus), Tim Lehnen (hestenet), and Ricardo Marcelino (rfmarcelino). Key points discussed:
Project Dependencies and Timing:
- Tim noted that progress on the Innovation Hub may be delayed until the initial stages of the Drupal 10 (D10) upgrade on Drupal.org are complete, as that upgrade currently has top priority. However, he suggested that developing the Innovation Hub as a set of custom modules on a generic D10 site could allow for a “jump start” and potential evaluation for later integration into Drupal.org.
- Gus acknowledged the delay but suggested that the team could advance the project independently of the Drupal Association’s involvement, particularly if there’s an approved plan and funding.
Funding Mechanism:
Open Collective integration is already a dependency of the Innovation Hub. Tim mentioned that CFO approval would be required to use Open Collective (OC) as the mechanism for the funding portion of the hub. Gus requested clarification on this point, as it wasn’t immediately clear why CFO approval would be necessary for using OC via the Open Collective module.
Next Steps:
- Gus proposed that the team seek Innovation Working Group (IWG) approval on the hub concept as a next step.
- Tim agreed, noting that once IWG and CFO approvals are in place, the team could move forward on the specific goals and funding pathways.
- Ricardo suggested focusing first on validating the initial work completed, as iterations on code are time-intensive.
As mentioned in #3412386-21: Leverage Drupal Innovation Fund on Open Collective → we've been discussing how companies in the Drupal ecosystem might benefit from participating in the Open Source Pledge (osspledge.com), an initiative encourages companies to contribute a minimum of $2,000 per full-time developer per year to open-source projects.
While direct donations to foundations like the Drupal Association could be one entry point for participants, Open Source Pledge will most likely leverage/integrate Open Collective to discover and fund projects/ecosystems like Drupal.
That said, we have yet another reason to figure out how we can make better use of the Drupal collective (see #3377002-28: Leverage top-level Drupal collective (Open Collective) → and previous comments) before the inaugural promotional campaign for Open Source Pledge kicks off in a few weeks.
Circling back as we've been discussing how companies in the Drupal ecosystem might benefit from participating in the Open Source Pledge (osspledge.com), an initiative encourages companies to contribute a minimum of $2,000 per full-time developer per year to open-source projects. These contributions could take the form of new or existing donations to the Drupal Association .
With a major promotional campaign in the works (https://github.com/opensourcepledge/osspledge.com/issues/11) this could provide great exposure for Drupal and its supporting companies in the broader open-source ecosystem.
Referencing here as leadership from Open Collective and Open Source Collective (the fiscal sponsor for the Drupal collective) are discussing how they can leverage Funds as a way to aggregate pledges interested in supporting ecosystems (like Drupal).
Considering there's interest from Open Collective and OSS Pledge in including and promoting Drupal (and Drupal companies) in the inaugural campaign, I think a Drupal Innovation Fund on OC could be an entry point for participation.
Wonder if we could experiment with some of Open Collective's new crowdfunding functionality on https://opencollective.com/drupal. Posting in this channel as the Drupal Association is still trying to figure out how to make better use of that collective (in a way that compliments/extends their current strategy).
I'm currently evaluating on another collective. Looks like you can enable on a per/project basis - which would basically be our use case https://opencollective.com/drupal/projects
Considering another entity (Open Source Collective) is the fiscal sponsor/host, it seems like one easy way to compliment DA fundraising would be to only have tiers for individual contributions. That way sponsoring orgs/partners could continue to use the existing system (funds could still be transferred into the collective on the back end) but individuals (open source/Drupal supporters) outside of the community/ecosystem might support (especially if the collective was promoted a bit more).
Actually these profiles will make it even easier to participate in FundOSS (and/or Drupal specific rounds). Considering the size of Open Collective's open source ecosystem (https://discover.opencollective.com/?tag=open+source) having the official 'Drupal' collective participate (individual projects could still choose whether or not to opt-in) would be pretty buzzworthy (and generate new funds and contributors).
Moving back to Sustainability - keeping closed for the time being.
Moving 'back' to the Sustainability project as there's new interest in getting the Sustainability team up and running. Helping manage the Drupal collective (including helping fundraise) is a responsibility.
Closing for reasons discussed in the comments and this meeting thread. Will most likely move (this and it's children #3328127: Determine standard process for onboarding projects (working groups, etc) → . #3332738: Create goals and tiers on the Drupal collective → , & #3280977: Outline projects, groups, and initiatives that can be supported on the Drupal collective → ) to a different project after we determine which team/working group will be helping the current admins/core contributors of https://opencollective.com/drupal (currently Tim, Dries, and myself) manage.
The following are excerpts from our meeting earlier today (@hestenet in blockquotes) as it should validate that the Drupal Association is in fact using https://opencollective.com/drupal as a compliment to their existing fundraising and crediting structures...
I will say that I have had an initial conversation with our new CFO about this - and have started having some other conversations about it with the Starshot leadership group as well.
Based on our discussion (so far) in :three: :one: it doesn't seem like whether or not to use https://opencollective.com/drupal is the question; it's more about how can it 'compliment' the existing mechanisms DA already has, yes?
Yes, very much - it's not about replacing existing structures we have that are working well - but about demosntrating how it can open a new avenue for expanding our funding reach.
...as members of the Innovation team have been working with the DA to support (see the issue description and subsequent comments for context), it's important we move this (and related closed issues) to the project we've agreed will be used to coordinate activities around organizing and sustaining the Innovation initiative ( https://www.drupal.org/project/innovation → )
The Drupal Association partner program webinar (for their partners) earlier this week ran through the new options to (a) fund people at the partners and/or (b) through the DA's innovation fund and/or (c) through DA employing people to work on Starshot. The last two depending on the amount of money the partner can contribute. The last two depending on the amount of money the partner can contribute. I think Dries will cover those tomorrow and the DA may publish more details of that later too.
@gábor-hojtsy provided some additional context (around funding Starshot) a couple weeks ago in Slack but I'm not sure what's been discussed or decided since.
Considering there's a component set up for Funding, it seems like https://www.drupal.org/project/issues/starshot → would be a good place to centralize (plans and processes to funding Starshot).
As noted in #3412386: Leverage Drupal Innovation Fund on Open Collective → , I think Starshot creates the need/opportunity to make better use of Open Collective (and Open Source Collective as a fiscal sponsor/partner) for the reasons outlined (I'll quote and provide additional context).
Drupal Association could continue to leverage their current fundraising and crediting system as funds could be allocated (to the Fund on Open Collective) via bank transfer or some other way. By using Open Source Collective as fiscal host/sponsor, the DA would 'not' be solely responsible for allocating funds to related projects and initiatives (and their contributors). For example, if we set up 'projects' for Starshot, Automatic Updates, Project Browser, Recipes, etc on https://opencollective.com/drupal funds could be allocated from the Drupal Innovation Fund to Starshot and/or any of the related projects via collective to collective transfer.
Per the previous comments we've been working with the Drupal Association (specifically @hestenet) on executing this already approved plan. This includes the first few implementation steps from creating https://opencollective.com/drupal and setting up an initial set of projects https://opencollective.com/drupal/projects (see #3280977: Outline projects, groups, and initiatives that can be supported on the Drupal collective → ). We've also been exploring how to/who should manage in #3328127: Determine standard process for onboarding projects (working groups, etc) → .
By leveraging, Open Source Collective as the fiscal sponsor for both the Fund and Drupal collective (OSC is currently the fiscal sponsor for https://opencollective.com/drupal), we could augment the DA's current system/capacity by providing a wide range of additional services and benefits for contributors (including potential full-time employment).
While my recommendation in #3377002-11: Leverage top-level Drupal collective (Open Collective) → to continue to use Open Source Collective as the fiscal sponsor was to alleviate potential capacity issues, by pooling/centralizing funds in https://opencollective.com/drupal, OSC could augment DA capacity by paying and potentially employing contributors.
Another benefit of pooling/centralizing funds would be increased visibility for Drupal in the largest open source ecosystem on the planet https://discover.opencollective.com/?tag=open+source
I think Starshot is a type of project which requires a lot of time and dedication from a lot of people, more than any theoretical fund could fund, and community is already mobilized for this effort.
A Drupal Innovation Fund isn't theoretical. It's something Dries mentioned multiple times during this Starshot session Participation, Funding, and Governance.
Neither is an Open Collective Fund (https://docs.opencollective.com/help/financial-contributors/organization...). It's a mechanism that Open Collective has provided for several years and something the Drupal Association (specifically @hestenet) has been exploring over the past year.
This task was created before the Innovation Fund was announced as a way to fund contributions to Starshot → (including the session Dries led on Participation, Funding, and Governance). While we have been talking about creating/leveraging an Open Collective Fund for other use cases, Starshot creates the need and opportunity to do the following:
- Create a Drupal Innovation Fund on Open Collective (see https://blog.opencollective.com/funds-for-open-source/)
- Create a Starshot project on https://opencollective.com/drupal (see
#3377002: Leverage top-level Drupal collective (Open Collective) →
)
By doing the following the Drupal Association could continue to leverage their current fundraising and crediting system as funds could be allocated (to the Fund on Open Collective) via bank transfer or some other way. By using Open Source Collective as fiscal host/sponsor, the DA would 'not' be solely responsible for allocating funds to related projects and initiatives (and their contributors). For example, if we set up 'projects' for Starshot, Automatic Updates, Project Browser, Recipes, etc on https://opencollective.com/drupal funds could be allocated from the Drupal Innovation Fund to Starshot and/or any of the related projects via collective to collective transfer.
If we created projects on the Fund for each use case (Starshot, Innovation Funding rounds (see #3376257: Innovation Funding Rounds: Leveraging Democratic Funding → ), the DA would have even more control and flexibility in terms of allocating funds.
By leveraging, Open Source Collective as the fiscal sponsor for both the Fund and Drupal collective (OSC is currently the fiscal sponsor for https://opencollective.com/drupal), we could augment the DA's current system/capacity by providing a wide range of additional services and benefits for contributors (including potential full-time employment).
We need to move into https://www.drupal.org/project/innovation → for reasons discussed in this issue and Slack thread.
Or to summarize again - https://opencollective.com/drupal exists and the DA CTO + Drupal project founder are admins (I'm also a team member)
It's way beyond an idea or proposal. We've been working together to execute this plan for quite some time.
Marking RTBC because the proposal has already been shared with key members of the Drupal Association/board and we've been on/off working together over the past year to execute the plan (skim the Google doc comments and this Slack canvas for more context).
Assigning to @hestenet as he's been interfacing with members of the DA/board and members and partners of FundOSS (the program we'd be leveraging).
tekNorah → credited gusaus → .
tekNorah → credited gusaus → .
Minor title change to reflect the fact that https://opencollective.com/drupal exists and is active
This was a child task for an outdated initiative https://www.drupal.org/project/innovation_ideas/issues/3325045 →
Updating title to reflect primary goal/task of creating a fund on Open Collective
Not sure if the admins (of https://opencollective.com/drupal) were able to discuss at DrupalCon, but setting up projects for Starshot → and other related initiatives (like what Dries referenced in this summary post) would eventually surface Drupal in Open Collective's open source ecosystem provide additional visibility, increase funding, and grow/diversify the contributor base for the initiatives and Drupal.
From an implementation standpoint, it will primarily rely on the Project Browser → and Recipes → initiatives, while also incorporating the Experience Builder initiative.
Closing this out as most (all?) of the components are part of related projects/initiatives like the following:
- https://www.drupal.org/innovation/ →
- https://www.drupal.org/community-initiatives/documentation-and-help-init... →
- https://www.drupal.org/project/innovation_hub →
- https://www.drupal.org/project/funding →
- https://www.drupal.org/project/opencollective →
or children of other projects/tasks in this repo
Will revisit if we determine there's still a need for this type of initiative.
Updated to align with the goal of creating a dedicated innovation fund.
updated the title to better reflect the ongoing nature of these funding rounds (and what they would fuel).
seantwalsh → credited gusaus → .
hestenet → credited gusaus → .
Moving as this is a subtask of #3325045: Community Enabler Initiative → . As the latter overlaps with other active projects and initiatives, we may end up consolidating and closing out this initiative (and this task!).
Transferring all related issues to Innovation as Open Collective (and https://opencollective.com/drupal) are key components in Innovation Initiative goals and strategy
Moving this (again) as the goals/outcomes align with https://www.drupal.org/innovation/ → and other projects/initiatives in this issue queue (specifically #3421224: Unify and solidify Innovation Hub plan → and the Documentation and Help Initiative → ).
Moving this to the Innovation project (or the closest thing we have) as the issue for the top-level Drupal collective is here...which should be key for Drupal growth and innovation.
This has been on the back burner (once again) but we're in the process of evaluating if/how the platform (and it's dependancies) could be a proof of concept and prototype for the Innovation Hub on drupal.org (see #3421224: Unify and solidify Innovation Hub plan → ).
We'll update this issue as we go through the process.
Moving to the Innovation project as the Drupal collective should be a key component for meeting/exceeding DA innovation (and related strategic goals).
Narrowing down the scope to focus on enabling the program to coincide with with Drupalcon Portland.
@mindaugasd Thanks for the additional input (and creating the related issue). Considering Vitalik Buterin is a key innovator for the model we're leveraging, I'm sure there are components of Gitcoin's evolving platform and solutions that will address challenges and concerns.
With regards to how it relates to what we're proposing here, Drupal (via the Innovation Working Group?) would be participating (not owning) in a program organized and sustained by FundOSS (in partnership with organizations like Open Source Collective and Gitcoin).
The same model that has raised over $56 million towards public goods in a short period of time https://impact.gitcoin.co/
The following are the key goals referenced in https://www.drupal.org/drupalorg/blog/drupal-means-innovation-introducin... →
🔍 Exploring Innovation: Delve into the latest projects, initiatives, and breakthroughs shaping the future of Drupal. From experimental features to groundbreaking modules, discover how Drupal continues to innovate and evolve.
💡 Inspiration and Ideas: Get inspired by the creative endeavors of our community members. Explore case studies, success stories, and thought-provoking articles that showcase the innovative spirit of Drupal enthusiasts worldwide.
🤝 Contributing to Progress: Be part of the movement driving Drupal forward. Discover opportunities to contribute your skills, expertise, and ideas to the Drupal project and help shape its trajectory in the years to come.
We invite you to join us in sharing, participating, and collaborating in the Drupal innovation journey. Together, let's shape the future of digital experiences and contribute to the vibrant ecosystem of Drupal.
Should we incorporate into the plan here?
What about the projects/priorities/programs referenced in https://www.drupal.org/innovation → , https://www.drupal.org/innovation/blog → , and https://www.drupal.org/project/issues/innovation_ideas?categories=All → ?
Assuming these are part of the same Innovation initiative (working group?) should we have a corresponding d.o. project? If yes, possibly we could rename this one and change the slug to https://www.drupal.org/project/innovation → ?
With the Innovation Hub announcement → linking to https://www.drupal.org/innovation → how/where do these mockups fit in?
Assuming the Innovation Hub → @alexmoreno just announced → (on behalf of the Drupal Association) is the same one we all were discussing on a recent call (see the https://docs.google.com/document/d/1Rp-uGFPq2Zmz1g4JApcJFNvi19dDWkHsC5_R...), we should make sure all goals/priorities/needs are consolidated in this plan (and referenced in this project).
Including the DA strategic goals referenced in the announcement and https://www.drupal.org/innovation/ →
Does that make sense to everybody that attended the recent calls?
Copying over the description from #3099877: SustainDrupal program → as most/all of the suggestions (an attempt to update/rebrand Snowball charter) seem to be relevant here. Instead of rebranding as SustainDrupal initiative we could roll the overlapping Snowball goals/user stories into this plan.
Integrating these funding tools will be great, but I think there's still going to be a need for a working group or initiative with a focus on sharing tools, talent, and resources to sustain.
Instead of reinventing the wheel, possibly we could create a SustainDrupal initiative by doing the following:
1) Change the name of this Drupal group to SustainDrupal
This group looks to consolidate some of these ideas and discussions in one place, providing a venue for people to discuss creative funding solutions or business models that can add sustainability and a source of income for individuals contributing back to Drupal, whether that's through work on Core, contributing modules or themes, or building new frameworks for other developers to use in their own development.
2) Review, update and incorporate elements of this Snowball charter into SustainDrupal.
Problems this initiative intended to solve include:
- People who would like to support an idea but cannot do it all themselves do not have a way to move forward.
- Potential collaborators do not have clarity on what proposals exist, who has committed to working on them, and the specification of what is proposed to be done. This lack of clarity can lead to duplication of effort, and consequent underresourcing of efforts.
- Potential supporters do not have a good way of understanding the level of technical vetting a proposal has.
- Potential supporters do not always have a transparent view of the risks to a proposal's success.
- Many good developers are using Free Software, not contributing to Free Software, even though they would prefer to work directly on projects benefiting the community.
3) Create #sustaindrupal channel in Drupal Slack
4) Identify roles and find some folks interested in contributing to this type of initiative
5) Create an Open Collective as a tool to sustain the SustainDrupal initiative
Does anyone else have some thoughts on this approach?
As mentioned in several Slack discussions, I believe the following aspects of #3325045: Community Enabler Initiative → and/or the Contribution Credit system → overlap with goals/dependencies of Innovation Hub:
- Enable organizations and individuals to pledge resources (sponsored contributors and funds)
- Ability to search and discover projects, and groups in need of resources (funds and contributors)
- Ability to fund specific teams/contribution areas or the entire project and community
- Enable organizations and individuals to receive credit
- Logo displayed on sponsored projects, teams, initiatives, and other groups (see 🌱 Roadmap to Stable Release 1.0.x Active )
- Number of contributors and time on their organization page
- Credit for financial contributions (via the crediting system)
- See #3094555-8: Roadmap to Stable Release 1.0.x → for more examples
Do you think we should roll some/all into the plan?
Closing this out as we should merge relevant goals and ideas into the larger Innovation Hub project (and plan once we create an issue).
Considering https://www.drupal.org/innovation/pitchburgh-2023 → at the last US DrupalCon was the catalyst for this plan and project, wouldn't it be fitting if we could do something similar for https://events.drupal.org/portland2024 but leveraging the funding tools we're in the process of building?!?
I think providing a way for the community to vote by actually funding projects during a Driesnote would be really powerful (and buzzworthy).
As noted it the last comment, it seems like we'd need buy-in from the DA to make it happen. Maybe we already have that considering we're in the process of unifying overlapping projects/programs in #3325045: Community Enabler Initiative → and have a team which now includes both DA CTO and Innovation coordinator?
We're starting off 2024 by consolidating this and #3099877: SustainDrupal program → as they overlap with goals and ideas described in https://www.drupal.org/project/innovation_ideas →
We've also been discussing having active contributors join forces as maintainers... which would make sense considering there would be multiple team members (@hestenet and @alexmoreno) representing what 'seems' like it would need buy-in and involvement from the Drupal Association to move forward.
Specifically we need to determine the following:
1) Can the Drupal Association include in their offerings to supporters (using their existing tools and resources)?
if yes
2) What can we do (Innovation ideas maintainers and members of the Sustainability Team) to help make it happen?
@hestenet was able to set up https://opencollective.com/drupal a few months ago but there has since been a long delay in actually doing anything with it due to confusion around who could/should manage. So it's been lingering with a balance of less that $50 - which is a terrible look for Drupal when it comes up in Open Collective search.
From my understanding it's the Drupal Association still trying to figure out if they can connect their https://opencollective.com/drupalassoc fiscal host so they can centralize fundraising and integrate/extend their strategy.
Main issue is whether or not they'll have capacity to take on the responsibilities outlined in Open Collective's docs.
With no decision on the horizon, I'd like to suggest we keep using our current fiscal host Open Source Collective, but utilize in a way that would compliment/not compete with DA's fundraising and crediting system.
To do this we can create a Fund (see the documentation and blog post) that the Drupal Association could contribute to via bank transfer. While the Drupal Association might have a role in determining how the fund is used, it would be the open collective fiscal host (either Open Source Collective or Open Collective Foundation) that would handle the rest.
Similarly we can create a 'Drupal' project on the FundOSS Fund for the FundDrupal matching pool (see #3376257: FundDrupal: Leveraging Democratic Funding to build on the success of the Pitch-burgh innovation contest → ).
Both can then be used to sustain and grow the Drupal project and community (via the Drupal collective) based on policies the admins of each Fund create.
Again - Drupal Association may help admin and create policies but they would 'not' assume any of the fiscal host/sponsor responsibilities.
I narrowed down the project scope to reflect the realistic commitment Drupal Association would have to make in order to enable quarterly Quadratic/Democratic funding rounds. Reason for the limited investment (time and funds) is we'll be able to leverage the FundOSS platform and resources when the program comes back online in early 2024.
The only investment DA would need to make is incorporating the match fund (and potentially a stand-alone Fund (https://docs.opencollective.com/help/financial-contributors/organization...) into their existing fundraising strategy.
Transferring this to Sustainability (who will be helping DA manage https://opencollective.com/drupal) but putting on hold until there's clarity on #3280977: Outline projects, groups, and initiatives that can be supported on the Drupal collective →
Is there a different way to present it?
YES! If the Drupal Association supports the effort, we'll customize the program so it's clear to Drupal stakeholders. The Gitcoin program and platform is not the best example (mainly because it's currently centered on web3/crypto), but FundOSS (which was a partnership between Open Source Collective and Github) is better since it focused on sustaining open source projects without the crypto dependency. As a pilot participant (with a WordPress project), I can say it was similar to other crowdfunding programs/platforms. The funding model made it unique actually has a pretty good explainer on this site https://www.wtfisqf.com/
We're addressing and answering similar questions to yours in the google doc and Slack conversations with the Drupal Association. We all agree it needs to be clear for DA and the community to adopt. That's exactly what we're in the process of doing.
> I think quadratic funding is great idea if clients and site builders vote too (in addition to agencies/developers).
I understand why this idea is confusing to the Drupal community (because no Drupal projects/programs/orgs have participated), but the program and potentially the platform we'd be leveraging and extending have existed for several years.
There's already a process and policies we can incorporate into our own (our specific goals and needs will be different). Even a new training cohort that can we repurpose or participate in (depending on how we pool resources with our parters).
Everything is dependent on if/how the Drupal Association becomes involved. After a brief pause (largely because our platform/program lead changed jobs), we're restarted discussions (in the #drupal-association Slack channel) and will continue those (in-person and virtually) during DrupalCon.
seantwalsh → credited gusaus → .
With the Drupal collective coming online, this issue (at least in it's current state) is outdated.
@mindaugasd You raise valid points in your other comments. As a participant in the FundOSS pilot (the brought the Quadratic Funding model to open source projects on Open Collective), our (WordPress) project raised more funds in two weeks than we ever had before (or since). Considering the original program has been so impactful, a renewed platform and marketing partnership should bode well for a Drupal program and/or Drupal participants in FundOSS (which we're also planning to revive).
Still may not be a good fit for every project or maintainer. So we'll keep evaluating and experimenting with other models and partners.
Solidify partnerships with groups, organizations, and individuals with expertise and capacity to support and grow Drupal by enabling ongoing Quadratic Funding rounds.
There reason I haven't provided an update is we're still stuck on this task because our platform and marketing partners became unavailable soon after we shared our proposal with the Drupal Association.
Just over the last week or so I've reconnected with the same people we were forming a partnership with...and long story short...it looks like there's not only interest but access to additional platform and marketing resources provided by the company that created the Quadratic Model and platform in the first place.
In addition to using a third party platform, it looks we'll be able to integrate the Quadratic Funding component into Drupal. Doubtful that we'll be able to find skilled/available contributors without funds.
seantwalsh → credited gusaus → .