Your message dated Mon, 30 Jun 2008 12:02:49 +0100
with message-id <[EMAIL PROTECTED]>
and subject line sounds, how the Factory
has caused the Debian Bug report #92810,
regarding doc-rfc: Please try to clarify license issues with ISOC
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
92810: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92810
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: doc-rfc
Version: 2000.08-1
Severity: serious
The license on this package is pretty clearly non-free. The doc-rfc
package is a great resource, but its license makes it unsuitable for main.
The older RFC's appear to me to be DFSG-free, since the most onerous
restrictions are described as a "courtesy":
3. Favor or indulgence, as distinguished from right; as, a
title given one by courtesy.
The newer ones, however, are not:
However, this document itself may not be modified in any way, such as by
removing the copyright notice or references to the Internet Society or
other Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be followed,
or as required to translate it into languages other than English.
The phrase "in any way," fails DFSG 3, and "for the purposes..." and the
subsequent language fails DFSG 6.
There are no other problems with the "new" license that I can see.
Perhaps only the DFSG-free RFC's could be split into a doc-rfc-nonfree
package?
Copyright:
(this is rfc-copyright-story in the rfc-editor subdirectory.)
"Hi.
The Request For Comments (RFC) documents are intended to have wide
distribution.
1. Copying and distributing the whole RFC without any changes:
1a. The copying and free redistribution are generally encouraged.
1b. The inclusion of RFCs in other documents and collections that are
distributed for a fee is also encouraged, though in this case it is a
courtesy (i) to ask the RFC author and (ii) provide the RFC author
with a copy of the final document or collection. Anyone can takes
some RFCs, put them in a book, copyright the book, and sell it. This
in no way inhibits anyone else from doing the same thing, or inhibits
any other distribution of the RFCs.
2. Copying and distributing the whole RFC with changes in format,
font, etcetera:
2a. The same as case 1 with the addition that a note should be made
of the reformatting.
3. Copying and distributing portions of an RFC:
3a. As with any material excerpted from another source, proper credit
and citations must be provided.
4. Translating RFCs into other languages:
4a. Since wide distribution of RFCs is very desirable, translation
into other languages is also desirable. The same requirements and
courtesies should be followed in distributing RFCs in translation as
would be followed when distributing RFCs in the original language.
--jon."
Newer RFCs are under the following copyright:
"Full Copyright Statement
Copyright (C) The Internet Society (1998). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux apocalypse 2.4.3 #1 Mon Apr 2 04:43:41 UTC 2001 i586
--- End Message ---
--- Begin Message ---
be noted that investment advisory service are providing a variety of decision
on the you were informed the documentation to other bodies.
http://heatwritten.com
--- End Message ---
