La loi et le Logiciel Libre.

Exploration profane des interactions entre la loi et le Logiciel Libre

Loïc Dachary Biographie

http://en.wikipedia.org/wiki/Loic_Dachary

Sujets abordés

Sujets non abordés

Le droit d'auteur.

Traités OMPI.

La formation du contrat.

Le droit d'utilisation.

http://www.april.org/livre-blanc-sur-les-modeles-economiques-du-logiciel-libre

Le droit d'étudier.

Le droit de modifier et distribuer.

Le droit moral et exctinction.

Implémenter une idée ou un clone

http://cardstori.es/

Copyleft et transmission du partage.

Copyleft et mises à jour.

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

GPLv3 non modifiable

Copyright (C) 2007 Free Software Foundation, Inc. http://fsf.org/ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

GPLv3 préambule : l'objectif poursuivit

The GNU General Public License is a free, copyleft license for software and other kinds of works.

The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.

GPLv3 préambule : le prix et les sources

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.

GPLv3 préambule : l'interdiction

To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.

GPLv3 préambule : l'information et la propagation

For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

GPLv3 préambule : a quoi sert cette licence ?

Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.

GPLv3 préambule : pas de garantie

For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.

GPLv3 préambule : la tivoisation

Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.

GPLv3 préambule : les brevets

Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.

GPLv3 fin de la mise en contexte

The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS

GPLv3 0. Definitions

A suivre dans le cours de la lecture.

GPLv3 1. Source Code.

The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work.

GPLv3 1. Source Code.

A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.

GPLv3 1. Source Code.

The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.

GPLv3 1. Source Code.

The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.

GPLv3 1. Source Code.

The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.

The Corresponding Source for a work in source code form is that same work.

GPLv3 2. Basic Permissions.

All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.

GPLv3 2. Basic Permissions.

You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.

GPLv3 2. Basic Permissions.

Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.

GPLv3 3. Protecting Users' Legal Rights From Anti-Circumvention Law.

No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.

GPLv3 3. Protecting Users' Legal Rights From Anti-Circumvention Law.

When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.

GPLv3 4. Conveying Verbatim Copies.

You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.

You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.

GPLv3 5. Conveying Modified Source Versions.

You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:

GPLv3 5. Conveying Modified Source Versions.

a) The work must carry prominent notices stating that you modified it, and giving a relevant date.

b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices".

GPLv3 5. Conveying Modified Source Versions.

c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.

GPLv3 5. Conveying Modified Source Versions.

d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.

GPLv3 5. Conveying Modified Source Versions.

A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.

GPLv3 6. Conveying Non-Source Forms.

You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:

a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.

GPLv3 6. Conveying Non-Source Forms.

b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.

GPLv3 6. Conveying Non-Source Forms.

c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.

GPLv3 6. Conveying Non-Source Forms.

d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.

GPLv3 6. Conveying Non-Source Forms.

e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.

GPLv3 6. Conveying Non-Source Forms.

A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.

GPLv3 6. Conveying Non-Source Forms.

A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.

GPLv3 6. Conveying Non-Source Forms.

"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.

GPLv3 6. Conveying Non-Source Forms.

If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).

GPLv3 6. Conveying Non-Source Forms.

The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.

GPLv3 6. Conveying Non-Source Forms.

Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.

GPLv3 7. Additional Terms.

"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.

GPLv3 7. Additional Terms.

When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.

GPLv3 7. Additional Terms.

Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:

GPLv3 7. Additional Terms.

a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or

b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or

c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or

GPLv3 7. Additional Terms.

d) Limiting the use for publicity purposes of names of licensors or authors of the material; or

e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or

f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.

GPLv3 7. Additional Terms.

All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.

GPLv3 7. Additional Terms.

If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.

Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.

GPLv3 8. Termination.

You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).

GPLv3 8. Termination.

However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.

GPLv3 8. Termination.

Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.

GPLv3 8. Termination.

Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.

GPLv3 9. Acceptance Not Required for Having Copies.

You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.

GPLv3 10. Automatic Licensing of Downstream Recipients.

Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.

GPLv3 10. Automatic Licensing of Downstream Recipients.

An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.

GPLv3 10. Automatic Licensing of Downstream Recipients.

You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.

GPLv3 11. Patents.

A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.

GPLv3 12. No Surrender of Others' Freedom.

If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.

GPLv3 13. Use with the GNU Affero General Public License.

Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.

GPLv3 14. Revised Versions of this License.

The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

GPLv3 14. Revised Versions of this License.

Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.

GPLv3 14. Revised Versions of this License.

If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.

Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.

GPLv3 17. Interpretation of Sections 15 and 16.

If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.

Questions réponses

Est-ce que logiciel libre signifie utiliser la GPL ?

Est-ce que logiciel libre signifie utiliser la GPL ?

Absolument pas—il y a beaucoup d'autres licences de logiciels libres. Toute licence qui offre à l'utilisateur certaines libertés spécifiques est une licence de logiciel libre.

Pourquoi devrais-je utiliser la GNU GPL plutôt que d'autres licences de logiciel libre ?

Pourquoi devrais-je utiliser la GNU GPL plutôt que d'autres licences de logiciel libre ?

En utilisant la GNU GPL vous exigerez que toutes les versions améliorées diffusées soient du logiciel libre. Ceci signifie que vous pouvez éviter le risque d'avoir à entrer en compétition avec une version modifiée propriétaire de votre propre travail. Cependant, dans certaines situations il peut être préférable d'utiliser une licence plus permissive.

Que devrais-je faire si je découvre une violation potentielle de la GPL ?

Que devrais-je faire si je découvre une violation potentielle de la GPL ?

Vous devriez la signaler. Tout d'abord, vérifiez les faits du mieux que vous pouvez. Puis signalez-le à l'éditeur ou au détenteur du copyright du programme en question couvert par la GPL. Si c'est la Free Software Foundation, écrivez à. Sinon, le mainteneur du programme pourrait être le détenteur du copyright, ou pourrait sinon vous dire comment contacter le détenteur du copyright, donc signalez- le au mainteneur.

Pourquoi la GPL permet-elle aux utilisateurs de publier leur versions modifiées ?

Pourquoi la GPL permet-elle aux utilisateurs de publier leur versions modifiées ?

Un aspect crucial du logiciel libre est que les utilisateurs sont libres de coopérer. Il est absolument essentiel de permettre aux utilisateurs qui désirent s'entraider de partager leurs patches et améliorations avec d'autres. Certains ont proposé des alternatives à la GPL qui requièrent que la version modifiée passe par l'auteur original. Tant que l'auteur original assure la maintenance nécessaire, ceci peut fonctionner en pratique, mais si l'auteur cesse (plus ou moins) et passe à autre chose, ou ne répond pas aux besoins de tous les utilisateurs, cette manière de procéder s'effondre. En plus des problèmes pratiques, cette façon de faire ne permet pas aux utilisateurs de s'entraider. Quelquefois, le contrôle sur les versions modifiées est proposé comme un moyen d'éviter des confusions entre les différentes versions faites par les utilisateurs. Notre expérience nous a montré qu'il ne s'agit pas d'un problème majeur. De nombreuses versions d'Emacs ont été faites en dehors du cadre du Projet GNU, mais les utilisateurs peuvent les différencier. La GPL requiert que l'auteur d'une version mette son nom dessus, pour la distinguer des autres versions et protéger la réputation des autres mainteneurs.

Puis-je avoir un programme couvert par la GPL et programme non-libre indépendant sur le même ordinateur ?

Puis-je avoir un programme couvert par la GPL et programme non-libre indépendant sur le même ordinateur ?

Oui.

Dois-je revendiquer mon droit d'auteur pour mes modifications sur un programme couvert par la GPL ?

Dois-je revendiquer mon droit d'auteur pour mes modifications sur un programme couvert par la GPL ?

Vous n'êtes pas obligé de revendiquer un copyright sur vos modifications. Dans la plupart des pays, cependant, ceci arrive automatiquement par défaut, aussi vous devrez mettre de façon explicite les modifications dans le domaine public si vous ne voulez pas qu'elles soient sous copyright. Que vous revendiquiez ou non un copyright sur vos modifications, vous devrez publier la version modifiée, dans son entier, sous la GPL (si vous la publiez).

Est-ce que la GPL m'autorise à vendre des copies payantes de mon programme ?

Est-ce que la GPL m'autorise à vendre des copies payantes de mon programme ?

Oui, la GPL autorise cela pour tout le monde. Le droit de vendre des copies est une partie de la définition du logiciel libre.

Est-ce que la GPL m'autorise à exiger que quiconque reçoit le logiciel doive me payer un montant et/ou me le signaler ?

Est-ce que la GPL m'autorise à exiger que quiconque reçoit le logiciel doive me payer un montant et/ou me le signaler ?

Non. D'ailleurs, une telle exigence rendrait le programme non-libre. Si l'on doit payer pour recevoir une copie d'un programme, ou si l'on doit le signaler à quelqu'un en particulier, alors le programme n'est pas libre. Voir la définition du logiciel libre. La GPL est une licence de logiciel libre, et par conséquent elle permet l'utilisation et même la redistribution du logiciel sans que l'on ait à payer de droit à quiconque pour cela.

La GPL me permet-elle de distribuer une version modifiée ou beta sous accord de non divulgation ?

La GPL me permet-elle de distribuer une version modifiée ou beta sous accord de non divulgation ?

Non. La GPL dit que quiconque reçoit une copie de votre version de votre part a le droit de redistribuer des copies (modifiées ou non) de cette version. Elle ne vous donne pas le droit de distribuer votre travail avec plus de restrictions. Si quelqu'un vous demande de signer un accord de non divulgation pour recevoir un logiciel sous copyright de la FSF, veuillez nous en informer immédiatement en écrivant à license-violation@fsf.org. Si la violation concerne du code couvert par la GPL ayant un autre détenteur de copyright, veuillez en informer le détenteur, tout comme vous le feriez pour toute autre violation de la GPL.

Je veux que mon travail soit reconnu. Je veux que les gens sachent ce que j'ai écrit. Puis-je encore être reconnu si j'utilise la GPL ?

Je veux que mon travail soit reconnu. Je veux que les gens sachent ce que j'ai écrit. Puis-je encore être reconnu si j'utilise la GPL ?

Votre travail doit certainement être reconnu. La distribution d'un programme sous licence GPL doit aussi se traduire par la mention d'un copyright à votre propre nom (à supposer que vous déteniez ce copyright). La GPL requiert que chaque copie porte une mention de copyright appropriée.

Pourquoi la GPL exige-t-elle d'inclure une copie de la GPL avec chaque copie du programme ?

Pourquoi la GPL exige-t-elle d'inclure une copie de la GPL avec chaque copie du programme ?

Le fait d'inclure une copie de la licence avec le programme est vital, ainsi tous ceux qui reçoivent une copie du programme peuvent connaître leurs droits Il peut paraître tentant d'inclure une URL qui réfère à cette licence, au lieu de la licence elle-même. Mais vous ne pouvez pas être sûr que cette URL sera toujours valable dans cinq ou dix ans. Dans vingt ans, les URL que nous connaissons aujourd'hui n'existeront peut-être plus. La seule façon de s'assurer que les détenteurs de copies du programme pourront continuer à voir les licences, malgré les changements qui apparaîtront dans le réseau, est d'inclure une copie de la licence dans le programme.

Puis-je ôter le préambule de la GPL, ou les instructions sur la façon de l'utiliser dans vos propres programmes, pour économiser de l'espace ?

Puis-je ôter le préambule de la GPL, ou les instructions sur la façon de l'utiliser dans vos propres programmes, pour économiser de l'espace ?

Le préambule et les instructions sont des portions intégrales de la GNU GPL et ne peuvent être supprimées. Lisez s'il vous plaît l'ensemble de la GPL. En fait, la GPL est sous copyright, et sa licence permet seulement de la recopier telle-quelle dans son intégralité. Le préambule et les instructions ajoutent environ 5000 caractères, moins d'1/3 de la taille totale de la GPL. Ils ne constitueraient pas un changement substantiel de la taille d'un paquetage logiciel à moins que ce paquetage lui-même soit vraiment petit. Dans ce cas, vous pourriez aussi bien utiliser une licence totalement permissive au lieu de la GNU GPL.

Comment obtenir un droit d'auteur sur mon programme de façon à le distribuer sous la GPL ?

Comment obtenir un droit d'auteur sur mon programme de façon à le distribuer sous la GPL ?

Selon la Convention de Berne, tout écrit est automatiquement sous copyright dès qu'il est placé sous une forme fixe. Donc vous n'avez rien à faire pour « obtenir » un copyright sur ce que vous écrivez—dès lors que personne d'autre ne peut prétendre posséder votre travail. C'est toutefois une excellente idée d'enregistrer votre copyright aux État-Unis. Cela vous donnera plus d'influence pour traiter avec une violation aux États-Unis. Il se peut que quelqu'un d'autre puisse réclamer le copyright si vous êtes un employé ou un étudiant; alors, l'employeur ou l'école peuvent prétendre que vous avez effectué le travail pour eux, et que le copyright leur appartient. La validité de leurs prétentions dépend des circonstances telles que les lois de votre lieu de résidence, votre contrat d'embauche et le genre de travail que vous faites. Le mieux est de consulter un avocat s'il y a le moindre doute. Si vous pensez que l'employeur ou l'école peuvent avoir des droits, vous pouvez résoudre le problème clairement en obtenant une renonciation au copyright signée par un officiel autorisé de l'entreprise ou de l'école. (Votre supérieur hiérarchique immédiat ou votre professeur ne sont généralement PAS autorisés à signer de telles renonciations).

J'ai entendu parler de quelqu'un qui a obtenu une copie d'un programme en GPL sous une autre licence. Cela est-il possible ?

J'ai entendu parler de quelqu'un qui a obtenu une copie d'un programme en GPL sous une autre licence. Cela est-il possible ?

La GNU GPL ne donne pas le droit aux utilisateurs d'attacher d'autres licences au programme. Mais le détenteur du copyright sur un programme peut le publier sous différentes licences en parallèle. L'une d'entre-elles peut être la GNU GPL. La licence qui se trouve dans votre copie, en supposant qu'elle y ait été mise par le détenteur du copyright et que vous aillez acquis cette copie de façon légitime, est la licence qui s'applique à votre copie.

Dans quels cas le résultat produit par un programme sous GPL est-il également couvert par la GPL ?

Dans quels cas le résultat produit par un programme sous GPL est-il également couvert par la GPL ?

Seulement quand le programme copie des portions de lui-même dans le résultat.

Quelle est la différence entre « aggrégation » et d'autres types de «versions modifiées » ?

Quelle est la différence entre « aggrégation » et d'autres types de «versions modifiées » ?

Une « aggrégation » consiste en des programmes séparés distribués ensemble sur le même CD-ROM ou un autre média. La GPL vous permet de créer et distribuer une aggrégation, même si les licences des autres logiciels ne sont pas libres ou sont incompatibles avec la GPL. La seule condition est que vous ne pouvez pas publier une aggrégation sous une licence qui interdise aux utilisateurs d'exercer les droits que chaque licence individuelle des programmes leur autorise. Où est la limite entre deux programmes séparés et un programme en deux parties ? Il s'agit d'un problème juridique, qui sera tranché en dernier recours par un juge. Nous pensons qu'un critère adapté tient compte à la fois des modes de communication (exec, pipes, rpc, appel de fonctions au sein d'un espace de mémoire commun, etc.) et de la sémantique de cette communication (quels genres d'informations sont échangés). Si les modules sont inclus dans un même fichier exécutable, ils sont indéniablement combinés dans un seul programme. Si les modules sontconçus pour être exécutés par édition de liens dans un même espace mémoire partagé, cela signifie presque à coup sûr une combinaison en un seul programme. En revanche, les pipes, sockets et autres arguments de ligne de commande sont des mécanismes de communication utilisés normalement entre deux programmes séparés. Aussi, tant que ceux-ci servent à communiquer, les modules sont normalement des programmes séparés. Mais si la sémantique des échanges est assez 'intime', avec échange de structures de données internes complexes, cela pourrait également constituer une base suffisante pour considérer les deux éléments combinés comme un seul et même programme.

Traduction GPL en Français

AGPL et services en ligne.

Compatibilité des licences

Contributor License Agreement

Seeks_CLA.txt

Les acteurs de la compliance

Conseil sur les licenses

Le libre dans les organismes publiques

Les devoirs des distributeurs de logiciel.

Assister un auteur

Interactions avec les juristes.

Rassembler des preuves

Les fournisseurs en violation.

Vérification de sources.

Violation de licence.

Procès

Le développeur employé et les licences.

Le développeur indépendant et les licences.

Contrats de travail

En application de l'article L-113-9 du CPI, l'EMPLOYÉE reste seule titulaire des droits patrimoniaux sur les LOGICIELS et leur DOCUMENTATION créés dans l'exercice de ses fonctions ou d'après les instructions de son employeur, à la condition qu'elle satisfasse à toutes les exigences exposées ci-après.

http://fsffrance.org/contrats/travail.fr.html

Compilation et autres traitements

As a special exception, you may create a larger work that contains part or all of the Bison parser skeleton and distribute that work under terms of your choice, so long as that work isn't itself a parser generator using the skeleton or a modified version thereof as a parser skeleton. Alternatively, if you modify or redistribute the parser skeleton itself, you may (at your option) remove this special exception, which will cause the skeleton and the resulting Bison output files to be licensed under the GNU General Public License without this special exception.

La tivoisation.

Les marques.

DMCA / EUCD DeCSS.

debian-mentors-chat-about-decss-in-debian.txt

La cryptologie

Slides sous GPLv3+

Copyright (C) 2011 Loic Dachary <loic@dachary.org>

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.