Author: buildbot
Date: Sat Feb 7 18:24:48 2015
New Revision: 939368
Log:
Staging update by buildbot for nifi
Modified:
websites/staging/nifi/trunk/content/ (props changed)
websites/staging/nifi/trunk/content/development/licensing-guide.html
Propchange: websites/staging/nifi/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Feb 7 18:24:48 2015
@@ -1 +1 @@
-1658091
+1658092
Modified: websites/staging/nifi/trunk/content/development/licensing-guide.html
==============================================================================
--- websites/staging/nifi/trunk/content/development/licensing-guide.html
(original)
+++ websites/staging/nifi/trunk/content/development/licensing-guide.html Sat
Feb 7 18:24:48 2015
@@ -186,7 +186,7 @@ found and provide a link to the project
<p>Specific guidance for handling other ASF projects is found <a
href="http://www.apache.org/dev/licensing-howto.html#bundle-asf-product";>here</a>.
"It is not necessary to duplicate the line "This product includes software
developed at the Apache Software
Foundation...", though the ASF copyright line and any other portions of NOTICE
must be considered for propagation."</p>
-<p>Specific guidance for handling LICENSE/NOTICE information for category-B
licensed works is <a
href="http://apache.org/legal/resolved.html#category-b";>her</a>.
+<p>Specific guidance for handling LICENSE/NOTICE information for category-B
licensed works is <a
href="http://apache.org/legal/resolved.html#category-b";>here</a>.
Place an entry in the notice indicating the work is included in binary
distribution. Provide a link to the
homepage of the work. Indicate it's license. Group like licensed items
together. "By attaching a prominent label to
the distribution and requiring an explicit action by the user to get the
reciprocally-licensed source, users are less
