Skip to main content

Creative and IP rights · France and Switzerland : separate country-labelled rules

Open-source licences: check a software release

Shipping software with open-source components requires a licence-by-licence review, not a general choice between open source and SaaS. France and Switzerland supply their own copyright context, while the actual licence governs its contractual conditions. Record versions, modifications, notices, distribution method and corresponding-source arrangements. A GPL example must not be presented as the rule for every open-source licence.

  • Component and version
  • Exact licence text
  • Changes made
  • Distribution method
  • Official texts cited
  • Sources checked on
  • Drafted with AI assistance, our method

General legal information with official references and dated checks. It is not personalised advice: for a decision that commits you, have your situation checked by a qualified professional.

Julie by AlphaDeep

Illustrative conversation
Example question

Which licence applies to each version?

Julie Illustration

Keep the exact text and provenance. An open-source label does not summarise every permission and condition.

Read the references

Your question concerns “Open-source licences: check a software release”. I can help organise the facts and records. Which document have you received or prepared, and is this a French or Swiss matter?

French law

3 free questions at signup. Avoid names and sensitive information.

Tool

Which records are still missing from your file?

Indicate which records you have. The result identifies gaps and prepares a complete question for Julie, without requiring an account.

julie://tool/memoireNothing leaves your browser

Answers stay on this page until you explicitly continue to Julie. Avoid names and sensitive information.

Fictional example · Your preparation

Point to complete: Distribution method. Separate source delivery, binaries and service access. Different delivery models cannot be resolved by one blanket distribution conclusion.

Component and version
Record available
Exact licence text
Record available
Changes made
Record available
Distribution method
Needs checking
Records indicated
3 / 4
  1. How will recipients receive the software?

This worksheet organises records; it does not establish admissibility, entitlement or a procedural outcome.

Answer

Which components will actually ship?

Inventory the versions and dependencies in the delivered build, rather than only the project's initial dependency list.

Code de la propriété intellectuelle art. L122-6Code de la propriété intellectuelle art. L122-6-1231.1 : Art. 2 Définition231.1 : Art. 10 Utilisation de l’œuvre231.1 : Art. 16 Transfert des droitsFree Software Foundation : GNU GPL version 3

Preparation schematic: connect records and questions. It does not guarantee a legal outcome. Open-source licences: check a software release
Preparation schematic: connect records and questions. It does not guarantee a legal outcome.
Comparison

Which documents answer which questions?

Which documents answer which questions?
Record or informationIssue to check
Component and versionInventory the versions and dependencies in the delivered build, rather than only the project's initial dependency list.
Exact licence textKeep the exact text and provenance. An open-source label does not summarise every permission and condition.
Changes madeDistinguish unchanged code, modifications and added components. The actual operation matters when assessing licence duties.
Distribution methodSeparate source delivery, binaries and service access. Different delivery models cannot be resolved by one blanket distribution conclusion.

Code de la propriété intellectuelle art. L122-6Code de la propriété intellectuelle art. L122-6-1231.1 : Art. 2 Définition231.1 : Art. 10 Utilisation de l’œuvre231.1 : Art. 16 Transfert des droitsFree Software Foundation : GNU GPL version 3

Answer

Which licence applies to each version?

Keep the exact text and provenance. An open-source label does not summarise every permission and condition.

The law

Which official provision helps explain this situation?

Sous réserve des dispositions de l'article L. 122-6-1, le droit d'exploitation appartenant à l'auteur d'un logiciel comprend le droit d'effectuer et d'autoriser :

Code de la propriété intellectuelle art. L122-6In force since 11 May 1994Read on Légifrance

In plain English: CPI L122-6 addresses software reproduction, adaptation and distribution with relevant special provisions. Public repository access is not unlimited permission.

Answer

What was modified?

Distinguish unchanged code, modifications and added components. The actual operation matters when assessing licence duties.

Answer

How will recipients receive the software?

Separate source delivery, binaries and service access. Different delivery models cannot be resolved by one blanket distribution conclusion.

Answer

What is the French statutory starting point?

CPI L122-6 addresses software reproduction, adaptation and distribution with relevant special provisions. Public repository access is not unlimited permission.

Code de la propriété intellectuelle art. L122-6Code de la propriété intellectuelle art. L122-6-1231.1 : Art. 2 Définition231.1 : Art. 10 Utilisation de l’œuvre231.1 : Art. 16 Transfert des droitsFree Software Foundation : GNU GPL version 3

Answer

What is the Swiss statutory starting point?

The Swiss Copyright Act includes computer programs and reserves relevant exploitation rights. The actual licence still determines its own conditions.

Code de la propriété intellectuelle art. L122-6Code de la propriété intellectuelle art. L122-6-1231.1 : Art. 2 Définition231.1 : Art. 10 Utilisation de l’œuvre231.1 : Art. 16 Transfert des droitsFree Software Foundation : GNU GPL version 3

Answer

How should an unidentified licence be handled?

Keep that component visibly unverified and locate the original terms. Do not silently treat missing information as unrestricted use.

Answer

What does the delivery record contain?

It connects components, versions, licences, changes and delivery. It does not automatically certify compatibility or legal compliance.

Frequent questions

What other questions arise in this file?

Which licence applies to each version?

How will recipients receive the software?

What is the French statutory starting point?

How should an unidentified licence be handled?

Sources

Which official references should you consult?

  1. Code de la propriété intellectuelle art. L122-6Légifrance
  2. Code de la propriété intellectuelle art. L122-6-1Légifrance
  3. 231.1 : Art. 2 DéfinitionFedlex
  4. 231.1 : Art. 10 Utilisation de l’œuvreFedlex
  5. 231.1 : Art. 16 Transfert des droitsFedlex
  6. Free Software Foundation : GNU GPL version 3Source officielle

Texts cited last checked: 1 November 2026