Skip to content

Commit cb5992a

Browse files
committed
Merge branch 'main' of github.com:InnerSourceCommons/managing-innersource-projects into add-mdbook
2 parents 64c646d + bf8e63f commit cb5992a

File tree

3 files changed

+23
-37
lines changed

3 files changed

+23
-37
lines changed

README.md

Lines changed: 17 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,17 +2,29 @@
22

33
![Managing InnerSource Projects](managing-innersource-projects-cover.jpg)
44

5-
This book is intended to bring, from a managerial perspective, the several aspects needed
6-
when introducing InnerSource methodologies into enterprises.
5+
## What is this book about?
76

8-
This book is a work in progress process where anyone is more than welcome to contribute
7+
This book is intended to cover all aspects of managing an InnerSource Program at an organization.
8+
Pitching, starting, scaling, training, governance, infrastructure, metrics, motivation, and much more!
9+
If there is any explanation that you need in relation to your InnerSource Program, then this book is intended to have it.
10+
11+
## How is the book structured?
12+
13+
This book is divided into sections and articles, each of which cover one single aspect of an InnerSource Program.
14+
Articles should be relatively short and self-contained so that they can be read in any order and any amount and still be useful.
15+
Detailed explanation of InnerSource topics should go in the [InnerSource Patterns] book and be linked from the article here.
16+
Think of the articles in this book like either a conversational introduction/summary to a pattern or possible a journey showing how multiple patterns can be used together in an InnerSource Program.
17+
18+
## Who can contribute?
19+
20+
This book is a work in progress where anyone is more than welcome to contribute
921
in any possible way. Ideas, comments, typos, full paragraphs or sections would be
1022
great. This repository aims at bringing specialized knowledge from the industry
1123
within this respect in a way that this is useful for third parties. For this, we are
1224
actively looking for reviewers that can help in this process.
1325
For those that have already contributed to the book, thanks a lot!
1426

15-
You can find more information about the process in the [contributing section](https://github.com/dicortazar/managing-inner-source-projects/blob/main/CONTRIBUTING.md).
27+
You can find more information about the process in our [contributing section](./CONTRIBUTING.md).
1628

1729
## Who is fostering this initiative?
1830

@@ -55,3 +67,4 @@ All of the content found in this repository is licensed [CC BY-SA 4.0](https://c
5567
[Bitergia]: https://bitergia.com/
5668
[ISPO Working Group]: https://innersourcecommons.org/community/#ispo
5769
[InnerSource Commons]: https://innersourcecommons.org/
70+
[InnerSource Patterns]: https://patterns.innersourcecommons.org/

introduction/framework.md

Lines changed: 2 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -32,40 +32,9 @@ Let's introduce the *InnerSource framework*.
3232

3333
## Governance
3434

35-
According to the Business Dictionary, governance is defined as:
35+
A core aspect of the InnerSource framework is the governance model. Good governance is essential for the success of any project, and InnerSource is no exception.
3636

37-
>Establishment of policies, and continuous monitoring
38-
>of their proper implementation, by the members of the
39-
>governing body of an organization. It includes the
40-
>mechanisms required to balance the powers of the
41-
>members (with the associated accountability), and
42-
>their primary duty of enhancing the prosperity and
43-
>viability of the organization
44-
45-
In open source, governance is described in the "governance
46-
model" document, defined by [OSSWatch](http://oss-watch.ac.uk/resources/governancemodels) as:
47-
48-
>A governance model describes the roles that project participants
49-
>can take on and the process for decision making within the project.
50-
>In addition, it describes the ground rules for participation in the
51-
>project and the processes for communicating and sharing within
52-
>the project team and community
53-
54-
Usually the governance model is a written document containing:
55-
56-
- project goals
57-
58-
- work, management and collaboration infrastructures definition
59-
60-
- people roles and responsibilities definitions
61-
62-
- community support mechanisms
63-
64-
- decision making process policies description
65-
66-
- contribution process policies description
67-
68-
- monitoring policies and mechanisms description
37+
Pick the right [governance standards and model](/governance/governance.md) for your organization.
6938

7039
## Technical infrastructure
7140

tooling/innersource-tooling.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,10 @@
44

55
This documentation is a compilation of the essential settings and strategies necessary for implementing InnerSource inside an organization. It encompasses both overall strategic elements and specific points relating to SCM configuration.
66

7+
We also encourage you to read the OpenSSF's (Open Source Security Foundation's)
8+
[Source Code Management Configuration Best Practices guide](https://best.openssf.org/SCM-BestPractices/)
9+
for a perspective focused entirely on security.
10+
711
## Table of Contents
812

913
### GitHub

0 commit comments

Comments
 (0)