Mercurial > emacs
view etc/LPF @ 83309:6aee1e9b0bd7
Merged from miles@gnu.org--gnu-2005 (patch 74-79, 332-349)
Patches applied:
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-332
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-333
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-334
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-335
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-336
Merge from gnus--rel--5.10
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-337
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-338
etc/emacs-buffer.gdb: Remove RCS keywords
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-339
Merge from gnus--rel--5.10
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-340
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-341
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-342
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-343
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-344
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-345
Merge from gnus--rel--5.10
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-346
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-347
Update from CVS
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-348
Merge from gnus--rel--5.10
* miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-349
Update from CVS
* miles@gnu.org--gnu-2005/gnus--rel--5.10--patch-74
Merge from emacs--cvs-trunk--0
* miles@gnu.org--gnu-2005/gnus--rel--5.10--patch-75
Update from CVS
* miles@gnu.org--gnu-2005/gnus--rel--5.10--patch-76
Update from CVS
* miles@gnu.org--gnu-2005/gnus--rel--5.10--patch-77
Update from CVS
* miles@gnu.org--gnu-2005/gnus--rel--5.10--patch-78
Update from CVS
* miles@gnu.org--gnu-2005/gnus--rel--5.10--patch-79
Update from CVS
git-archimport-id: lorentey@elte.hu--2004/emacs--multi-tty--0--patch-349
author | Karoly Lorentey <lorentey@elte.hu> |
---|---|
date | Fri, 03 Jun 2005 05:49:26 +0000 |
parents | 885f63d7c285 |
children |
line wrap: on
line source
Protect Your Freedom to Write Programs Join the League for Programming Freedom (Version of February 3, 1994) Ten years ago, programmers were allowed to write programs using all the techniques they knew, and providing whatever features they felt were useful. This is no longer the case. New monopolies, known as software patents and interface copyrights, have taken away our freedom of expression and our ability to do a good job. "Look and feel" lawsuits attempt to monopolize well-known command languages; some have succeeded. Copyrights on command languages enforce gratuitous incompatibility, close opportunities for competition, and stifle incremental improvements. Software patents are even more dangerous; they make every design decision in the development of a program carry a risk of a lawsuit, with draconian pretrial seizure. It is difficult and expensive to find out whether the techniques you consider using are patented; it is impossible to find out whether they will be patented in the future. The League for Programming Freedom is a grass-roots organization of professors, students, businessmen, programmers and users dedicated to bringing back the freedom to write programs. The League is not opposed to the legal system that Congress expressly established for software--copyright on individual programs. Our aim is to reverse the recent changes that prevent programmers from doing their work. The League works to abolish the new monopolies by publishing articles, talking with public officials, denouncing egregious offenders, and filing amicus curiae briefs, most notably against Lotus in its suit against Borland. We testified twice at the recent Patent Office hearings on software patents. We welcome suggestions for other activities, as well as help in carrying them out. (Added 2003) The League for Programming Freedom is inactive nowadays, though its web site www.programming-freedom.org is still maintained. It would be very useful to find a person who could take the initiative to get the LPF operating again. It will be a substantial job, requiring persistence and working with a lawyer. If you want to do it, please write to rms@gnu.org.