[Evergreen-documentation] Update on licensing question

[Susan Morrison]

I'm sorry I missed the meeting! We were at the Georgia Libraries Conference
last week. I also vote for #1. I feel like #2 would be an impossible task,
and managing mixed licenses seems...complicated.

On Thu, Oct 10, 2024 at 2:00 PM Andrea Buntz Neiman via
Evergreen-documentation <evergreen-documentation at list.evergreen-ils.org>
wrote:

> Hi DIG,
>
> At the last meeting I brought up
> https://bugs.launchpad.net/evergreen/+bug/1831672 and the consensus was
> that we wanted a 4.0 license on our docs.
>
> Galen and I looked at this carefully while prepping for TEP Board next
> week, and it turns out it's complicated.
>
> To summarize the current licensing statements / icons in docs:
>
>    - New Docs (3.6 and later)
>       - No per-page licensing statement, icon, or links
>       - Licensing page verbiage, links, and CC icon all refer to 3.0:
>       https://docs.evergreen-ils.org/docs/latest/shared/licensing.html
>    - Old Docs (3.5 and earlier)
>    - No per-page licensing statement, however there is a CC icon that
>       links to a 4.0 license
>       - Licensing page verbiage & links refer to 3.0:
>       https://olddocs.evergreen-ils.org/docs/3.5/licensing.html
>
> Galen and I concluded that the per-page icon in the old docs is likely in
> error, and furthermore, to upgrade all docs from 3.0 to 4.0 will be quite
> the undertaking.
>
>
> https://opensource.stackexchange.com/questions/7430/can-i-upgrade-the-version-of-cc-by-sa-from-3-0-to-4-0-in-my-modification
>
> https://wiki.creativecommons.org/wiki/4.0_upgrade_guidelines
>
> In particular, "If the contributor, then can license new contributions to
> an adaptation under 4.0 but *original contributions remain under prior
> version unless express permission to upgrade is obtained*." (emphasis
> added)
>
> So that means we have the following options:
>
> 1) Continue to license under 3.0, and correct the apparent error in the
> old docs footer
> 2) Port all old content to 4.0 which means getting permission to upgrade
> from every copyright holder, which means every.single.person who
> contributed to the docs.
> 3) Request TEP Board to allow us to license all new content under 4.0,
> which will mean managing multiple licenses and might be an even bigger pain
> to untangle given the myraid ways docs are updated.
>
> Anyway, I am in favor of option #1 but I'm interested in what the rest of
> DIG things.
>
> ABN
>
> --
> Andrea Buntz Neiman, MLS
> Project Manager for Software Development | Product Specialist
> Equinox Open Library Initiative
> abneiman at equinoxOLI.org <abneiman at equinoxoli.org>
> 1-877-OPEN-ILS (673-6457)
> Direct: 770-709-5583
> *https://www.equinoxOLI.org/ <https://www.equinoxOLI.org/>*
> _______________________________________________
> Evergreen-documentation mailing list
> Evergreen-documentation at list.evergreen-ils.org
>
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-documentation
>


-- 

[image: logo with link to Georgia Public Library Service website]
<https://georgialibraries.org/>

Susan Morrison, PINES Operations Analyst

------------------------------

​Georgia Public Library Service

​2872 Woodcock Blvd, Suite 250 | ​Atlanta, GA 30341

(404) 235-7142 | smorrison at georgialibraries.org

https://help.georgialibraries.org | help at georgialibraries.org

[image: logo with link to Georgia Public Library Service Facebook page]
<https://www.facebook.com/georgialibraries>[image: logo with link to
Georgia Public Library Service Instagram page]
<https://www.instagram.com/georgialibraries/>[image: logo with link to
Georgia Public Library Service LinkedIn page]
<https://www.linkedin.com/company/georgia-public-library-service/>[image:
logo with link to Georgia Public Library Service Threads page]
<https://www.threads.net/@georgialibraries>

Join our email list <http://georgialibraries.org/subscription> for stories
of Georgia libraries making an impact in our communities.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-documentation/attachments/20241011/d118306a/attachment-0001.htm>