Skip to content

Airbus pattern use #622

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 24, 2023
Merged

Airbus pattern use #622

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c1c7782
add Airbus use of patterns
sicot-f Nov 23, 2023
aa6b0aa
change emphasis style
sicot-f Nov 24, 2023
5598ff8
correct link to other pattern
sicot-f Nov 24, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions patterns/2-structured/dedicated-community-leader.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,7 @@ Having excellent and dedicated community leaders is a precondition for the succe
## Known Instances

* _BIOS at Robert Bosch GmbH_. Note that InnerSource at Bosch was, for the majority, aimed at increasing innovation and to a large degree dealt with internal facing products. This pattern is currently not used at Bosch for lack of funding.
* _Airbus_. A data scientist wanted to improve the collaboration with peers in the group and found: i) many developers (beyond data science) wanted that too and were happy someone was taking care of the issue, and ii) support from line manager and middle management to eventually act as the _de facto_ community leader, on top of his regular line of duty.

## Alias

Expand Down
2 changes: 2 additions & 0 deletions patterns/2-structured/innersource-license.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,8 @@ The mentioned collaboration challenges include:

It is worth mentioning that so far the software shared under this InnerSource license is mostly tooling, infrastructure, and tools lower in the stack.

Airbus created ad hoc InnerSource licenses to enable InnerSource way of working within a large part of the group.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean by "ad hoc" in this context?
Do you have a template that people should use to create their own licenses? Or do you prescribe a single one? Or something else? :)

Also can you share if you modelled your licenses after any open source license that is out there, and why?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By "ad hoc" I mean we created them from scratch (not based on open-source licenses) for the sole sake of Airbus InnerSource program. Our IP team was used to commercial licenses while developers were more familiar with open-source ones. We iterated many times to find common grounds and also comply with the transfer pricing directive. I'll see with my colleagues if I can share more. Keep you posted.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would be awesome!


## Status

* Structured
Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/maturity-model.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -213,6 +213,7 @@ long term.
* Entelgy
* Zylk
* Bitergia
* Airbus

## Authors

Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/project-setup/base-documentation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,6 +132,7 @@ started right away: [README-template.md](templates/README-template.md),
* Paypal Inc.
* Mercado Libre - create a documentation site that contains how to get started with InnerSource and also define the basic artifacts that a repository must have to be InnerSource (README, CONTRIBUTING, CODING_GUIDELINES, etc).
* Analog Devices Inc.
* Airbus

## Authors

Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/repository-activity-score.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,6 +115,7 @@ The repository activity score is a simple calculation based on the GitHub API. I
## Known Instances

* Used in SAP's InnerSource project portal to define the default order of the InnerSource projects. It was first created in July 2020 and is fine-tuned and updated frequently ever since. When proposed to the InnerSource Commons in July 2020, this pattern emerged. Also see [Michael Graf & Harish B (SAP) at ISC.S11 - The Unexpected Path of Applying InnerSource Patterns](https://www.youtube.com/watch?v=6r9QOw9dcQo&list=PLCH-i0B0otNQZQt_QzGR9Il_kE4C6cQRy&index=6).
* Airbus took a lot of inspiration from this pattern to create an "InnerSource score" that combines the activity score together with checks from the [Standard Base Documentation](./project-setup/base-documentation.md) and the [InnerSource License](./innersource-license.md).

## Status

Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/start-as-experiment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,7 @@ Finally, starting as an experiment makes it much easier to sidestep regulations
## Known Instances

- Robert Bosch GmbH (globally distributed software development)
- Airbus: the data science community collaborated on shared Python libraries that eventually lead to a group-wide InnerSource scheme for any software.

## Status

Expand Down