You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for reporting this @Bashamega! I'm just checking with the team. I'm thinking we probably want Apache 2.0 like our app repository, but just confirming.
We can update it to whatever license by running, npx license, e.g. npx license Apache-2.0.
Obligatory "I'm not a lawyer" but I'm not sure Apache 2.0 or another permissive license (like MIT) makes sense since the landing page contains alot of our own "works" attributed in the blog to individual authors.
We shouldn't give rights for others to fork and modify those works.
One of the creative commons licenses might make sense. Or a copy left GPL license would require others keep their source open if they use our landing page for some reason.
Or, if we don't see it as a big deal, Apache 2.0 is probably fine: it is a strange case since it's not really something others would take and use like a typical piece of open source software.
Describe the bug
Hello:)
I think the project is missing a license which is an important file for an open source repository
Steps to reproduce
You can't find a LICENSE file in the root
The text was updated successfully, but these errors were encountered: