TL;DR
A manifesto by Mike McQuaid urges developers to maintain open source software on company time without asking permission. The movement challenges existing norms, emphasizing OSS as essential infrastructure work that should be integrated into employment roles. The development signals a shift towards recognizing OSS maintenance as a core part of tech work.
A new movement called the Open Source Resistance is advocating for developers to maintain open source software during their paid work hours without seeking explicit permission from management. Created by prominent open source contributor Mike McQuaid, the initiative challenges the traditional approach of asking for approval and frames OSS maintenance as a vital part of infrastructure work that companies already rely on.
The movement is rooted in a manifesto that states open source work is not a hobby but an integral component of modern business operations. It emphasizes that companies benefit from OSS continuously and that maintainers should be empowered to work on these projects during paid hours without bureaucratic hurdles. The manifesto also advises maintainers to verify their employment contracts and IP ownership rights before engaging in OSS work during work time.
Mike McQuaid, a well-known figure in the open source community and creator of Homebrew, explained that he has been maintaining OSS projects during his work hours for years, negotiating contracts to ensure legal clarity. The movement also highlights existing initiatives like the Open Source Pledge and Open Source Friday, which encourage companies to support OSS work through funding or dedicated time.
Why It Matters
This development could reshape workplace norms around OSS maintenance, positioning it as a standard part of software engineering roles. For developers, it offers a pathway to sustain their open source contributions without risking employment conflicts. For companies, it underscores the importance of integrating OSS work into their infrastructure, potentially leading to more sustainable open source ecosystems and reducing the burden on individual maintainers.
However, it also raises legal and contractual questions about ownership, confidentiality, and employment policies, which remain to be clarified across different jurisdictions and organizations. The movement’s advocacy may influence future corporate policies and employment agreements related to OSS work.
Data Analysis with Open Source Tools: A Hands-On Guide for Programmers and Data Scientists
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background
Historically, open source contributions have often been seen as voluntary or outside formal employment, leading to concerns about unpaid labor and sustainability. Recent years have seen increased recognition of OSS as critical infrastructure, with companies like Google, Microsoft, and Facebook heavily relying on open source projects. Initiatives like the Open Source Pledge and Open Source Friday have sought to formalize support, but many maintainers still operate without company backing or dedicated time.
The manifesto by McQuaid builds on this background, challenging the notion that OSS work requires explicit permission and advocating for a cultural shift where maintaining dependencies and fixing bugs are treated as core infrastructure tasks, just like network or server maintenance.
“Open source software is not a hobby for your spare time. It’s infrastructure work that companies already depend on, and maintaining it should be part of your paid job.”
— Mike McQuaid
“You should verify your contract and ownership rights before doing OSS work during work hours, but don’t let bureaucratic hurdles stop you from contributing.”
— Mike McQuaid
CASASIO Office Desk Chair with Ergonomic Lumbar Support, Extra-Thick Seat Cushion, Flip-up Arms, Breathable Mesh Back, Computer Task Chair for Home Office
【𝐀𝐧 𝐞𝐫𝐠𝐨𝐧𝐨𝐦𝐢𝐜 𝐜𝐡𝐚𝐢𝐫 𝐭𝐡𝐚𝐭 𝐚𝐜𝐭𝐮𝐚𝐥𝐥𝐲 𝐡𝐚𝐬 𝐲𝐨𝐮𝐫 𝐛𝐚𝐜𝐤】The lumbar support actually moves up, down, in, and out—so no…
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
It is not yet clear how widespread adoption of this approach will be across different organizations or legal jurisdictions. Many companies still require formal approval processes, and employment contracts vary significantly. The legal implications of working on OSS during paid hours without explicit management approval remain to be fully clarified.
Gogoonike Adjustable Laptop Stand for Desk, Metal Foldable Laptop Riser Holder, Portable Desktop Book Stands, Ventilated Cooling Computer Notebook Stand Compatible with 10-15.6” Laptops
【Adjustable & Ergonomic】：This laptop stand can be adjusted to a comfortable height and angle according to your actual…
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What’s Next
Expect further discussions within the developer community and possibly shifts in company policies to formally recognize OSS work as part of employment. Legal and HR departments may begin to update contracts or create guidelines supporting this movement. Monitoring responses from corporate leadership will be key to understanding the movement’s impact.
Logitech MX Mechanical Wireless Illuminated Performance Keyboard, Tactile Quiet Switches, Backlit Keys, Bluetooth, USB-C, macOS, Windows, Linux, iOS, Android, Metal, Graphite
Tactile Quiet mechanical key switches with a satisfying tactile bump you feel – for precise feedback, reactive key…
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Is working on open source projects during work hours legally protected?
Legal protections vary by jurisdiction and employment contract. Developers should verify ownership rights and employment policies before engaging in OSS work during paid time.
Will companies support this movement officially?
Some companies already support OSS work through policies or funding, but widespread official endorsement remains uncertain. The movement aims to encourage more organizations to recognize OSS maintenance as part of the job.
What risks are involved for developers adopting this approach?
Potential risks include contractual violations or ownership disputes if contracts are not clear. Developers should review their agreements and seek legal advice if necessary.
How can developers start advocating for this change in their workplaces?
Developers can discuss the movement with managers, propose formal policies, or negotiate contracts to include OSS work during paid hours. Joining community initiatives like Open Source Friday can also help build support.
