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.

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

Add first draft for communication tooling setup. #124

Open
wants to merge 5 commits into
base: master
from

Conversation

@MaineC
Copy link
Collaborator

MaineC commented Dec 19, 2019

This is a first stab at #114 - so far it covers structured and unstructured communication channels.

It covers the difference between team channels and channels setup around a project.

It mentions that channels should be archived, searchable, linkable.

Copy link
Collaborator

rrrutledge left a comment

Thanks so much for doing this writing, @MaineC !

archived, searchable, linkable communication channels that are free to subscribe
to by anyone in the company:

- Others lurking and reading lowers the barrier to get involved raising the

This comment has been minimized.

Copy link
@rrrutledge

rrrutledge Dec 19, 2019

Collaborator

These bullets feel like part of the Resulting Context (Benefits).

This comment has been minimized.

Copy link
@MaineC

MaineC Jan 7, 2020

Author Collaborator

I agree. Moved and merged.

project-setup/communication-tooling.md Outdated Show resolved Hide resolved
project-setup/communication-tooling.md Outdated Show resolved Hide resolved
- Others lurking and reading lowers the barrier to get involved raising the
likelihood of receiving contributions.
- Answering questions in those channels means that not only other team members
can listen in and provide additional information, it also means that other

This comment has been minimized.

Copy link
@rrrutledge

rrrutledge Dec 19, 2019

Collaborator

Other users can help to answer questions, too!

This comment has been minimized.

Copy link
@MaineC

MaineC Jan 7, 2020

Author Collaborator

That's a good one to make explicit! Added.

MaineC and others added 4 commits Dec 20, 2019
Co-Authored-By: rrrutledge <rrrutledge@users.noreply.github.com>
Co-Authored-By: rrrutledge <rrrutledge@users.noreply.github.com>
Copy link
Collaborator

rrrutledge left a comment

LGTM

@MaineC

This comment has been minimized.

Copy link
Collaborator Author

MaineC commented Jan 21, 2020

Does this need the "Do 2nd review" label?

@rrrutledge

This comment has been minimized.

Copy link
Collaborator

rrrutledge commented Jan 21, 2020

I suppose so!

@MaineC

This comment has been minimized.

Copy link
Collaborator Author

MaineC commented Jan 22, 2020

Would be nice if someone added the label then - I can't do that myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.