Open Source Resistance: keep OSS alive on company time
AIThis post was created with the assistance of artificial intelligence (AI).

TL;DR

A manifesto led by Mike McQuaid urges developers to maintain open source software during company time without seeking permission. This challenges existing policies and emphasizes OSS as infrastructure work. The movement aims to normalize working on OSS as part of job responsibilities.

A new manifesto, authored by Mike McQuaid, calls for developers to maintain open source software during paid work hours without seeking managerial approval, asserting it as part of their job responsibilities. This movement challenges traditional policies that restrict OSS work to personal time, emphasizing the importance of OSS infrastructure for companies and the internet at large.

Before you orderOffer from Amazon

Get the latest gadgets delivered free with Prime

  • Fast, free delivery on millions of items
  • Prime Video, Amazon Music and more included
  • Member-only deals all year
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

The manifesto, published on Hacker News, advocates for treating OSS maintenance as routine infrastructure work that companies should support during work hours. McQuaid, a prominent open source maintainer, states that companies already benefit from OSS and should allow employees to contribute during paid time without bureaucratic hurdles. The movement, called The Open Source Resistance, encourages developers to take ownership of dependency maintenance, arguing that it is already part of their job, even if not officially recognized. The manifesto also warns maintainers to verify their contracts and ownership rights before working on OSS projects during work hours. It references existing initiatives like Open Source Friday and the Open Source Pledge, which promote company-supported OSS contributions and funding.

Why It Matters

This development could significantly impact how companies approach OSS maintenance, potentially leading to more formal recognition of OSS work as part of employee responsibilities. It raises questions about workplace policies, legal ownership, and the balance between employer control and developer independence. If widely adopted, it may accelerate the sustainability of critical OSS infrastructure, which underpins much of the internet and modern software.

Products Worth Considering

Apple MacBook Air 15-inch Laptop with M5 Chip, 16GB Memory, 512GB SSD, Liquid Retina Display, and Touch ID (Midnight)

Apple MacBook Air 15-inch Laptop with M5 Chip, 16GB Memory, 512GB SSD, Liquid Retina Display, and Touch ID (Midnight)

LG UltraGear 27-Inch QHD OLED Gaming Monitor, 240Hz, 0.03ms, G-SYNC Compatible, FreeSync Premium Pro, HDMI 2.1, Black

LG UltraGear 27-Inch QHD OLED Gaming Monitor, 240Hz, 0.03ms, G-SYNC Compatible, FreeSync Premium Pro, HDMI 2.1, Black

As an affiliate, we earn on qualifying purchases.

Background

Historically, OSS work has often been done on personal time, with companies relying heavily on external maintainers for critical infrastructure. Recent discussions highlight a shift towards recognizing OSS as core to business operations. The manifesto echoes longstanding debates about developer rights, employer ownership, and the ethical responsibilities of companies that depend on open source.

“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

“Nobody is entitled to your unpaid nights, weekends or family time because their business model depends on your code.”

— Mike McQuaid

“Take things into your own hands. What a company does with its budgets is not what you control. How you spend your working time is.”

— Mike McQuaid

What Remains Unclear

It is not yet clear how many companies will officially adopt this approach or modify their policies. Legal and contractual implications remain complex, and some employers may push back or enforce existing restrictions. The movement’s long-term impact on workplace policies is still uncertain.

What’s Next

Next steps include broader discussions within tech organizations, potential policy changes, and legal clarifications. Monitoring how companies respond to this movement and whether developers begin implementing these practices will be key. The movement aims to influence industry standards and possibly inspire formal policy updates.

Key Questions

Can I legally work on OSS during paid hours without my employer’s permission?

Legal considerations depend on your employment contract and local laws. It is advisable to review your agreement and consult with legal counsel if necessary before proceeding.

Will this movement lead to formal policy changes in companies?

It is uncertain. Some companies may adopt new policies supporting OSS during work hours, while others may resist. The movement aims to encourage such change but has no guarantee of widespread implementation.

How should I verify my ownership rights before working on OSS projects at work?

Review your employment contract, IP agreements, and company policies. Negotiate clear clauses that specify OSS work and ownership rights before starting contributions during work hours.

You May Also Like

The deployment. How the AI labs verticallyintegrated into the serviceslayer — the Palantir modelat scale.

Major AI labs are embedding forward-deployed engineers into enterprise deployments, transforming the services layer and reshaping industry dynamics.

Elon Musk’s SpaceXAI has been bleeding staff since its merger

Elon Musk’s SpaceXAI has seen more than 50 researchers and engineers depart since February, raising concerns over its AI development efforts.

Memory Stopped Being a Commodity

Micron’s 16 take-or-pay agreements reserve major DRAM and NAND supply through 2030, with about $22B in customer commitments.

TechCrunch Mobility: The AI skills arms race is coming for automotive

Automakers are increasingly hiring AI-focused talent and cutting traditional jobs, signaling a shift driven by AI advancements and skills competition.