InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns

InnerSource @ Flutter Entertainment | innersource.flutter.com

Open
#395 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:book: Type - Content Work :tiger2: patterns-in-the-wild
Dominant language
HTML
Stars
853
Forks
206
Avg merge
1d 23h
Merged PRs (30d)
2

Description

The Flutter Entertainment InnerSource community is publishing information at
https://innersource.flutter.com/

It contains a lot of great InnerSource content, some of which we hope to distill into patterns in the future for the greater benefit of the InnerSource Commons community.

Examples of topics that sound interesting (I am sure there is more!):

  • community - The community of a repository represents the members that contributed the most to the respective repository according to a set of rules. See How it is calculated
  • Flutter Inner Source team - is that like an ISPO?
  • capabilities - "We divide each inner source product into capabilities, with each capability encapsulating something meaningful to us and our customers. Example capabilities within our betting platform are the product catalogue, bet placement, cashout, content filtering, virtual sports and so on." See here and capability owners
  • Divisional Independence especially the Virtual Maintainer Team sounds interesting
  • Strategic Consensus for Significant Change => sounds similar to our RFC pattern
  • Work Type Analysis

Luckily we have @robtuley with us, who is the a great person to ask about this :)

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.

Research direction

Review the material at innersource.flutter.com, especially the community, capabilities, divisional independence, strategic consensus, and work type analysis pages. Compare those topics with the existing InnerSource Commons patterns and determine which material can become useful patterns. The issue does not define a specific pattern, file, test, or completion criteria.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.