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
{{ message }}
This repository has been archived by the owner on Apr 8, 2021. It is now read-only.
. This feels a little dangerous, I doubt most of our internal projects are actually Apache licensed projects, and it feels a little too easy to forget to remove this license.
I would have thought that we would probably default to an all rights reserved license, allowing any project maintainer to easily amend to a more permissive license. (IANAL), but I would imagine that once a piece of source code is issued with a permissive license, then that license would be applied forever (it's not possible to remove the permissions granted by that license).
I'm all for open software, but it should be a conscious choice by the owner/maintainer of the software in question.
The text was updated successfully, but these errors were encountered:
These build.sbt settings apply (or rather should!) to sbt-cake only - hence why it has a permissive license. For BAMTech Media uses of sbt-cake, we fully expect that teams will define there own licenses (probably not relevant now for BAMTech Media projects?).
These build.sbt settings apply (or rather should!) to sbt-cake only - hence why it has a permissive license. For BAMTech Media uses of sbt-cake, we fully expect that teams will define there own licenses (probably not relevant now for BAMTech Media projects?).
Looking at line
sbt-cake/build.sbt
Line 31 in e686d5d
I would have thought that we would probably default to an all rights reserved license, allowing any project maintainer to easily amend to a more permissive license. (IANAL), but I would imagine that once a piece of source code is issued with a permissive license, then that license would be applied forever (it's not possible to remove the permissions granted by that license).
I'm all for open software, but it should be a conscious choice by the owner/maintainer of the software in question.
The text was updated successfully, but these errors were encountered: