Chad has been leading the Open Source Pledge, a simple framework to get companies to fund the projects they rely on. The idea is straightforward: for every developer your company employs, allocate $2,000 per year to open source. Distribute those funds however you want—GitHub Sponsors, Open Collective, Thanks.dev, direct payments, etc. The only other ask is to publish a blog post showing what you did. - Source: dev.to / 10 days ago

We see some projects that can financially survive (via sponsor or external infrastructure such as open collective or patreon), favoring the long-term sustainability. Thus, we keep our stand on promoting a transparent governance model to state where the investment will be managed and who can benefit from it, especially when knowing that non-technical users have an increasing key role in these communities. - Source: dev.to / 9 days ago

Leverage multiple platforms: Utilize GitHub Sponsors along with OpenCollective to broaden funding sources. - Source: dev.to / 10 days ago

Traditionally, open source projects were sustained by volunteer contributions and modest donations. However, as digital infrastructure came to rely on open source software, the need for reliable, scalable funding became evident. Enter corporate sponsorship—a model where companies invest in open source initiatives to secure their technology stacks, attract top talent, and foster innovation. This has spurred the... - Source: dev.to / 12 days ago

Abstract: This post explores various open source project funding strategies and examines their evolution, core concepts, applications, challenges, and future trends. We discuss methods such as sponsorship and donations, crowdfunding, dual licensing, paid services, foundations and grants, and the freemium model. Through real-world examples and a technical yet accessible approach, this guide offers insight into... - Source: dev.to / 12 days ago

There are plenty of tools that have started popping up to try and improve this situation since last year. CodeTogether, Duckly, Code With Me, and GitLive to name a few. Source: over 3 years ago

GitLive. Extend your IDE with the real-time features remote development teams need to work together effectively. See what your teammates are working on and get notified of merge conflicts before you commit. Make video calls and code together live, VS Code to JetBrains. [GITLIVE]. - Source: dev.to / almost 4 years ago

This is in no way an answer to your question but perhaps you would find git.live's merge conflict detection feature useful to potentially avoid the conflicts in the first place 😅. Source: about 4 years ago