InnerSourceCommons / InnerSourceCommons/InnerSourceLearningPath

Common concerns people have when adopting InnerSource

Open
#455 2 comments 1 reaction 1 assignee View on GitHub

@tsadler1988 is already working on this.

Since Jan 10, 2022.

Introduction
Dominant language
JavaScript
Stars
77
Forks
47
Avg merge
11h 11m
Merged PRs (30d)
5

Description

We have observed that new adopters of InnerSource have common concerns e.g.

  • What is the cost/overhead?
  • Why not just open source?
  • Will this slow us down?
  • Will we just be reviewing PRs all day every day?

This could be a candidate for a new segment within the introduction section.

We may start this as a simple FAQ.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.