-
Notifications
You must be signed in to change notification settings - Fork 7
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 a chapter on communication etiquette and best practices #16
Comments
Do we want to limit this to "naked pings" / chat? |
I'm happy to explore any direction you'd like, but I'm especially interested in the angle that sounds like: "here's how practitioners of open work have developed some best practices and etiquette for working remotely using chat applications, and here's why they're important." What else are you thinking? |
An interesting avenue I had not considered. Happy to work in whatever direction you both determine is best. |
Additional note that @jimmysjolund is also working on something great vis-à-vis asynchronous communication and visualization in #13. |
How about a more "best practices and etiquette" chapter approach? |
I like that, @jzb. In my mind, the "questions to ask when picking your tools" is one dimension deserving its own space. The "best practices and etiquette" is an additional, related issue (of which "naked pings" is but one topic/aspect) that in turn deserves its own space (even if we run them back-to-back in the guide). Just my two cents. |
Agreed. I think the tool selection chapter may grow beyond just communication tools and into all tools, so it makes sense to have this be a separate, broad chapter. |
OK. I'll plan on "best practices and etiquette" then. Will try to get a draft out shortly. |
And I'll update the issue title so it's a better representative 😄 |
Astute observer @jzb would like to contribute a chapter on avoiding "naked pings" (and other foibles associated with asynchronous chat), drawn on his (and others') experiences in open organizations like open source communities.
The text was updated successfully, but these errors were encountered: