Coding

Open Source Resistance: keep OSS alive on company time

As companies increasingly adopt "open-source everything" policies, a grassroots movement is emerging to ensure that employees can contribute to open-source projects on company time without sacrificing their intellectual property or compromising sensitive data. This pushback is centered around the concept of "open-source-compatible" enterprise software licenses, which would allow developers to contribute to OSS projects without risking corporate liability. The movement's advocates argue that such licenses are essential for preserving the integrity of open-source ecosystems.

Overview

The Open Source Resistance is a grassroots movement that advocates for employees to contribute to open-source projects on company time without sacrificing their intellectual property or compromising sensitive data. This movement is centered around the concept of "open-source-compatible" enterprise software licenses, which would allow developers to contribute to OSS projects without risking corporate liability.

What it does

The Open Source Resistance argues that maintaining open-source dependencies is already part of an employee's job, even if management refuses to acknowledge it. The movement encourages employees to take ownership of their work and contribute to open-source projects during work hours, as long as they are not compromising company secrets or violating their employment contract. This approach is seen as a way to balance the value that companies extract from open-source maintainers with the need for maintainers to sustain themselves.

The movement's advocates argue that companies already depend on open-source software and that maintaining it is essential for preserving the integrity of open-source ecosystems. They also point out that shareholders have received free open-source subsidies for decades, and that it is time for companies to give back to the open-source community.

Tradeoffs

While the Open Source Resistance movement has its benefits, it also has its limitations and potential drawbacks. For example, employees who contribute to open-source projects during work hours may face objections from their employers, who may view this as "time theft" or "stealing from shareholders." Additionally, employees who are junior or precarious may not have the leverage to absorb the potential downside of contributing to open-source projects during work hours.

To mitigate these risks, the movement's advocates recommend that employees verify their contract, keep confidential information at work, and make sure they own the open-source IP they ship. They also suggest that employees negotiate their IP agreement and ask for an open-source carve-out in writing before signing their employment contract.

In conclusion, the Open Source Resistance movement is a call to action for employees to take ownership of their work and contribute to open-source projects during work hours. While it has its limitations and potential drawbacks, it also has the potential to benefit both employees and companies by promoting a more sustainable and equitable open-source ecosystem.

Practical takeaway: If you are an open-source maintainer, consider negotiating an open-source carve-out in your employment contract and contributing to open-source projects during work hours, as long as you are not compromising company secrets or violating your employment contract. This can help you balance your work and personal life while also giving back to the open-source community.

{ "headline": "Open Source Resistance Movement", "synthesis": "The Open Source Resistance is a grassroots movement that advocates for employees to contribute to open-source projects on company time. The movement argues that maintaining open-source dependencies is already part of an employee's job and encourages employees to take ownership of their work and contribute to open-source projects during work hours.", "tags": ["Open Source", "Resistance Movement", "Grassroots"], "sources_used": ["https://ossresistance.com/"]

Similar Articles

More articles like this

Coding 1 min

Fragnesia Made Public as Latest Linux Local Privilege Escalation Vulnerability

A previously undisclosed local privilege escalation vulnerability, dubbed Fragnesia, has been disclosed in the Linux kernel, exposing a critical flaw in the ext4 file system's handling of extended attributes. The vulnerability, assigned CVE-2023-41692, allows attackers to bypass access controls and execute arbitrary code with elevated privileges. Fragnesia affects Linux distributions as far back as kernel version 4.15.

Coding 2 min

The limits of Rust, or why you should probably not follow Amazon and Cloudflare

Rust's promise of memory safety is being put to the test as Amazon and Cloudflare's high-profile migrations to the language reveal a disturbing trend: the more complex the system, the more it exposes the limitations of Rust's borrow checker. Specifically, the language's inability to handle cyclic references and its reliance on manual memory management are causing headaches for developers. As a result, some are questioning whether Rust is truly ready for prime-time.

Coding 1 min

The AI Backlash Could Get Ugly

As the AI industry's carbon footprint and data storage needs continue to balloon, a growing coalition of environmental activists and community organizers is linking the expansion of data centers to rising rates of political violence and displacement, sparking a contentious debate over the true costs of AI's accelerating growth. The movement's focus on data center siting and energy consumption has already led to high-profile protests and municipal ordinances restricting new facility development.

Coding 2 min

The US is winning the AI race where it matters most: commercialization

As the global AI landscape shifts towards practical applications, the US is gaining a decisive edge in commercializing cutting-edge technologies, with a surge in AI-powered product deployments and a growing ecosystem of specialized startups and venture capital firms. This momentum is driven by the increasing adoption of cloud-based infrastructure, particularly Amazon Web Services and Google Cloud Platform, which provide scalable resources for AI model training and deployment.

Coding 1 min

Software Developers Say AI Is Rotting Their Brains

As AI-driven development tools increasingly rely on opaque, black-box models, software engineers are reporting a surge in cognitive dissonance, with many citing the inability to understand or debug complex neural networks as a major contributor to mental fatigue and decreased job satisfaction. This phenomenon is particularly pronounced in the use of large language models, which often employ transformer architectures and billions of parameters. The resulting "explainability gap" threatens to undermine the productivity gains promised by AI-assisted coding.

Coding 1 min

The Emacsification of Software

A quiet revolution is underway as software development increasingly adopts a modal editing paradigm, mirroring the customizable, extensible workflow of the venerable Emacs text editor. This "Emacsification" of software is driven by the proliferation of domain-specific languages (DSLs) and extensible frameworks, which enable developers to craft bespoke workflows and toolchains that rival the complexity of traditional IDEs. The result is a more flexible, efficient, and expressive software development process.