gruntwork-io / gruntwork-io/boilerplate
Consider licensing issues when opening Boilerplate up to more customers
Open
- Dominant language
- Go
- Stars
- 350
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
From https://github.com/gruntwork-io/boilerplate/pull/111
> [Older versions licensed as MIT] might become an issue if we ever open boilerplate up to other customers, as legally all those commits are licensed as MIT.
> It would be a bit of a pain to retroactively update the LICENSE file, especially with all the release tags. I think the best way to handle this would be to fork boilerplate and start the history a new when we are ready to start sharing it with more people.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.