Skip to content
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

Create unreachable-communication-channels.md #499

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Create unreachable-communication-channels.md #499

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a279c6d
Create unreachable-communication-channels.md
Trueblueaddie Dec 4, 2022
3e5fc71
Update unreachable-communication-channels.md
Trueblueaddie Dec 6, 2022
c1c6be1
Update unreachable-communication-channels.md
Trueblueaddie Dec 6, 2022
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
51 changes: 51 additions & 0 deletions patterns/2-structured/unreachable-communication-channels.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
## Title

Unreachable Communication Channels

## Patlet

Communications channels require explicit access requests that leave the organization silo-ed. A public portal was created to build transparency for InnerSource practice, process, and impact.

## Problem

Currently at the organization there is a silo-ed culture for communication channels. People that work in certain areas of the organization need explicit communication access to others, even when they are using a similar toolchain (e.g. Microsoft Teams). This can be extended to geographical locations.

## Context

Highly regulated industries experience high scrutiny for information publicly shared. Internally companies experience similar limitations between departments and teams.

## Forces

Against:
Existing regulation that forces the organization to use local pieces of infrastructure unreachable by others within the corporation.
Sense of ownership and control of the communication channels or pieces of infrastructure to be used by the project.
In favor:
Willingness to use a shared and common repository
Need of the technical teams to use a shared repository for code management, tickets, etc.

## Solutions

The solution was to provide a central point where participants can find and teams/SIGs can ask for InnerSource-friendly (public, open, and indexed) communication channels.

## Resulting Context

Anyone in the InnerSource region (country, Europe, world level) has full transparency on the existing projects and they have read access by default. This process has to be transparent and as easy as possible to lower the barriers to contribution. The desired situation is that once you are within the firewall of the organization, you have full access to any project.

## Known Instances

Santander Bank

## Status

Structured
Published internally in Santander Bank; drafted via pull-request in December of 2022

## Authors

Alberto Pérez García-Plaza
Daniel Izquierdo Cortázar
Addie Girouard

## Acknowledgements

Igor Zubiaurre