FINOS InnerSource Licenses
- Dominant language
- JavaScript
- Stars
- 37
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
## Finos Inner Source License
### Description of Problem:
The application of inner source within a Financial enterprise requires more clarity in terms of permissible use and clear definitions of boundary particularly with the involvement of 3rd Party vendors and partners. Inner Source can sometimes be mistaken as Open Source causing issues. It would be good to have some clear do and don't when you get your hands on inner source code. The license should also encourage sharing code back in certain scenarios.
If we have a common and popular set of inner source licenses:
1. It would be less of a cost for an organisation to adopt (vs define an organisational license/contract/etc)
2. Popularity similar to Open Source will make developers more comfortable contributing to inner source
3. A shared inner source license would be easier to defend in court
4. We are applying the principle of Open Source to how we define the inner source license, which seems like the right way to do it
### Description of Problem
1. Presentation: [InnerSource SIG Licenses Working Group 7th November 2022.pdf](https://github.com/finos/InnerSource/files/9954255/Inner.Source.SIG_.Licenses.WG.-.7-Nov-22.pdf)
5. Video: https://www.youtube.com/watch?v=bQz12Rwzzbk (15min video at recent Inner Source Commons Summit)
Contributor guide
Assessment
This issue has not been assessed yet.