key: c-fsl-1.1 short_name: C-FSL 1.1 name: Convertible Free Software License 1.1 category: Copyleft Limited owner: Elmar Stellnberger homepage_url: https://www.elstel.org/license/C-FSL-v1.1.txt spdx_license_key: LicenseRef-scancode-c-fsl-1.1 text_urls: - https://www.elstel.org/license/C-FSL-v1.1.txt ignorable_copyrights: - copyright 2016, by Elmar Stellnberger ignorable_holders: - Elmar Stellnberger text: "CONVERTIBLE FREE SOFTWARE LICENSE\n Version 1.1, 2016-08-11\ncopyright 2016, by Elmar\ \ Stellnberger\nEveryone is permitted to copy and distribute verbatim copies of this license\ \ document. You must not modify the license itself.\nThis license applies to any software\ \ containing a notice by the copyright holder saying that it may be used under the terms of\ \ the Convertible Free Software License. If a specific version number is mentioned then usage\ \ rights include this version as well as any newer version which will always be similar in\ \ spirit to this license. The term Convertible Free Software license may be abbreviated as\ \ C-FSL.\n\n1. Any work under this license comes completely without any warranty or any kind\ \ of liability such as lost revenues, profits, harm or damage of any kind even if the authors\ \ should have been advised of the possibility of such harm or damage. It may be seen as research\ \ work and does not claim for fitness to any particular usage purpose.\n\n2. The term 'source\ \ code' applies to the preferred form that is used to develop or apply changes to a work under\ \ this license referred to herein as 'the work'. You are allowed to modify or change the source\ \ code if you accept that the resulting changed work will become subject to this license.\ \ As soon as you apply any change this is an implicit consent to fully comply with this license\ \ and a consent that the work may be used under this license. \n\n3. It is your obligation\ \ that the changed version of your sources will be available to the public for free within\ \ the time frame of a month at least if there is no undue hindrance by the authors to make\ \ it available. Modifications which result in a broken or unusable program which the authors\ \ do not plan to continue their work on are considered dead end and do not need to be published.\ \ Available for free means that there will be no undue hindrance in obtaining the given item\ \ like a registration of the person who wants to download or obtain the given item. Available\ \ for free also means that you must not charge for the given item itself apart from the possibility\ \ to require a reasonable charge for the physical reproduction of the data.\n\n4. You are\ \ allowed to issue an 'automatic derivation process' on the source code which will result\ \ in so called 'object code'. You are obligated to provide sufficient data, tools and utilities\ \ so that a functionally equivalent object code can be compiled merely from programs and work\ \ licensed either under any open source license approved by opensource.org or under C-FSL.\ \ The given data and utilities for obtaining functionally equivalent results need to be available\ \ to the public for free.\n\n5. When applying changes to the source code you need to leave\ \ your name, your email address and the date of your modifications so that other people may\ \ contact you. If a contributor should not have a steady access to the internet or a satisfying\ \ access to an emailing service he may leave another way by which he can be contacted. We\ \ suggest to list all changes by contributors either in a separate changelog file or in the\ \ header of the changed file. Several consecutive changes may be collapsed. Furthermore you\ \ need to give your changed version a 'marker' which may be used to distinguish it from the\ \ upstream version when being distributed to other people. The distributed product needs to\ \ be of the form upstream name - dash upstream version - dash your marker optionally followed\ \ by a version number under your control. If there should be a chain of upstream contributors\ \ there only needs to be one marker by the party which is at the end of the chain as long\ \ as that chain remains to be documented in some place where it is shipped with your software.\ \ The marker needs to be unique, at least two letters in size. We suggest it to reflect the\ \ name of your company or distribution. You may always distribute an upstream version in unchanged\ \ form either with your own marker or without.\n\n6. You may choose to create a fork of a\ \ work under C-FSL by giving it a completely different name. However you need to assert that\ \ people will know that your fork is based on the original work. If your program has a graphical\ \ user interface the whole C-FSL license must be referenced via the GUI. Otherwise a plain\ \ text copy of this license needs to be given and packed alongside the distributed product.\ \ A complete reference to the base product including email address and web presence must be\ \ referenced via the GUI for any GUI program that is a fork of another C-FSL program. If your\ \ program has a comprehensive help, manual or info page and is a fork a similar reference\ \ to the base product must be given there. It does not apply to quick or short command line\ \ help output as long as a more comprehensive help page is also available. Any program under\ \ C-FSL which is a fork of another C-FSL program must ship with a reference to the base product.\ \ \n\n7. Contributing to a work under C-FSL means that you will give a group called the 'original\ \ authors' a consensus based right to re-license your derived work so that it will be available\ \ under both licenses: the C-FSL and the newly applied license. In order to re-license consensus\ \ is only required between these original authors. The original authors are the group of people\ \ who have initially started to create a work. They shall be mentioned at the beginning of\ \ the changelog or the file header of changes. As soon as there is a consensus to do so by\ \ all original authors the work may either be re-licensed, published as upstream version without\ \ a marker or new people may be accepted and mentioned as 'original authors'. \n\n8. No work\ \ under C-FSL shall be deemed part of an effective measure under anti-circumvention laws like\ \ under article 11 of the WIPO copyright treaty adopted on 1996-12-20 or any similar law.\ \ By your consent to work under this license you waive any legal power to forbid such circumventions\ \ regarding the work under C-FSL or any work combined with it. You must assert that the right\ \ to use, modify, generate object code and distribute any software under C-FSL will not be\ \ infringed by patent claims or similar law. If you modify a work under C-FSL so that it will\ \ knowingly rely on a patent license then it means that you will thereby grant to extend the\ \ patent license to any recipient of the work. Every contributor grants by the act of contributing\ \ to a work under C-FSL a non-exclusive, worldwide and royalty-free patent license to any\ \ prospective contributor or user of the given work applicable to all his 'essential patent\ \ claims'. The essential patent claims comprise all claims owned or controlled by the contributor.\n\ \n9. A work under C-FSL which has another component or plug-in as well as a work under C-FSL\ \ which is used itself as a component, plug-in, add-on of another product, any product under\ \ C-FSL which is combined or which links against another work requires that the other work\ \ will either be put under an open source license as approved by opensource.org or it needs\ \ to be put under C-FSL as well. Usage of proprietary libraries and kernel modules pose an\ \ exception to this rule. There must be a functionally equivalent open source library for\ \ any proprietary library so that a work under C-FSL can run and execute even without any\ \ proprietary library. No such restriction applies to kernel modules. The term 'kernel' refers\ \ to the core of an operating system. Libraries are separate components which link against\ \ the given work or other components. The term 'linking' refers to the relocation of references\ \ or addresses when the library is combined with another component in order to make the combined\ \ aggregate executable or runnable. Such references are bound to symbols which are part of\ \ the common interface between the library and the component which the library is combined\ \ with at runtime. Libraries which provide operating system services use a well defined binary\ \ interface but do not 'link' against the kernel.\n\n10. This license is either governed by\ \ the Laws of Austria or by the laws of the country where the first mentioned original author\ \ lives or is a resident. Disputes shall be settled by the nearest proper court given the\ \ home town or location of the first original author unless there is a common consensus for\ \ another place of court by all original authors. If any of the terms stated in this license\ \ were not in accordance with the law of the country that governs this license all other parts\ \ of the license shall remain valid."