X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=developers-reference.sgml;h=646f4f56e5eaf8aaf4bfca8549fc48865ff6865c;hb=373aca6ace7c0f2e56a7ff4017c6a6697812a405;hp=726143703a78eaae4fc3a881759bbf136756511d;hpb=9a70ca7ec95c1cb9ce91b2c36d1a831a39e08353;p=developers-reference.git

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 7261437..646f4f5 100644
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -5,7 +5,7 @@
   <!-- common, language independant entities -->
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.51 $">
+  <!entity cvs-rev "$Revision: 1.53 $">
 
   <!-- if you are translating this document, please notate the RCS
        revision of the developers reference here -->
@@ -1085,7 +1085,7 @@ After uploading your package, you can check how the archive maintenance
 software will process it by running <prgn>dinstall</prgn> on your changes
 file: <example>dinstall -n foo.changes</example>
 
-	<sect1 id="upload-non-us">Uploading to <tt>non-us</tt> (pandora)
+	<sect1 id="upload-non-us">Uploading to <tt>non-US</tt> (pandora)
 	  <p>
 As discussed above, export controlled software should not be uploaded
 to <tt>ftp-master</tt>.  Instead, use <prgn>scp</prgn> or non-anonymous
@@ -1100,7 +1100,29 @@ the program for details.
 You can check your upload the same way it's done on <tt>ftp-master</tt>,
 with:
 <example>dinstall -n foo.changes</example>
-      
+	  <p>
+Note that U.S. residents or citizens are subject to restrictions on
+export of cryptographic software. As of this writing, U.S. citizens are
+allowed to export some cryptographic software, subject to notification
+rules by the U.S. Department of Commerce.
+	  <p>
+Debian policy does not prevent upload to non-US by U.S. residents or
+citizens, but care should be taken in doing so. It is recommended that
+developers take all necessary steps to ensure that they are not
+breaking current US law by doing an upload to non-US, <em>including
+consulting a lawyer</em>.
+	  <p>
+For packages in non-US main or contrib, developers should at least
+follow the <url id="&url-u.s.-export;" name="procedure outlined by the
+US Government">.  Maintainers of non-US/non-free packages should
+further consult these <url id="&url-notification-of-export;"
+name="rules on notification of export"> of non-free software.
+	  <p>
+This section is for information only and does not constitute legal
+advice. Again, it is strongly recommended that U.S. citizens and
+residents consult a lawyer before doing uploads to non-US.
+
+
 	<sect1>Uploads via <tt>chiark</tt>
 	  <p>
 If you have a slow network connection to <tt>ftp-master</tt>, there are