# sponsorship Published articles for sponsorship. 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?]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-06-30T18:30:00Z Content type: opinion Language: en Sources: [Google Open Source Blog]() Topics: [Maintainers](), [Open Source](), [Google](), [Pull Request]() Tags: [community](), [conference](), [funding](), [maintainers](), [open-source](), [open-source-communities](), [procurement](), [sponsorship](), [sustainability](), [transparency]() ### 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 ## Documenting the manual: how curiosity and robotic arms led to a career in open source DevFeed: [Documenting the manual: how curiosity and robotic arms led to a career in open source]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-06-22T18:30:00Z Content type: article Language: en Sources: [Google Open Source Blog]() Topics: [Documentation](), [Open Source](), [Linux Kernel](), [Linux](), [C](), [Undocumented feature](), [Network](), [Scripting]() Tags: [c](), [communities](), [documentation](), [linux](), [linux-kernel](), [linux-man-pages](), [network](), [open-source](), [scripting](), [sponsorship](), [undocumented-feature](), [work]() ### AI overview This article profiles Alejandro "Alex" Colomar's path from working with robotic arms to maintaining Linux Kernel documentation. It explains how documenting the previously undocumented SO_TIMESTAMPNS feature led to his first man-pages patch and eventually to a career focused on clarity in open source communities. Google sponsors his work on the Linux Kernel man-pages project. ### Source excerpt by Daryl Ducharme, Google Open Source When you think of "innovation" in open source, your mind probably jumps to the latest AI model or a revolutionary new framework. You might not immediately think of manual pages. Even Alejandro "Alex" Colomar, who spends his days maintaining Linux Kernel documentation, jokingly admits that some might find the work "boring" because it focuses on fixing existing issues and documenting new features rather than flashy inventions. But as any developer knows, the most powerful code is only as good as the documentation behind it. At Google, we believe that investing in the success of projects we don't own is a core part of being a good open source citizen. That is why we are proud to sponsor Alejandro's work on the Linux Kernel man-pages project--supporting the critical infrastructure that many of our own systems rely on every day. Documentation is the gift you give to your future self and your whole community. The precision of a robot Alejandro's journey into the world of essential documentation started at university. He was working with robotic arms that used a proprietary scripting language. Wanting more control, he decided to write a C library to communicate with the robots over the network by sniffing packets with Wireshark. It worked, but it was slow--he had to wait seconds between commands to ensure the robot had finished moving. To make the movements smooth, he needed to understand the messages the robot was sending back in real-time. This required high-precision timing. He found SO_TIMESTAMP, which provided microsecond precision, but he noticed a macro called SO_TIMESTAMPNS in the header files that promised nanosecond resolution. The problem? It wasn't documented in the manual page. The first patch After figuring out how to use the undocumented feature by looking at the kernel source code, Alejandro decided to ensure the next person wouldn't have to struggle. He cloned the man-pages repository, wrote a new paragraph based on exis ## 2014 New York Android Meetups Featuring Mark Murphy and Ray Ryan DevFeed: [2014 New York Android Meetups Featuring Mark Murphy and Ray Ryan]() Original publisher: [Read original article]() Published: 2014-07-08T18:17:59Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Android](), [Mobile](), [Development](), [Dagger](), [Open Source]() Tags: [android](), [android-development](), [community](), [conferences](), [dagger](), [development](), [meetup](), [open-source](), [q-a](), [speakers](), [sponsorship](), [talks]() ### AI overview Touchlab recaps its March and May 2014 New York Android meetups, featuring presentations by Mark Murphy and Ray Ryan. Topics included the future of the Android ecosystem, Dagger, Flow, and Mortar, with sponsorship and venue support from several companies. ### Source excerpt Mark Murphy, the founder of CommonsWare and author of The Busy Coder's Guide to Android Development, joined us at StackExchange's new office. ## ING-DiBa Foundation Sponsorship DevFeed: [ING-DiBa Foundation Sponsorship]() Original publisher: [Read original article]() Published: 2011-10-23T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS]() Tags: [bank](), [community](), [competition](), [free](), [funding](), [open-source](), [os](), [react](), [reactos](), [sponsorship](), [win32](), [winapi]() ### AI overview The ReactOS Foundation is participating in an ING-DiBa AG competition in which the top 1,000 foundations receive a EUR 1,000 donation. The article asks community members to vote to help ReactOS remain among the winners. ### Source excerpt The German ING-DiBa AG bank is running a competition which people have until November 15th to vote on which foundation they support. The top 1000 foundations will receive a 1000EUR donation from the bank. At the time of writing the ReactOS Foundation is sitting at 9th place, but three weeks is a long time for other projects to catch up and perhaps even bump ReactOS from the top 1000. Instructions for how to vote are located here and requires only an email.