-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/08/2012 08:20 PM, Jessica Tomechak wrote: > On Wed, Aug 8, 2012 at 2:50 PM, Jessica Tomechak > <jessica.tomec...@gmail.com <mailto:jessica.tomec...@gmail.com>> > wrote: > > Hello all, We had earlier proposed using the cc-by-sa license for > documentation, for a variety of good reasons, and I believed this > was approved by our mentors and/or legal. Recently, Joe B. did > some work in the doc files and has inserted the Apache 2.0 license. > It also looks like we have changed it in the publican-cloudstack > brand files (see Legal_Notice.xml). > > Is there any reason why we can not use cc-by-sa legally? It will > allow us to do good stuff like pull in content from outside > contributors, blogs, Wikipedia, any cc-licensed content we can > find. If we need to take the docs into their own non-Apache repo to > do this, it's worth considering. > > Jessica T. CloudStack Tech Pubs
Having been down this road with other projects I can tell you that Apache, similar to GPL and other software licenses, is not a good license for documentation. The license was mainly developed to protect source code and I see several holes in it when used on final-form, published documents. Of particular note is that downstream, derivative works must use this license further complicating the process. Not being an attorney I'm not going to specifically call out the holes in the license but the end result would be similar to not licensing the work at all for successful use in the FLOSS environment. The defacto standard FLOSS license for documentation is the Creative Commons CC-BY-SA license[0] which has been specifically designed for documentation, both in source and final-form documents. Using this license will allow CloudStack to reuse other upstream works and easily allow reuse of CloudStack works. If the Apache license is required I'd ask about whether or not a CC-BY-SA can also be applied to the documentation for dual-licensing. [0] https://creativecommons.org/licenses/by-sa/3.0/ - -Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQIwh7AAoJEIB2q94CS7PRykMP/A5BOkADsA/x5TRic+lv28mm LaMLpkz6AI/b1qeHq29M9XqzGx09ZKjNmP1Oy4EhFKJSU97wQucBtVoqBvcaVHPF Mp6NG+HnRCIOWeT4NVfsS+Z6NWWasTzF5U/Ai6kGpZwBk8BNy91CXVklX/j3TsSG kOl1G2v9I529xH9fdNbujWTQswezQRl3KgjGk170s1sC9EaAiN/e+j8LzeCEanGf r7Xx+39s58+0bqz42983IuUrgyW10WW5gzGvFkbAFQJ3gHp4AVm/dFn2EjrLpp6c 6XCbfCsY1ll8Klktqein7+KXRpXCJD8fOtD9ZtA8d3GkEf4ALxlzCquXPaMU78W2 XB3jlCecz2fommLD5dttSU74UF9Nc0b3Zcwvph5aTYeY0vUlY8CZYzp3z4oiX4My pbXGAxNUwIC/vqjnF0olCyo/8dn0xZuWwXIJIFWvXOKVHpnJWaO1gkF2as5EEkCj XY4eses96VM+mgZFbrKMbhbNPtWZ3vJQdBPKR8z5oxm/sRbO9Cre9t1F5wEU5/SZ 4WF0/rgGLada6CYzDSYHB78OHrtw9J8hvFmuiV5qFNcfwrYdiMvFgAa4uTdjWb2/ 4RyGvy14Agq6gyPChz9nQCBKXzLCjZ2trvigfqbZtwkA3e9uFjK99+fB4nFf+MhC YswSWKEA7Ht1U4ST9kLB =gA5I -----END PGP SIGNATURE-----
