# open source communities

Published articles for open source communities.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Community feedback: How can corporations improve support for open source maintainers?

DevFeed: [Community feedback: How can corporations improve support for open source maintainers?](<https://devfeed.tech/articles/community-feedback-how-can-corporations-improve-support-for-open-source-maintainers-34307.md>)

Original publisher: [Read original article](<http://opensource.googleblog.com/2026/06/community-feedback-how-can-corporations-improve-support-for-open-source-maintainers.html>)

Author: Google Open Source (noreply@blogger.com)

Published: 2026-06-30T18:30:00Z

Content type: opinion

Language: en

Sources: [Google Open Source Blog](<https://devfeed.tech/sources/google-open-source-blog.md>)

Topics: [Maintainers](<https://devfeed.tech/topics/maintainers.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Google](<https://devfeed.tech/topics/google.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [community](<https://devfeed.tech/tags/community.md>), [conference](<https://devfeed.tech/tags/conference.md>), [funding](<https://devfeed.tech/tags/funding.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [open-source-communities](<https://devfeed.tech/tags/open-source-communities.md>), [procurement](<https://devfeed.tech/tags/procurement.md>), [sponsorship](<https://devfeed.tech/tags/sponsorship.md>), [sustainability](<https://devfeed.tech/tags/sustainability.md>), [transparency](<https://devfeed.tech/tags/transparency.md>)

### AI overview

Google Open Source reports community feedback on how corporations can better support open source maintainers. Suggestions include predictable financial support, contribution-based payments, procurement and support services, conference travel sponsorships, respect for community norms, and consistency between documentation and practice.

### Source excerpt

by Sophia Vargas, Google Open Source We know that AI is actively transforming the sustainability and socio-technical dynamics of OSS communities. Google Open Source is committed to partnering with open source communities and ecosystems to learn together how we should update our own models for engagement and support. During an open meetup for GitHub Maintainer Month, I led a session to gather community feedback on how corporations can more effectively support open source maintainers. Paying maintainers takes creativity Many maintainers would appreciate consistent financial support. However, facilitating payments to individuals without established contractual relationships remains a complex challenge, particularly across diverse international jurisdictions. Fiscal hosts and programs such as Open Collective, GitHub Sponsors, and the LFX Mentorship Program can simplify components of this process, but they do not resolve the underlying issues of funding sustainability and predictability. While initiatives like the Open Source Endowment are working toward long-term funding sustainability, individual maintainers also had a few ideas: Pay per meaningful contribution vs gameable metrics: Avoid payment models based on easily manipulated units like pull request counts or review volume. A proposed alternative is 'pay per report,' encouraging maintainers to document their achievements and upcoming roadmaps. Commitment-based purchasing: Corporate policies might make procurement simpler (or more complex) than sponsorships, so maintainers could benefit from offering structured support services alongside traditional sponsorship opportunities. Fund conference attendance: In-person networking can be a boon for solo maintainers but it's often cost-prohibitive. For some corporations, travel sponsorship may be a simpler alternative to direct payments. Challenge for Corporations and Fiscal Hosts: How can we assist maintainers in understanding any and all prerequisites and documentation ne