Open Source Software

We help the ETH Zurich community learn, use, contribute to, and benefit from Open Source Software (OSS) by providing resources and support to facilitate the use and distribution of OSS, sharing insights and best practices for effective OSS management, and promoting the strategic use of OSS to drive both social impact and commercial success.

The Open Source Definition (OSD)

Open source doesn’t just mean access to the source code. The license of open source software must comply with the following 10 criteria, as defined by the external page Open Source Initiative (OSI) (Version 1.9, last modified 2007-03-22)

Source Code

The software must include source code and allow distribution in both source and compiled forms. There must be a well-publicized way to obtain the source code, which should be in a form that programmers can easily read and modify. Deliberately obfuscated source code is not allowed. 

No Discrimination Against Persons or Groups

Equal access for all users.

No Discrimination Against Fields of Endeavor

Cannot restrict use in specific fields or applications, like business or research. 

License Must Not Restrict Other Software

The License cannot place restrictions on other software distributed alongside. 

License Must Not Be Specific to a Product

Rights cannot be tied to a specific product or being part of a particular distribution. 

Free Redistribution

The license cannot limit or charge a fee for selling or sharing the software as part of a bundled software distribution.

Derived Works

The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.

Integrity of Author's Source Code

May restrict modified source distribution if patch files are allowed. Must permit distribution of software built from modified source code.

Distribution of License

Rights must apply to all to whom the software is redistributed without requiring them to sign a separate license.

 

License Must Be Technology-Neutral

The license cannot depend on any specific technology or type of interface.

Open source software (OSS) refers to software that is distributed with the source code available to the public and under a license that allows anyone to view, modify, and redistribute the code. In contrast, proprietary software is closed-source, meaning its source code is kept secret by the owner, with usage governed by licensing agreements. If you are considering releasing your code as proprietary software, please proceed to License software to third parties.

OSS began with the early sharing of code among computing programmers but faced obstacles in the 1970s and 1980s as major companies viewed OSS as a threat to the proprietary models that dominated their business. The free software movement, led by Richard Stallman and the GNU Project, sought to counter these obstacles. The term "open source" emerged in the late 1990s to promote collaboration and gain broader appeal. Over time, skepticism over security and profitability faded as projects like Linux and Apache showcased OSS’s potential, leading even former critics to embrace open source as a key part of modern technology and innovation.

Nowadays, the choice between open source and proprietary software often depends on the specific needs and priorities of both owners and users. (See the figure below)

move

Copyright and patents are two different methods of protecting software, each focusing on different aspects of intellectual property rights.

Copyright In Switzerland, external page copyright law protect works that are literary and artistic intellectual creations with individual character, irrespective of their value or purpose. This includes, for example, literary and musical works, paintings, sculptures, films, operas, ballets and pantomimes works.

Computer programs (software) are explicitly considered works under copyright law. However, copyright does not protect the underlying ideas, algorithms, or functionality of the software—only the specific way these elements are expressed in code. 

A work is protected by copyright law as soon as it is created. In case of software, this means that as soon as the software code is written, it is copyrighted (as long as the other copyrightability requirements are fulfilled). 

For detailed information of the copyright law and ownership of software at ETH, please refer to Software and Copyright.

Patents, on the other hand, protect the underlying inventions that make the software function as a technical solution to a practical problem. A computer-implemented patent can protect new and inventive algorithms, methods, or technical solutions implemented by the software. With a patent, the inventor can prevent others from using, selling, or making the patented invention without permission.

If you are interested in applying for a patent for your invention implemented as a software, please proceed to Patenting Software.

The author of a software is the person who has materially written the program code, meaning the developer(s) or coders are considered the authors of the software. If a professor hosts an OSS project but does not directly contribute to the coding (by either writing software code or being substantially involved in code development), he or she is not considered an author under Swiss copyright law.

Under Swiss law, copyright authors have moral rights, in particular attribution rights. This means that the author has the right to be acknolwedged as the creator of software.  

Importantly, if the software was created as part of an employee’s official duties at ETH Zurich, ETH Zurich holds the exclusive rights of use and exploitation of the software (Federal Act on the Federal Institutes of Technology, external page Article 36, para. 2). This means that ETH Zurich can exclusively determine who and under what conditions can access, use, distribute, and redistribute (including license and sueblicense) the software. In this sense, ETH Zurich can be regarded as the "owner" of the software.

  • If you wish to license your code as proprietary software to a third party, it must be submitted to ETH transfer for review. ETH transfer will then draft a license agreement for the software, which must be approved and signed by the ETH Vice President for Knowledge Transfer and Corporate Relations, as well as the responsible professor. A detailed guidance can be found at licensing software.
  • If you wish to release your code under an open-source license, the decision must be approved by the responsible Research Group Leader (normally the professor in charge of the funding for this work), even if he or she is not an author of the code. This reflects the planned revision of the ETH Zurich Exploitation Guideline, while the old Exploitatoin Guideline (RSETHZ 440.4), currently still in force, requires that the decision of OSS release must always be approved by all authors.

As the OSS ecosystem operates with dynamics and mindset that differ significantly from conventional proprietary software, it is important to be fully informed about the legal, commercial, and reputational risks associated with OSS release and license management. OSS authors at ETH Zurich are strongly encouraged to visit our website, particularly the "OSS Release Checklist".

If you need further assistance with open source software or have any feedback about our website, please don't hesitate to contact us:

Dr. Ying Wang
  • HG E 36
  • +41 44 633 85 25

ETH transfer IP und Lizenzen
Rämistrasse 101
8092 Zürich
Switzerland


JavaScript has been disabled in your browser