Skip to content

Transplant the commit suggestions from #44 onto the principles article. #87

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 1 commit into from
May 29, 2019
Merged

Transplant the commit suggestions from #44 onto the principles article. #87

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 3 additions & 3 deletions introduction/principles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,18 +38,18 @@ This means that guest teams should be able to have an understanding of:
* Progress on feature requirements
* Decision making of the host team

When possible, the above should be communicated in such a way that does lend itself to tribal knowledge.
When possible, the above should be communicated clearly and in details, from teams internal definitions of items to special case scenarios specific to the project, in a manner that can be easily understood to those that are not part of the core team.

## Prioritized Mentorship

_Mentorship_ from host team to guest team via trusted committers is a key aspect of inner source.
Contributors on guest teams are upleveled so that they understand enough about the host team system to change it successfully.
In the process of doing so, they come to better understand the host team system as a general consumer.
In the process of doing so, they come to better understand the host team's software system as a general consumer.
They can use it more effectively and help other consumers to do so as well.

It's critical that this mentorship for contributors is _Prioritized_ by the host team.
The host team should strive to make time to mentor guest team contributors _at the time that the contributor needs it_ as opposed to when it's convenient to the host team.
At times at may be a culture change for engineers on the host team to spend time helping others to code rather than just coding themselves.
At times it may be a culture change for engineers on the host team to spend time helping others to code rather than just coding themselves.
This mentorship is valuable to both the individual contributor and the host, and it is worth doing well.
It proves to be mutually beneficial in the long run, by improving the code, the contributor model and forging or
improving relationships within an organization that may not have existed otherwise.
Expand Down