Managing InnerSource Projects
English
English
  • Summary
  • Introduction
    • Scenarios
    • Framework
    • Authors and Reviewers
  • Infrastructure
    • Basic Infrastructure
    • Comparing How Inner-Sourced Your Infra Is
    • Authors and Reviewers
  • What, When and How to Measure
    • Goals using Metrics
      • Use Goals, Questions, and Metrics
        • Goals
          • Find InnerSource Projects
          • Reduce Duplication
        • Questions
          • What is the InnerSource Adoption Trend?
          • Who contributes to the InnerSource project?
          • Who Uses
        • Metrics
          • Code Contributions
          • Contribution Distance
          • Number of InnerSource repositories
          • Usage Count
    • Areas of Analysis
    • Goal-Question-Metric Approach
    • Strategy
    • Examples of Interest
    • References
    • Authors and Reviewers
  • Governance
  • Tooling
    • GitHub Strategy
    • GitHub Configuration
    • GitLab Strategy
    • GitLab Configuration
    • Authors and Reviewers
Powered by GitBook
On this page
  • Comparing How InnerSourced your Infrastructure is
  • Development Process Infrastructure
  • Communication Channels Infrastructure
  • Monitoring Infrastructure
  • Some Examples of Infrastructure
Edit on GitHub
Export as PDF
  1. Infrastructure

Comparing How Inner-Sourced Your Infra Is

Comparing How InnerSourced your Infrastructure is

Just detailing the infrastructure needed within an organization to effectively apply InnerSource would be simplistic. This section aims at listing the questions you need to ask to your infrastructure team to check if that internal and well known infrastructure is able to be part of the InnerSource process.

The goal of this section is to compare the internal infrastructure used within an organization and check how close this is to an ideal InnerSource toolchain. As detail, in the software development process, it is necessary the use of specific tools such as the versioning system, code review process, ticketing system, continuous integration, documentation storage and collaborative platform to share technical decisions.

For each of those, we need to check if they are following the key aspects provided such as openness.

Development Process Infrastructure

Openness
Transparency
Archivable
Searchable
Monitoring
Access Rights

Versioning

Ticketing system

Code Review

CI

Wiki/Documentation

TODO List

Collaborative notes

Communication Channels Infrastructure

Openness
Transparency
Archivable
Searchable
Monitoring
Access Rights

Mailing lists/forums

Instant channels

Questions/Answers

Monitoring Infrastructure

Openness
Transparency
Archivable
Searchable
Monitoring
Access Rights

Retrieval platform

Enrichment platform

Visualization platform

Some Examples of Infrastructure

GitHub enterprise. GitLab. In house repositories. Atlasian stack.

Last updated 1 year ago