30 lines
1 KiB
Markdown
30 lines
1 KiB
Markdown
```eval_rst
|
|
.. _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
|
|
```
|
|
|
|
Try to get important meetings on our :ref:`calendars`
|
|
|
|
.. note::
|
|
Agarics can get more detail `on communication channels in the wiki <https://gitlab.com/agaric/internal/wikis/Communication-Channels>`.
|
|
|