InnerSourceCommons / InnerSourceCommons/InnerSourceLearningPath
Exempt our meeting mechanics documents from the CC-BY-SA part and turn them into CC-BY or even CC-0
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 77
- Forks
- 47
- Avg merge
- 11h 11m
- Merged PRs (30d)
- 5
Description
The meeting mechanism we use in the learning path (shaped by @rrrutledge and many others) has proven to work really well over time and people.
It turns out to be even valuable for other non learning path groups (e.g. our foundation board meetings).
However, the material is still CC-BY-SA licensed and thus would need to return changes back to its origin. Which some people might not be comfortable with for their corporate changes.
While I fully stand behind our choice of CC-BY-SA for the learning path material, I would like to ask to change the license for the above mentioned material to CC-BY (only attribution) or even CC-0 (as public domain as it gets, EU/DE just doesn't know the US public domain concept).
Git says that there is at least on-the-record contribution to it by @rrrutledge, @tsadler1988, @fioddor and of course @arnom-ms (and me, but I'm asking for the change, so count me as "for"). What do you think about this change?
How could we do it:
- Add a note to our README document and add the chosen license as a file to the meeting folder. We could also add Markdown comments indicating the license to those documents.
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
Inspect the meeting folder documents and the README to identify the material covered by the proposed license change. Review the recorded contributors and the issue's CC-BY versus CC-0 options before deciding what the project accepts. Done means the chosen license is documented in the README or a license file, with Markdown license comments added where appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100