<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Well, as I said earlier, I believe that the spirit of the Apache
    license is that you ALWAYS say yes, to any request to reuse, remix,
    repurpose, re-whatever your documentation content.<br>
    <br>
    If we believe that the Apache license expresses our wishes about our
    project, and if we understand what the license says, then we have no
    reason ever to say no when someone asks to quote from, paraphrase,
    or copy our docs wholesale.<br>
    <br>
    Or our source code, for that matter.<br>
    <br>
    <div class="moz-cite-prefix">On 01/14/2014 02:54 PM, Nermina Miller
      wrote:<br>
    </div>
    <blockquote
      cite="mid:D549B579-7A45-47B1-BBDD-20176851BB90@gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      Hence my questions :) How DO you deal with such requests?
      <div><br>
        <div>
          <div>On Jan 14, 2014, at 2:47 PM, Rich Bowen <<a
              moz-do-not-send="true" href="mailto:rbowen@redhat.com">rbowen@redhat.com</a>>
            wrote:</div>
          <br class="Apple-interchange-newline">
          <blockquote type="cite">
            <meta content="text/html; charset=ISO-8859-1"
              http-equiv="Content-Type">
            <div bgcolor="#FFFFFF" text="#000000"> <br>
              <div class="moz-cite-prefix">On 01/14/2014 02:41 PM,
                Nermina Miller wrote:<br>
              </div>
              <blockquote
                cite="mid:32A26013-39BA-41DB-8F34-6ACFF2CC3724@mirantis.com"
                type="cite">
                <meta http-equiv="Content-Type" content="text/html;
                  charset=ISO-8859-1">
                When I worked on manuals for an international
                association, I used to check the copyright policy of
                each company whose material we used for support. They
                varied. In some cases, you could paraphrase, in some
                only quote. They also had specific notes you were
                required to use whether in text, footnote, or reference
                list. So, there are some specifics that are important to
                state for those who want to write tutorials, blog posts,
                and larger bodies of work.</blockquote>
              <br>
              Absolutely, but I presume that none of those products were
              Open Source. That changes the game.<br>
              <br>
              We're not a software company. We're an Open Source
              project.<br>
              <br>
              <pre class="moz-signature" cols="72">-- 
Rich Bowen - <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:rbowen@redhat.com">rbowen@redhat.com</a>
OpenStack Community Liaison
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://openstack.redhat.com/">http://openstack.redhat.com/</a></pre>
            </div>
            _______________________________________________<br>
            Openstack-docs mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br>
            <a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Rich Bowen - <a class="moz-txt-link-abbreviated" href="mailto:rbowen@redhat.com">rbowen@redhat.com</a>
OpenStack Community Liaison
<a class="moz-txt-link-freetext" href="http://openstack.redhat.com/">http://openstack.redhat.com/</a></pre>
  </body>
</html>