Recommended Free Tools
Yes—competitors can work together on open-source software. Antitrust risk usually comes from using a technical project to coordinate commercial behavior or exchange competitively sensitive information, not from sharing code or solving interoperability problems. Open-source status does not suspend competition law. Participants should follow the policy governing the project, keep meetings technical and governance-focused, document what happens, and refer fact-specific questions to their own counsel.
What antitrust law means for an open-source project
Open-source projects commonly include employees from several companies, including companies that compete in the same market. The Linux Foundation’s LFC105 course is aimed at contributors, maintainers, steering-committee members and governing-board members because that mixed-participant structure creates practical compliance questions.
The central distinction is between technical collaboration and commercial coordination. Designing an API, fixing a vulnerability, agreeing on an interoperability test or reviewing code is not automatically an antitrust violation. A project becomes riskier when participants use it to align prices, bids, customers, suppliers, output, product launches or other independent business decisions.
Foundation policies are project rules and educational guidance; they are not statutes and do not decide whether conduct is lawful in a particular jurisdiction. The Linux Foundation’s U.S. policy, amended by its Board on October 27, 2007, says its goal is “to encourage vigorous competition.” Linux Foundation Europe’s policy states: “Technical participation in any Project shall be open to all, subject only to compliance with the policies of LF Europe, including without limitation the provisions of the charter applicable to such Project.” Neither statement is a blanket legal approval of every project arrangement.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
Which rules and policies apply?
| Source | What it provides | What it does not provide |
|---|---|---|
| Linux Foundation Antitrust Policy (U.S.) | Rules for Foundation activities, examples of prohibited commercial subjects, and a direction to consult counsel. | It is not a case-specific legal opinion or a substitute for applicable law. |
| Linux Foundation Europe Antitrust Policy | Operational meeting safeguards, protest-and-exit instructions, and provisions concerning project requirements and alternatives. | It does not make every standards or licensing decision lawful. |
| European Union competition law | TFEU Articles 101–106 are the treaty competition provisions. Article 101 addresses restrictive agreements; Article 102 addresses abuse of a dominant position. | A high-level summary cannot determine how a particular software market or project will be treated. |
| U.S. guidance | The Federal Trade Commission’s Competition Guidance index points to DOJ/FTC guidance on competitor collaborations and intellectual-property licensing. | An index is not a project-specific analysis or a safe harbor. |
Use the policy adopted by the actual project or meeting, and then apply the law of every relevant jurisdiction. A foundation policy may impose process requirements even where a legal rule is uncertain.
What should participants avoid discussing?
The U.S. Linux Foundation policy identifies these subjects as inappropriate for project meetings:
- Current or future prices, discounts or margins
- Bids, tenders or other offer terms
- Individual product plans, including launch plans
- Decisions about particular customers or suppliers
- Individual company costs
Linux Foundation Europe’s policy describes a broader set of sensitive information. Depending on the meeting and governing policy, avoid discussion of:
- Supply, production, capacity or inventory
- Market shares
- Confidential business strategy
- Customer or supplier conduct
- Prices, bids, costs and individual product plans
Do not assume that a statement is safe because it is informal, hypothetical or made by one employee. A comment such as “What price will your company charge after this release?” can invite coordination even if nobody reaches an explicit agreement. Move the conversation back to project requirements, code, security, interoperability, release mechanics or governance.
How to run a safer project meeting
Before the meeting
- Distribute an agenda limited to the technical or governance decisions the group must make.
- Identify the antitrust policy that governs the project and meeting.
- Remind attendees that commercial topics and competitively sensitive information are out of scope.
- Invite participants to send legal questions to their own counsel rather than debating them in the technical meeting.
During the meeting
- Keep discussion tied to requirements, implementation, interoperability, security, testing and project administration.
- Stop or redirect questions about prices, bids, costs, customers, suppliers, capacity, market shares, inventory, launch timing or confidential strategy.
- Do not solicit a competitor’s internal forecast or disclose your employer’s nonpublic plans.
- Have the chair state the reason for the redirection so the boundary is clear to everyone.
After the meeting
- Prepare accurate minutes and distribute them where the governing policy requires.
- Record the technical decision and its rationale, not private commercial speculation.
- Escalate unresolved questions to counsel. The U.S. policy directs participants to contact their respective counsel and identifies the Foundation’s General Counsel for questions about a proposed course of action.
Agendas and minutes are not cosmetic paperwork. They create a contemporaneous record that the group had a defined technical purpose and did not silently accept a commercial discussion.
What should a chair do if someone raises pricing?
Interrupt promptly and make the boundary explicit. A chair can say: “That is a commercial topic outside this project meeting. We will discuss only the technical requirement and implementation.” Do not ask follow-up questions that cause participants to reveal more information.
Rank #3
- Used Book in Good Condition
If the discussion appears to continue into a prohibited area, the Linux Foundation Europe policy instructs participants to protest, leave if the discussion continues, and seek to have the protest reflected in the minutes. A participant should identify the objection clearly, avoid contributing further to the topic, and preserve the record of the objection. The exact procedure depends on the policy governing that meeting.
Can an open-source project set technical standards?
Technical standard-setting is not the same as agreeing on prices or dividing customers, but it still needs careful governance. Linux Foundation Europe’s policy says project requirements are voluntary, and it prohibits restricting alternatives or preventing the supply of products that do not conform to a project requirement.
In practice, define requirements by objective technical needs such as interoperability, security or compatibility. Keep alternative implementations possible where the project’s rules require it, and do not use a specification to exclude a rival product for commercial reasons. These are policy safeguards, not a declaration that every standard-setting arrangement satisfies competition law.
Responsibilities by project role
Contributors
- Use project channels for technical work, not employer-to-employer commercial coordination.
- Do not share nonpublic company data or request it from another participant.
- Object when a discussion crosses the policy boundary and follow the applicable protest-and-exit procedure.
Maintainers and meeting chairs
- Publish a narrow agenda and give the antitrust reminder.
- Redirect or stop sensitive topics immediately.
- Ensure minutes are accurate and distributed as required.
- Escalate difficult questions instead of improvising a legal conclusion.
Steering committees and governing boards
- Adopt and clearly identify the policy that applies to each project activity.
- Train people who chair meetings or approve requirements.
- Keep governance decisions separate from member companies’ pricing, sales, capacity and product decisions.
- Provide a route to counsel for country-specific questions.
Organizations sending employees
- Give participating staff instructions on the project policy and their own competition-law obligations.
- Review unusual collaborations, licensing proposals or standards decisions with qualified counsel.
- Do not treat an employee’s project role as authority to bind the company to a competitor’s commercial plan.
How U.S. and EU concepts differ
The European Commission’s overview describes Article 101 as covering agreements between independent market operators that restrict competition, with price fixing and market sharing as examples. It describes Article 102 as prohibiting abuse by a firm holding a dominant position, including conduct such as unfair prices, limiting production or refusing to innovate to consumers’ detriment. Those are summary descriptions, not a complete test for an open-source project.
The Commission identifies the Treaty on the Functioning of the European Union as the source of the basic provisions and Articles 101–106 as the treaty competition rules. Its legislation materials distinguish legislation from Commission guidance, guidelines and notices: guidance is not itself the same thing as a treaty rule, although a notice may have legal effects and guidelines can describe the Commission’s enforcement practice.
For U.S. matters, consult current DOJ and FTC material on competitor collaborations and intellectual-property licensing, as well as counsel familiar with the project’s markets. A project with participants, customers or operations in several countries may require a coordinated review rather than a single-country answer.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesBest Value
What to do when a concern arises
- Stop sharing or soliciting the sensitive information.
- State the objection in plain language and ask the chair to redirect the discussion.
- Follow the governing policy’s protest, departure and minutes procedure if the discussion continues.
- Preserve the agenda, minutes and relevant correspondence.
- Ask your organization’s qualified antitrust counsel for advice on the facts and jurisdictions involved.
Neither a permissive license nor a public repository changes the need for this process. The relevant question is what participants did, what information they exchanged, the market context and which law applies.
Is LFC105 useful training?
Linux Foundation Education lists LFC105 as beginner-level, self-paced material intended for contributors, maintainers, steering-committee members and governing-board members. The listing showed one hour of course material, 90 days of online access and a displayed price of $0 when checked in 2026; those commercial terms can change. It is general education, not tailored legal advice. For a compliance program, compare any training by jurisdictional coverage, role-specific meeting guidance, source authority, freshness and whether it explains how to document and escalate an incident.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
