InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Pattern Idea: Hive mind
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
This pattern proposal illustrates exactly what I'm trying to describe.
Often in corporations, there's a strong need to release a finished idea into the open. But here in the InnerSource Commons, even a vague intuition can be expressed, with others in the community contributing to help make it whole, or discrediting it.
When implementing InnerSource or even open source, one should be encouraged to open up early on to elicit feedback from other participants in the community, treating the community as a "hive mind".
Based on my talks with others in the community, this seems to be a novel idea, so I think it can be formalized into a pattern.
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 with the issue description and review the repository's existing patterns to understand how a proposal becomes a formalized pattern. Compare the hive-mind idea with related patterns and the discussion in this issue; done means an agreed, complete pattern suitable for the collection.
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