License choice?
#1040
Replies: 1 comment
-
|
Hey! I understand the concern and appreciate the question. The intention is to for Crush to remain source available and easily adoptable internally, with a clear path to MIT, while allowing us to sustainably build a commercial product around it. In other words, our goal is to keep development open and accessible while also making sure the project can be maintained long-term. We know that means it won’t fit every package repository, but we believe it's a fair trade-off. I'm going to close this discussion in effort of tidiness, but please do chime in if you have more questions. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, would you mind explaining the license choice of FSL-1.1-MIT instead of a bare MIT? Do you plan to build a commercial product around Crush? In case it makes sense... Otherwise i don't see the purpose meanwhile a lot of other coding agents exists under FLOSS licenses.
My actual concern is that Crush cannot be packaged into many software repositories (Homebrew, Debian, ...).
Beta Was this translation helpful? Give feedback.
All reactions