Reprise du message précédent :

Passons sur les conneries que tu debite a longueur de post sur la GPL, mais je veux que tu m'explique ca!!
Parce que tu ne peux pas ecrire ca et pretendre t'y connaitre en prog, ni meme avoir installer une fois dans ta vie un prog sous nux

djoh a écrit a écrit :           t'as lu la GPL avant de dire des anneries pareils ? y-a vraiment un paquet de boulait dans les windowsiens     après on va dire que les linuxiens sont intégristes mais quand on voit des taches comme toi c'est dur de resister qu'est ce que tu as aujourd'hui ? tu t'ennuyais et tu t'es dit "tiens ! j'vais aller faire mon con sur OSA today"

 
C'est madmartigan, faut pas faire attention, a part débiter des conneries sur la gpl qu'il n'a jamais compris, il fait pas grand chose

 
nan mais je connais (et pis même si je connais pas c'est tellement gros qu'on peut pas tomber dedans), mais j'avais envi d'allumer une tête à claque là

OK, voici donc le texte "Officiel" de la GPL (ça c'est pour faire taire ceux qui ne la connaissent pas et prétendent que je ne l'ai pas lu).
 
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
 
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
 
Preamble
 
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
 
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
this service 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.
 
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
 
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. 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.
 
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
 
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
 
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
 
The precise terms and conditions for copying, distribution and
modification follow.
 
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
 
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The " Program " , below,
refers to any such program or work, and a " work based on the Program "  
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term " modification " .) Each licensee is addressed as " you " .
 
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
 
1. You may copy and distribute 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 and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
 
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
 
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
 
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
 
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
 
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
 
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
 
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
 
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
 
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
 
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
 
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
 
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
 
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
 
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
 
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
 
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
 
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
 
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
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
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
 
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
 
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
 
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
 
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
 
9. The Free Software Foundation may publish revised and/or new versions
of the 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.
 
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and " any
later version " , you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
 
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
 
NO WARRANTY
 
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM " AS IS " WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
 
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
 
END OF TERMS AND CONDITIONS
 
How to Apply These Terms to Your New Programs
 
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
 
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the " copyright " line and a pointer to where the full notice is found.
 
 
Copyright (C)  
 
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 2 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, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
 
 
Also add information on how to contact you by electronic and paper mail.
 
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
 
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
 
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
 
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a " copyright disclaimer " for the program, if
necessary. Here is a sample; alter the names:
 
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
 
, 1 April 1989
Ty Coon, President of Vice
 
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
 
 
Dans l'idée, rien à redire, il est louable que quelqu'un décide de mettre son code à la disposition de tous et souhaite que SON travail reste libre. Par contre, je ne vois pas en quoi il est en droit de dire "c'est moi qui ait eu l'idée le premier et je décide que personne ne pourra en prendre ne serait-ce qu'une infime partie à son compte".
Supposons que je dépiotte nu source et y découvre une petite routine de 3 lignes qui m'interesse. Ayant fait de l'info un métier, j'ai BESOIN que MON travail (disons les quelques milliers de lignes de CODE autres ques ces 3 là) soit commercialisable.
Je serais tout à fait disposé à diffuser mon Prog accompagé des remerciements (un peu comme l'auteur d'un essai cite ces sources à la fin de son oeuvre), du style "pour créer ce prog, j'ai utilisé une petite partie d'un prog que je trouve génial et dont voici les sources...". Dans l'esprit donc je ne trahis en rien la volonté du précédent auteur : SON travail reste libre et accessible à tous, le SOURCE qu'il a créé est diffusé.
Seulement voila, GPL m'oblige à rendre aussi PUBLIC mon travail, à le diffuser avec les sources. De plus, la licence GPL a été écrite non pas par des personnes de LOI mais par des techniciens. Son écriture est ambigüe et donc beaucoup trop risquée pour une entreprise.
Les lignes les plus critiquées de GPL sont celles-çi
You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
Le problème est "jusqu'où doit-on considérer la notion de partie de code" ? L'exemple le plus classique est que pratiquement tous les programmes "C" commencent par #include stdio.h, si cette ligne est considérée comme "partie du code", alors le seul fait qu'un pgm placé sous GPL l'utilise rendrait mplicitement tout autre pgm (même déja existant) automatiquement GPL !
Il en va de même d'un FOR ... NEXT ou de n'importe quelle partie de code triviale.
Ainsi donc, je ne suis pas vicéralement contre GPL, mais contre l'utilisation abusive qu'il en est fait actuellement (beucoup trop de libraries sont encore GPL et non pas LGPL). Je ne dis pas que GPL doit disparaitre mais être ré-écrite, parce qu'elle se révelle finalement un handicap dans l'évolution de LINUX. Elle a effectivement permis à LINUX de progresser rapidement dans le domaine "libre" (quoi qu'en fait rien n'indique que ce serait passé différement sans GPL, une bonne idée, protégée ou pas reste une bonne idée et le fait que quelques uns ait cherchés à se l'approprier n'aurait pas empêché les autres de le faire librement). Par contre, elle freine lourdement les ardeures d'entreprises qui souhaiteraient investir sur le marché LINUX.
 
Mad

<troll>
qq'un disqait que l'avenir etait au tout open source
 
 
 
enfin fo bien gagner son pain et vivre !
 
 
ta baguette de pain, gcc la fait pas !
 
il ne faut pas forcement denigrer les logiciels commerciaux....
</troll>

 
Il y a pas besoin de lire pour faire copier/coller.
 
Tu prends un logiciel permettant d'envoyer des mails sous GPL. Tu le modifie pour ton usage personnel (ajout de fonctions). Tu l'installes sur ton serveur web de manière à ce que toute personne accédant à ton serveur puisse l'utiliser depuis son navigateur, afin d'envoyer des mails par ce logiciel, en utilisant tes propres modifications.
 
Doit-tu publier les modifications que tu as réalisé sous license GPL ?
 
Relevage des copies ce soir.

 
parfois je me demande si troll n'est pas le mot passe partout pour dire "je délire" .  
 
"il ne faut pas forcement denigrer les logiciels commerciaux...."  
 
oui , surtout s'ils ne vivent que du logiciel et pas de qq clients parsemés pour du service.  A se demander si certaines boites ne laissent pas qq bugs dans leurs developpement spécifiques pour inciter au 'service'

raaahhh non , je m'étais jurer de pas rentrer dans ces débats de barbus qui partent en couille ...

 
Tu serais pas un peu con là ? Je suis sûr que beaucoup de programmes proprio commencent aussi par #include stdio.h, tu crois que Microsoft et Adobe pourraient poursuivre tous les auteurs de LL pour plagiat ? Tu te rends compte de la portée du truc devant un juge ? Tu ne crois pas qu'implicitement, il s'agit de parties de code significatives, c'est-à-dire contenant des routines fonctionnelles ?

 
ouai moi je dirais qu'il n'y a pas besoin de copier/coller pour lire
ça sert à rien de tout coller comme ça, ça alourdi la page ... enfin bref il est irrécupérable aussi celui là

Je confirme : ce qui suit est une grosse connerie de gas qui ont bien comrpis le fud de microsoft.
 
La gpl empèche une seul chose : la réapopriation du code, ce qui est possible avec la licences bsd.
 
quand tu fais un prog GPL, tu comptes sur le fait d'utiliser aussi toi-même des outils GPL. En fait, tu utilises 1000x plus de code GPL que tu n'en produit. Or si tout le monde fonctionne comme cela, le nombre de programme disponnible augmente en exponnentiel car le programme à un coup de duplication nul. La qualité est meilleur, notament parce que tout le monde zieut le code.  
 
Il suffit de voir les crises passion des revues de code des codeurs windows qui n'ont pas l'habitude d'être relu (et qui souvent code comme des porcs).
 
Si une boite réutilise du code sans qu'il y ait un retour. La boucle est cassé et cela casse le système. C'est le cas bsd. Tout le monde a le droit de piller sans aucun retour (resultat macOSX est basé sur bsd et MS a utiliser des outils bsd sans le dire (ftp/telnet de Windows NT))
 
Cela parait dure pour une boite qui fait du soft de faire du code GLP. Mais en fait, si, dans le cas contraire, elle doit réinventer la roue à chaque fois, car le code précédent ne lui appartient plus(b-to-b).  
 
Dans le b-to-c, par exemple dans le dommaine des jeux, l'idée est d'avoir le moteur libre libre (il suffit de voir la montagne de bug de certain jeux pour en comprendre l'interret...) mais des graphismes et sons qu'il ne le sont pas.  
 
Si 2 boites jouent le jeux, elles divisent le dev par 2 du moteur. Elle peuvent gagner qq developpeurs indépendants, qui même s'il ne sont pas payé par l'une des 2 boites si retrouve car il peuvent utiliser ensuite le programme comme bon leur semble. C'est la forme habituelle de rétribution du libre.
 
Dans le b-to-c genre office, on peut imaginer qu'une boite comme EDF en est marre de payer 10MM? par an en licence MS, paye Mandrake pour améliorer la comptibilité de OOo avec .doc. Enfin, n'importe quelle boite peut payer pour une fonction qui lui manque.  
 
Du fait de la réutilisation de compétence, de l'absence du secret qui finalement coute une énergie folle (en cas de problème, si on cherche de l'aide on ne peut jamais communiquer des infos sur le projets en cours), bref, les cout de dev d'un projet libre est bien moindre (si on va chercher les bonnes personnes, ça cela ne changera jamais, mais dans le libre cela se sait tout de suite).
 

GPL 2.0 ou 3.0 ?
 
non en 2.0
oui en 3.0
 

 
true. Tu as des pointeurs pour la V3 ? Je sais qu'elle est en cours de redaction, et j'aimerais voir à quoi elle ressemble.

 
Ben a une licence

http://www.gnu.org/press/2002-03-19-Affero.fr.html
 
Je n'ai trouvé que ça.

Le paragraphe interressant.
 
 

 
 
J'aime pas le terme "interact with users".

 
Pourquoi ? Au moins c'est claire et précis !

 
 
 
D'ou l interet de programmer en java

 
Parcequ'un webservice peut interragir avec un autre webservice. La notion de "user" au sens humain est reporté tellement loin qu'il ne manipule pas la license.
 
c'est ça qui m'embête dans cette phrase.

Y'a borland qui à sortit toute sa suite non? Y'a aussi Vmware, Maya et quelques jeux.