svn commit: r45092 - head/en_US.ISO8859-1/articles/committers-guide

[Gabor Pali]

Author: pgj
Date: Sat Jun 21 09:43:30 2014
New Revision: 45092
URL: http://svnweb.freebsd.org/changeset/doc/45092

Log:
  - Add a section on keeping track of licenses granted to the Project
  
  Submitted by:	core

Modified:
  head/en_US.ISO8859-1/articles/committers-guide/article.xml

Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/committers-guide/article.xml	Sat Jun 21 09:06:02 2014	(r45091)
+++ head/en_US.ISO8859-1/articles/committers-guide/article.xml	Sat Jun 21 09:43:30 2014	(r45092)
@@ -2684,6 +2684,69 @@ Relnotes:           yes</programlisting>
       brought to the attention of the core team.</para>
   </sect1>
 
+  <sect1 xml:id="tracking.license.grants">
+    <title>Keeping Track of Licenses Granted to the &os; Project</title>
+
+    <para>Various software or data exist in the repositories where
+      the &os; project has been granted a special licence to be able
+      to use them.  A case in point are the Terminus fonts for use
+      with &man.vt.4;.  Here the author Dimitar Zhekov has allowed us
+      to use the "Terminus BSD Console" font under a 2-clause BSD
+      license rather than the regular Open Font License he normally
+      uses.</para>
+
+    <para>It is clearly sensible to keep a record of any such
+      license grants.  To that end, the &a.core; has decided to keep
+      an archive of them.  Whenever the &os; project is granted a
+      special license we require the &a.core; to be notified.  Any
+      developers involved in arranging such a license grant, please send
+      details to the &a.core; including:</para>
+
+    <itemizedlist>
+      <listitem>
+	<para>Contact details for people or organizations granting the
+	  special license.</para>
+      </listitem>
+
+      <listitem>
+	<para>What files, directories etc. in the repositories are
+	  covered by the license grant including the revision numbers
+	  where any specially licensed material was committed.</para>
+      </listitem>
+
+      <listitem>
+	<para>The date the license comes into effect from.  Unless
+	  otherwise agreed, this will be the date the license was issued
+	  by the authors of the software in question.</para>
+      </listitem>
+
+      <listitem>
+	<para>The license text.</para>
+      </listitem>
+
+      <listitem>
+	<para>A note of any restrictions, limtations or exceptions that
+	  apply specifically to &os;'s usage of the licensed
+	  material.</para>
+      </listitem>
+
+      <listitem>
+	<para>Any other relevant information.</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>Once the &a.core; is satisfied that all the necessary details
+      have been gathered and are correct, the secretary will send a
+      PGP-signed acknowledgement of receipt including the license
+      details.  This receipt will be persistently archived and serve
+      as our permanent record of the license grant.</para>
+
+    <para>The license archive should contain only details of license
+      grants; this is not the place for any discussions around
+      licensing or other subjects.  Access to data within the license
+      archive will be available on request to the &a.core;.</para>
+  </sect1>
+
   <sect1 xml:id="developer.relations">
     <title>Developer Relations</title>