Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Pattern extraction | Learning By Lurking

Open
#406 9 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale

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.

Description

:book: Type - Content Work :tiger2: patterns-in-the-wild

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.

Dominant language
HTML
Stars
853
Forks
206
Avg merge
1d 23h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from InnerSourceCommons/InnerSourcePatterns

All issues in InnerSourceCommons/InnerSourcePatterns

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.