Skip to content

Clean up the mis-merges introduced by #117. #164

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
Oct 21, 2019
Merged

Clean up the mis-merges introduced by #117. #164

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
20 changes: 2 additions & 18 deletions contributor/04-mechanics-of-contributing-article.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,26 +41,16 @@ It's better to add more slack time initially - you'll get a feeling about the tu
Often, you will notice a reduction in turn-around time per host team after making a few successful contributions to that host team.
This is effect can be observed with Open Source as well, you can read more about it [here](#buildup-of-trust-through-collaboration).

[EDITOR NOTE: There was actually a paper on how trust is build up on remote/asynchronous collaboration. Maybe I'll find that again.
The basic point is that aside of reliability in collaboration, continued presence the effect of water cooler discussions and food/drink consumption is quite impressive...
]
Comment on lines -44 to -46
Copy link
Member

@MaineC MaineC Oct 21, 2019

Choose a reason for hiding this comment

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

I assume you didn't find the publication?

Copy link
Member Author

@lenucksi lenucksi Oct 21, 2019 •
edited
Loading

Choose a reason for hiding this comment

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

The trust in PR's paper is the one that is linked at the bottom of the corresponding article.
A food & water cooler one didn't pop up in my paper stash anymore. The first one is worth a look, though.


### Expectation management

In your classic teams everyone had an idea of the expectable lead times.
Within an InnerSource context this might not be the case, either due to large time-zone differences (e.g. Seattle, USA with PDT vs Berlin, Germany with CEST) or you not being available full-time as with your original team even if they are in the same physical location as you are.
Thus, to prevent frustration on both sides, impatience and other non-trust-building effects you'll need to explicitly do expectations management with regards to your expected reaction times.
One approach be to just quickly react with a "I'll look into it, I won't get to it in the next few days though" to a Trusted Committer's feedback if you know that you'll only be able to come back to them in a few days.
Ideally you can provide them with a rough estimate when you likely will have time to take a look at their input.
Doing so builds trust by reliability even over non-physical contact, longer distance or otherwise asynchronous media.
Established trust will allow you overcome uncertainty bumps in the collaborative road ahead of you.
### Building trust

InnerSource puts huge weight on written communication - in particular when it comes to project decisions.
Does that imply that in-person communication is forbidden?

Clearly not: Where written communication shines when it comes to archiving and searchability, in-person communication shines when it comes to communication bandwidth.
Try to make time to meet the people behind the names. If possible, try to meet them over your favorite beverage or some food.
When you're able to hear people speak, when you know their idiosyncrasies remote collaboration will become easier.
### Building trust

InnerSource puts huge weight on written communication - in particular when it comes to project decisions.
Expand All @@ -69,13 +59,7 @@ Does that imply that in-person communication is forbidden?
Clearly not: Where written communication shines when it comes to archiving and searchability, in-person communication shines when it comes to communication bandwidth.
Try to make time to meet the people behind the names. If possible, try to meet them over your favorite beverage or some food.
When you're able to hear people speak, when you know their idiosyncrasies remote collaboration will become easier.

[EDITOR NOTE: There was actually a paper on how trust is build up on remote/asynchronous collaboration. Maybe I'll find that again.
The basic point is that aside of reliability in collaboration, continued presence the effect of water cooler discussions and food/drink consumption is quite impressive...
]
[EDITOR NOTE: There was actually a paper on how trust is build up on remote/asynchronous collaboration. Maybe I'll find that again.
The basic point is that aside of reliability in collaboration, continued presence the effect of water cooler discussions and food/drink consumption is quite impressive...
]
Comment on lines -76 to -78
Copy link
Member

@MaineC MaineC Oct 21, 2019

Choose a reason for hiding this comment

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

Was that by intention that you deleted both paragraphs?

Copy link
Member Author

@lenucksi lenucksi Oct 21, 2019

Choose a reason for hiding this comment

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

This is the same note as the one for 44-46, thus removing both. Comment is addressed above.


### Avoiding rejection

Do you have a large feature that you want to contribute?
Expand Down