Open Source Resistance: keep OSS alive on company time

A new movement called the Open Source Resistance is advocating for employees to dedicate work hours to maintaining open source software, asserting that it is part of their job and should not require permission. Led by Mike McQuaid, the initiative challenges traditional policies that treat OSS work as unpaid or extracurricular, emphasizing its critical role in company infrastructure.

The movement is rooted in a manifesto authored by Mike McQuaid, a prominent open source maintainer and advocate. It states that OSS work is already integral to many companies’ operations and should be recognized as such, with employees authorized to perform maintenance during paid work hours without needing managerial approval or additional paperwork.

McQuaid emphasizes that this approach aligns with how most open source has historically been maintained, often without explicit permission. The manifesto also advises employees to verify their contracts and ownership rights before engaging in OSS work during company time, highlighting the importance of legal and IP considerations.

Why It Matters

This development could shift workplace norms around open source contributions, potentially leading to more sustainable OSS ecosystems and reducing the burnout of individual maintainers. It also raises questions about employer-employee boundaries, legal ownership, and the recognition of OSS work as part of professional responsibilities, impacting both tech companies and open source communities.

Background

For years, open source software has been maintained largely by volunteers or employees supplementing their work hours. Recent calls, including McQuaid’s manifesto, challenge the traditional notion that OSS work is extracurricular, asserting it’s essential infrastructure. Movements like Open Source Friday and pledges like the Open Source Pledge have encouraged companies to support OSS financially or through dedicated time, but formal policies vary widely. This movement formalizes the idea that OSS maintenance is part of the job, not an optional activity.

“Maintainers inside companies should and can just take work time for the necessary work on the OSS code those companies already depend on.”

— Mike McQuaid

“This is about balance, not taking the piss.”

— Mike McQuaid

What Remains Unclear

It is not yet clear how widespread adoption of this approach will be or how companies will respond legally and culturally. Specific legal implications, especially regarding IP ownership and employment contracts, remain to be clarified as the movement gains traction.

What’s Next

Next steps include broader discussions within companies about OSS policies, potential formalization of work hours dedicated to OSS, and further legal clarification. Monitoring reactions from employers and legal experts will be key to understanding how this movement influences workplace norms.

Key Questions

Is maintaining open source software during work hours legally permitted?

Legal permissibility depends on employment contracts and IP agreements. Employees should verify ownership rights and negotiate clauses before engaging in OSS work during paid hours.

Will companies officially support this movement?

Some companies already support OSS during work hours or through funding. Broader adoption depends on organizational policies and cultural shifts, which are still evolving.

Does this mean employees can work on OSS projects without approval?

The movement advocates for employees to do so, but legal and contractual considerations vary. Employees should review their agreements and consult legal advice if unsure.

How does this impact open source sustainability?

If widely adopted, it could lead to more consistent and sustainable OSS maintenance, reducing burnout and ensuring critical infrastructure remains well-maintained.