Mention Licenses in Jupyter Book deployment

[soerenthomsen]

As pointed out by @paulineobps so far the licence is not clear when just looking at the Jupyter Book and it suggests that the The Jupyter Book community owns the copy right. By The Jupyter Book community © Copyright 2021.

We have to check with the jupyter book whether they own any copyright over the content of the deployment. If that is the case we have a problem.

This issue is relevant for each SOP.

[soerenthomsen]

@jbusecke do you have an idea what the "By The Jupyter Book community © Copyright 2021." below our book deployment exactly implies? Would be good if we could clarify this before Christmas to ensure we can us this approach in the long term.

[jbusecke]

Interesting point. [Here] is some internal discussion about this topic, but I agree this is not entirely clear. We should probably track down the actual type of license that the jupyter project uses and then see if/how we can explicitly modify it for this project? It is also not at all clear if the copyright applies to the framework of jupyter book only or the content aswell.

[soerenthomsen]

Thanks @jbusecke for supporting this. There is nothing linked in your comment.

[isgiddy]

Just had a look into this a little.

Jupyter Book is licensed under a BSD 3-Clause. See the link here.

The license footer can be edited in the default_config.yml file. (see link).

I had a look at some other jupyter books for reference. See example screenshot below:

[soerenthomsen]

Thank you @isgiddy for checking this! Indeed this is very helpful. Also the example is very helpful.

@jbusecke what do you think?

[jbusecke]

Sorry this is the link I meant to send: https://github.com/executablebooks/jupyter-book/issues/661. I am honestly not an expert on these specific things, and it seems like @isgiddy has now more expertise on this topic 😁

[paulineobps]

Thanks Isabelle

There are choices for licenses https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.

Creative Commons are the most well-known licenses and the Creative Commons-Attribution-ShareAlike (CC-BY-SA 4.0 ) is the one to use if you are going to permit access and use by Commercial interests.

BSD 3-Clause "New" or "Revised" License - looks good but is for executable books? Particularly like the 'prohibits others from using the name of the project or its contributors to promote derived products without written consent' What will go into OBPS is a pdf with a CC License with the link to the GitHUB code repository in the metadata field? BSD 3-Clause "New" or "Revised" License would cover the GitHub access.

I have not been in all the discussions so not totally sure of all the formats and componenets that will be produced for the SOP.

Pauline Pauline SIMPSON Ocean Best Practices System Project Manager https://www.oceanbestpractices.org/

UNESCO /IOC Project Office for IODE, Wandelaarkaai 7/61, 8400 Oostende, Belgium Email: @.**@.>; Alternate email: @.**@.>; Skype: Pauline Simpson ORCID: 0000-0003-2551-5740

http://www.iode.org

---

From: Isabelle Sindiswa Giddy @.> Sent: 01 December 2021 09:09 To: OceanGlidersCommunity/Oxygen_SOP @.> Cc: Simpson, Pauline @.>; Assign @.> Subject: Re: [OceanGlidersCommunity/Oxygen_SOP] Mention Licenses in Jupyter Book deployment (Issue #174)

CAUTION: This email is external from UNESCO. Please be vigilant on its sender and content. ATTENTION : Cet e-mail est externe à l'UNESCO. Soyez vigilant sur son expéditeur et contenu.

Just had a look into this a little.

Jupyter Book is licensed under a BSD 3-Clause. See the link herehttps://github.com/executablebooks/jupyter-book/blob/master/LICENSE.

The license footer can be edited in the default_config.yml file. (see linkhttps://github.com/executablebooks/jupyter-book/blob/master/jupyter_book/default_config.yml). Here the author and copyright can be edited.

I had a look at some other jupyter books for reference. See screenshot example below: [image]https://user-images.githubusercontent.com/30691939/144248982-2239bc94-cc91-4373-9a76-e91658e1c9f2.png

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHubhttps://github.com/OceanGlidersCommunity/Oxygen_SOP/issues/174#issuecomment-983677994, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFZQUQ33LYAOL746VNHJYO3UOYUCXANCNFSM5I4CJ6EA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[soerenthomsen]

From Pauline just post it here to ensure everyone reads it:

"Dear Soeren

We discussed the SOP at our OBPS SG last week. It will be a first, but the OBPS software can ingest Jupyter Notebook files. In the metadata we will link to the GitHub repo.

I think from the previous emails the licenses are now agreed?

Pauline Pauline SIMPSON Ocean Best Practices System Project Manager https://www.oceanbestpractices.org/"

[soerenthomsen]

Great to hear @paulineobps that you discussed this SOP and our process at the OBPS SG and even nicer to hear that the OBPS software can ingest Jupyter Notebook files. Indeed linking the GitHub repo is key so that people always find the up to date version. This might also help to get more and new users who engage with the SOP after downloading it.

Best wishes Soeren

PS: @tomhull please keep not of this conversion.

[soerenthomsen]

@isgiddy could you provide the link to the repo of the jupyter book example you screenshoted above?

[soerenthomsen]

This is solved via PR #187 and can be closed. Thanks @isgiddy for supporting this and implementing it directly into the Salinity SOP!