I think a specific feature for adding a license to a notebook would be really beneficial! For things like the unofficial Atom package for rendering local observable notebooks, where it’s pretty easy to import any public Observable notebook, people might be importing and using notebooks that they don…

Closing the loop here: we shipped support for licensing notebooks today. Feedback welcome. [image] Notebook Licenses Announcements Hi folks, We’ve just launched built-in support for software and content licenses on your notebooks! We hope this will help notebook authors …

Some talking points: Adoption is key, so setting a license should be a no-brainer UX-wise. Having something like LICENSE = License`MIT` is (imo) rather obscure. Users may not be familiar with the various licenses and might not care. They should be able to select a license, ideally with a short (no…

GitHub’s https://choosealicense.com has some great data for helping users choose between licenses.

Related: Copyright and software licenses License for code submitting on github Are Observable notebooks GPL compatible?

[image] mootari: We should research wether a SPDX identifier without the actual license text has any relevance. Creative Commons suggests the following: Different types of content will have different limitations, but your marker should contain: The full URL (link) to the license. Exampl…

Feature request: Standardize licensing notebooks

Feedback

mbostock July 16, 2020, 8:11pm 6

Closing the loop here: we shipped support for licensing notebooks today. Feedback welcome.

Topic		Replies	Views
Notebook Licenses Announcements	15	1394	January 14, 2022
Copyright and software licenses Feedback	23	4327	November 2, 2020
Licensing Help	2	51	November 17, 2024
Are Observable notebooks GPL compatible?	1	766	December 6, 2018
Export final code? Help	39	22691	December 18, 2018

Feature request: Standardize licensing notebooks

Related topics