Skip to content

Commit 28dccdd

Browse files
committed
Move benefits to resulting context.
1 parent 113adc4 commit 28dccdd

File tree

1 file changed

+20
-21
lines changed

1 file changed

+20
-21
lines changed

project-setup/communication-tooling.md

Lines changed: 20 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -29,20 +29,7 @@ answer.
2929

3030
The host team needs to be clear on the benefit of providing company-public,
3131
archived, searchable, linkable communication channels that are free to subscribe
32-
to by anyone in the company:
33-
34-
- Others lurking and reading lowers the barrier to get involved raising the
35-
likelihood of receiving contributions.
36-
- Answering questions in those channels means that not only other team members
37-
can listen in and provide additional information, it also means that other
38-
users with the same question see (or later on find) the previous answer leading
39-
to a lower need to repeat explanations.
40-
- Keeping communication in asynchronous channels allows for participants on
41-
different schedules - either due to different time zones or due to different
42-
routines - to meaningfully contribute to the project.
43-
- Using asynchronous communication channels creates a base level of passive
44-
documentation that can be referenced again when similar questions come up
45-
again.
32+
to by anyone in the company.
4633

4734
The goal when streamlining communication channels for InnerSource projects
4835
should be to align communication around topics, not around certain sets of
@@ -71,14 +58,26 @@ personally back to official communication channels.
7158

7259
# Resulting Context
7360

74-
Setting up and consistently using official communication channels helps collect
75-
passive documentation.
61+
Setting upt and consistently using official asynchronous communication channels
62+
helps create a base level of passive documentation that can be referenced again
63+
when similar questions come up again.
7664

7765
With communication happening in the open others can easily follow project
78-
progress and get active contributing.
66+
progress and get active contributing. Others lurking and reading lowers the
67+
barrier to get involved raising the likelihood of receiving contributions.
68+
69+
With questions being answered in public more people can add their perspective
70+
leading to a complete picture - this includes not only host team members,
71+
but also users of the project.
72+
73+
Keeping communication in asynchronous channels allows for participants on
74+
different schedules - either due to different time zones or due to different
75+
routines, meeting schedules, team routines - to meaningfully contribute to
76+
the project.
77+
78+
Answering questions in those channels means that not only other team members
79+
can listen in and provide additional information, it also means that other
80+
users with the same question see (or later on find) the previous answer leading
81+
to a lower need to repeat explanations.
7982

80-
With answers being answered in public more people can add their perspective
81-
leading to a complete picture.
8283

83-
Participation in the project becomes independent from meeting schedules and
84-
working schedules of different teams.

0 commit comments

Comments
 (0)