Introduction

The world of open source is full of passion and strong convictions. This can lead to disputes that arise from ideological differences around open source. But sometimes, strong convictions about open source converge with polarizing political debates to further raise the temperature within open source communities. 

This need not be the case, however. The recent controversy surrounding laptop maker Framework and its sponsorship of certain open source projects offers a powerful case study in the importance of proactive, transparent governance.

The Framework Controversy: A “Big Tent” with a Hole in it

Framework is a company that manufactures repairable and customizable laptops. Because it supports Linux-based OS options for its laptops, Framework has built a large customer base of Linux enthusiasts and touts itself as a supporter of open source software. Consequently, although Framework is not a commercial open source software (COSS) company per se, its customer base includes a large number of open source enthusiasts. 

Framework recently found itself embroiled in a heated debate within its community. The controversy began when a Debian developer, Antoine Beaupré, publicly objected to Framework’s sponsorship of two projects: Hyprland, a Wayland compositor, and Omarchy, a Linux distribution. Beaupré alleged that Hyprland fostered a “toxic and hateful community” and that Omarchy was associated with a “controversial figure”.

Framework founder Nirav Patel responded by advocating for a “big tent” approach, stating that the company partners with developers and organizations based on their alignment with “increasing the adoption of open source software,” not their personal beliefs or political stances. However, this response failed to quell the community’s concerns, and the debate quickly escalated into a “keyboard-warrior brawl” with over 1,500 replies in a single week.

This incident underscores a critical challenge for open source projects and their sponsors: in the absence of clearly defined values and principles, a “big tent” can quickly become a battleground. 

The Power of Proactive Governance

The Framework controversy could have been avoided, or at least mitigated, if the company had established a clear and transparent governance framework before the issue arose. 

A private technology business is certainly within its right to decide not to partner with certain organizations based on the controversial political views of their founders or community leaders. The business may also declare that it will not consider political views or affiliations in deciding whether to partner with that organization. What’s important is that, whichever philosophy it chooses, the business establish clear written guidelines that set expectations within its user community. 

This highlights the importance of proactive, rather than reactive, governance. In establishing the culture and principles of an open source project, project maintainers and the companies that support them should think beyond simply choosing a license. Rather, they should create mechanisms that cultivate a healthy community. This requires a thoughtful and deliberate approach to defining the project or company’s values, principles, and expectations for behavior. The following documents are essential for building a strong and resilient community:

Document	Purpose
Code of Conduct	Establishes expectations for behavior, protects participants, and empowers maintainers to facilitate a healthy community.
Project Charter/Governance Model	Defines the project’s mission, principles, scope, and decision-making processes.
Sponsorship/Partnership Policy	Outlines the criteria for selecting and vetting sponsored projects and partners.

What to Include in Your Governance Documents

Code of Conduct

A Code of Conduct is the cornerstone of a healthy open source community. As the Open Source Guide emphasizes, a good Code of Conduct should clearly define:

• Where it takes effect: Does it apply only to online forums and code repositories, or also to events?
• Whom it applies to: Does it cover all community members, maintainers, and sponsors?
• What happens in case of a violation: What are the consequences for unacceptable behavior?
• How to report violations: Is there a private and secure way for community members to report incidents?

Crucially, a Code of Conduct is only as effective as its enforcement. Maintainers must be prepared to investigate all reports of misconduct seriously and fairly, and to take appropriate action when necessary.

Project Charter/Governance Model

Beyond a Code of Conduct, a well-defined Project Charter or Governance Model provides a roadmap for the project’s development and decision-making. Drawing on the Open Source Initiative’s guide to open governance, a comprehensive charter should include:

• A specific and inspiring mission statement: What is the project’s ultimate goal?
• A clear set of principles: What are the project’s core values?
• A focused scope: What are the project’s key areas of focus?
• A transparent decision-making process: How are decisions made, and who has a say?

By clearly articulating the project’s purpose and principles, a charter can help to attract like-minded contributors and avoid the kind of ideological clashes that have plagued the Framework community.

Sponsorship/Partnership Policy

For COSS and COSS-adjacent companies like Framework that stake their reputations on their support of OSS projects, a clear and transparent Sponsorship/Partnership Policy is essential. This document should outline the criteria for selecting and vetting sponsored projects and partners and should be publicly available for community review. A well-defined policy can help to ensure that a company’s financial support is aligned with its values, which sets expectations within its community.

Conclusion: Building Healthier Communities Through Clear Expectations

The Framework controversy serves as a reminder that building a successful COSS company requires more than just writing good code, building good products, or choosing the right license. It requires a conscious and deliberate effort to cultivate a healthy community. By establishing clear and transparent governance documents, open source projects and their commercial sponsors can set clear expectations and avoid unnecessary controversies, thereby ensuring that their communities remain cohesive and resilient.