36 lines
1.5 KiB
ReStructuredText
36 lines
1.5 KiB
ReStructuredText
.. _in_team_communication:
|
|
|
|
In-team communication
|
|
=====================
|
|
|
|
Tasks people need to do go in GitLab, but that is *not* how tasks should be communicated. Whenever possible, anything important enough to be assigned is worth talking about in 'real-time' first, or concomitantly. Everything needed to understand an issue should be captured in GitLab, but we want to avoid back-and-forth 'huh what?' and 'nuh-uh not me' (un-assign)
|
|
|
|
Discussion that takes place outside of GitLab needs to be summarized (or copy-pasted) into the relevant issue in the GitLab project.
|
|
|
|
IRC
|
|
---
|
|
|
|
#agaric
|
|
|
|
Agaric also maintains a channel for worker-owners only.
|
|
|
|
Freenode has given us operator privileges for these channels. To use it, we need to register:
|
|
|
|
```
|
|
/msg nickserv identify mlncn pa55w0rd
|
|
/chanserv op #agaric mlncn
|
|
```
|
|
|
|
.. note::
|
|
Agarics can get more detail `on communication channels in the wiki <https://gitlab.com/agaric/internal/wikis/Communication-Channels>`.
|
|
|
|
Principles
|
|
----------
|
|
|
|
* Document closest to where people work:
|
|
* In README.md files or otherwise in the code repository for developers.
|
|
* In the site itself for site managers and content editors, or alternatively in an organization's already established locations.
|
|
* Topics which are of general application can be abstracted, put in this repository, and linked to at this documentation.
|
|
|
|
.. note::
|
|
In doing documentation we are living our :ref:`values` of encouraging continuous learning, appreciating new ideas, giving back to the communities we are part of, and valuing long-term relationships.
|