search

ChristianMurphy / apereo.foundation

Community based redesign of Apereo website
https://apereo.foundation
Apache License 2.0
4 stars 1 forks source link

re-license website content to CC-BY-4.0 (maybe) #10

Closed apetro closed 6 years ago

apetro commented 6 years ago

I'm quite open to being convinced that Apache2 is fine.

And frankly I'm personally pretty exhausted about licensing and would be pretty willing to just give up.

But if we're looking to run with what was previously discussed and worked out about how non-code content should be licensed, I think where we got is that the website content should be CC-BY (while the custom website software to the extent that it exists probably should be Apache2.)

cf. https://github.com/apereo/apereo.github.io/pull/4

Mechanically maybe we come out the other end with a root LICENSE file that remains Apache2 and then a /docs/LICENSE file that is CC-BY, and more importantly marking in the generated website that content licensed under CC-BY.

Cf. Apereo website status quo licensing footer

apereo-is-cc-by-3

Note also that happily since status quo website is unambiguously defaulting to CC-BY-3 most of its content can be slurped in and redesigned here per that license without asking anyone permission about anything. So much to be said for open source licensing.

ChristianMurphy commented 6 years ago

Sure, I'm for having the content as creative commons. :+1: I'm still on the fence about the docs/ folder, more clicks to get to the content, but with #7 it wouldn't be too bad.

ChristianMurphy commented 6 years ago

resolved in https://github.com/ChristianMurphy/apereo.foundation/pull/28