InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Pattern extraction | Learning By Lurking
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
The blog post Learning By Lurking describes an approach to creating a learning culture in an organization, that reminds us of some of the ideas of InnerSource.
There are also some conversations on twitter about this.
Maybe this is a pattern? However it might be too generic to be a pattern, not sure.
I posted a question on the hackernews discussion of the above article, to find out if the author specifically had an Open Source context in mind, or InnerSource as well.
Leaving this rather unfinished idea here, to see what others think about the blog post.
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
Start by reading the linked “Learning By Lurking” article and the referenced Twitter and Hacker News discussions. Check whether they provide a sufficiently specific InnerSource pattern; done means reaching a decision and, if supported, documenting a complete pattern rather than leaving the idea unfinished.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100