InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
[04/2023] Reference ongoing work of the FINOS InnerSource Licensing Working group
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
@chamindra gave a presentation at the ISC Summit 2022 about the work of the FINOS InnerSource SIG, specifically the FINOS InnerSource Licensing Working group.
They want to create a license generator, that orgs can use to generate their own InnerSource licenses.
Please review key points of the talk related to InnerSource at:
https://www.youtube.com/watch?v=pDG_CqvTWrE&t=453s
This work is ongoing. From what I can tell it has not produced results yet that others can immediately use. However it might still be interesting for readers of our InnerSource License pattern to know that this work is ongoing. I am a bit torn whether to add this information to the pattern already or not.
By filing this issue I figured we keep at least some trace of this ongoing work that could enrich the InnerSource License pattern in the future.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked FINOS InnerSource Licensing Working group issue and the referenced presentation, then compare their current status with the InnerSource License pattern. Decide whether the pattern should mention this ongoing work; done means either a focused documentation update is proposed or the issue records why no update is appropriate.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100