Add LICENSE to each colab.

[reddragon]

As per title.

[reddragon]

We need to figure out which license to use though. Is Apache the right one?

[NareshPS]

Let's figure it out before putting a license. It's not a good idea to change it later.

…

On Tue, Jun 14, 2022, 09:40 Gaurav Menghani ***@***.***> wrote: We need to figure out which license to use though. Is Apache the right one? — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADVLBGJU6ANYSGHVRSZNKTVO7WI5ANCNFSM5YWDQXZA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[NareshPS]

We need separate licenses for book pdf and code labs. Book PDFs should have a limited license in terms of reproducibility. We want to discourage people from publishing these chapters. Code labs, however, can have a free to use, modify license with attribution.

[NareshPS]

For the code labs we can use MIT License. It seems to fit our use case. Apache license requires the users to state the changes made to the code. I am kinda on the fence. It may be a good idea for some cases while too cumbersome for other cases. Take a look at the common licenses here if you haven't already: https://choosealicense.com/licenses/

I am still looking for a license to the PDFs. My current disposition is to avoid having a license for it. I don't know a use case for the readers to reproduce the book text. Readers should attribute the original material based on their usage.

[reddragon]

I agree, I was mostly thinking of license for code only. For book I guess it might depend on the potential publisher.

[NareshPS]

Let's leave it open for a couple of days just in case we have other ideas and add the license later this week.