Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add copyright notice to license #37

Closed
ghost opened this issue Jul 5, 2020 · 3 comments · Fixed by #38
Closed

Add copyright notice to license #37

ghost opened this issue Jul 5, 2020 · 3 comments · Fixed by #38

Comments

@ghost
Copy link

ghost commented Jul 5, 2020

This is a great starter but as it stands the work added to the gatsby starter is unclear from a licensing perspective given no copyright notice was added by the author. Please add a copyright notice. For more information see: https://writing.kemitchell.com/2016/09/21/MIT-License-Line-by-Line.html. If you're unsure how to add a notice let me know and I'll help. Note Gatsby recently relicensed all their starters under 0BSD.

@parmsang
Copy link
Owner

parmsang commented Jul 6, 2020

Hi @balibebas - Thanks for notifying me. If you can help that is much appreciated.

@ghost
Copy link
Author

ghost commented Jul 6, 2020

Sure bud. Basically you have two options. Rebase on a starter following the transition to 0BSD and you can do whatever you want with the license. Option 2 and less work is to add a copyright notice (mentioned with example in Mitchell's post) with your authorship info (you can use a pseudonym if you like but you need to add something otherwise licensure is unclear).

If you decide to go for door 1 you can use whatever license you like and will not have to carry the MIT license around. The choice of liceses is up to you though for the sake of your users I'd stick with MIT given it's what they were expeecting when they started using this product.

For a specific examples of how to update the license please see: AlexanderProd/gatsby-shopify-starter@1e2cc6e

@parmsang parmsang linked a pull request Jul 13, 2020 that will close this issue
@parmsang parmsang mentioned this issue Jul 13, 2020
@parmsang
Copy link
Owner

@balibebas Thank you for taking the time to make me aware of this update and advising me of the necessary changes. Very much appreciate it. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant