Add Chat-Rooms page

Author: rvl

docs/index.md

@@ -6,7 +6,7 @@ pandoc:
 
 ---
 
-# Adrestia Process Docs
+# Adrestia Project
 
 :::{.sticky-note .max-w-md .mx-auto}
 **Under Construction!**

docs/index.yaml

@@ -2,7 +2,7 @@
 # https://github.com/srid/emanote/blob/master/default/index.yaml
 
 page:
-  siteTitle: Adrestia Process Docs
+  siteTitle: Adrestia Project Docs
   headHtml: |
     <meta http-equiv="cache-control" content="private, max-age=60" />
     <meta http-equiv="Expires" content="60" />

docs/process/Chat-Rooms.md

@@ -0,0 +1,91 @@
+# Chat Rooms
+
+Here are a list of Slack channels / [[Matrix]] chat rooms that we use.
+
+Most channels are invite only, so if you're not a member, someone needs to add
+you.
+
+See also: [[Communication-Conventions]]
+
+## [[Matrix]]
+
+_Adrestia Space_ - this has its own room listing which you can explore once
+you've been invited.
+
+- [\#team](https://element.adrestia.iohkdev.io/#/room/#team:adrestia.iohkdev.io) - The full Adrestia team.
+- [\#matrix-testing](https://element.adrestia.iohkdev.io/#/room/#matrix-testing:adrestia.iohkdev.io) - A room for trying out features of Matrix chat rooms and client, etc.
+- [\#dev](https://element.adrestia.iohkdev.io/#/room/#dev:adrestia.iohkdev.io) - Development discussions.
+
+## [Slack](https://input-output-rnd.slack.com])
+
+### Adrestia
+
+- `#adrestia-dev` - main channel for people across the company to ask questions of our team and discuss all things Adrestia.
+- `#adrestia-secret-fort` - decommissioned and replaced with Matrix.
+- `#adrestia-polyglot`
+- `#adrestia-daily`
+- `#adrestia-releases`
+- `#adrestia-leads`
+- `#cardano-launcher-dev`
+- `#daedalus-adrestia-node`
+- `#lightwallet`
+- `#recruiting_adrestia`
+
+### Cardano
+
+- `cardano-dev`
+- `cardano-db-sync-dev`
+- `cardano-explorer-app-dev`
+- `#consensus`
+- `#ledger`
+- `#network`
+- `#node`
+- `#node-api-and-cli`
+- `#node-logging`
+- `#plutus`
+- `#team-cardanodocs`
+
+### Daedalus
+
+- `#daedalus` - main channel to discuss all things Daedalus.
+ 
+### Channels for getting help
+
+- `#crossteam-ci`
+- `#ops`
+- `#haskell`
+- `#emacs-best-practices`
+- `#nix-best-practices`
+
+### Large channels
+
+- `#engineering` - large channel for all engineering staff.
+- `#public`
+- `#public-random`
+- `#announcements`
+- `#comms`
+- `#security-public`
+
+### Special topics
+
+- `#aus`
+- `#keyboards`
+- `#fitness`
+
+### Admin-type things
+
+- `#concur`
+- `#udemy`
+
+
+## TODO
+
+- [ ] Add a key and tag each channel with categories
+   - 🔥 High traffic
+   - 👍 Recommended to join
+   - ⛪ Public
+   - 🔒 Private
+
+- [ ] Add more channels and descriptions.
+
+- [ ] Format in tables

docs/process/Communication-Conventions.md

@@ -25,7 +25,9 @@ We will use a private Matrix server for team chats, in place of the
 Team members are asked to review messages from Slack once per day. They may
 choose to use Slack more frequently, but this is up to them.
 
-See [[Matrix]] for information about how to use the team chat rooms.
+See [[Matrix]]# for information about how to use the team chat rooms.
+
+See [[Chat-Rooms]]# for a curated list of channels on Slack and Matrix.
 
 #### When to be online
 

docs/process/QA-Approach.md

@@ -109,7 +109,7 @@ Ok, we dealt with the process focusing especially on its QA elements. Here I'd l
 
 ### Types and levels of tests
 
-Obviously we value automated tests over manual. Actually, when it comes to `cardano-wallet` we only have 6 manual scenarios that are executed as part of every [release checklist](https://github.com/input-output-hk/cardano-wallet/wiki/Release-Checklist).
+Obviously we value automated tests over manual. Actually, when it comes to `cardano-wallet` we only have 6 manual scenarios that are executed as part of every [[Release-Checklist]].
 
 All automated tests are executed in CI environment in the following circumstances:
  - on every PR merge (most of the functional suite)

docs/resources/Onboarding.md

@@ -7,18 +7,15 @@ This is the process for starting new developers on the project.
 - Team member is added to the [Input Output](https://github.com/orgs/input-output-hk/people) organization on GitHub (you need to open an [IT Change Request](https://input-output.atlassian.net/servicedesk/customer/portal/2/group/6) for this).
 - Team member is added to the [Adrestia](https://github.com/orgs/input-output-hk/teams/adrestia) group on GitHub (you need Maintainer permissions on the team to do this).
 - Team member is added to the _Adrestia_ space on [Matrix](https://element.adrestia.iohkdev.io) and [#dev](https://element.adrestia.iohkdev.io/#/room/#dev:adrestia.iohkdev.io) channel.
-- Team member is added to Slack channels
-  - `#adrestia-dev`
-  - `#adrestia-releases`
-  - (more TBA)
+- Team member is added to important [[Chat-Rooms]].
 - Team member is added to [[Passwords|LastPass shared folder]].
 - Team member is invited to weekly planning meeting and daily Hello call.
 
 ## Checklist - new team member
 
 - Provide GitHub user name to team lead.
 - Provide PGP key ID to team, and ensure that your public key is published on multiple keyservers.
-- Ensure that you have a LastPass account associated with your `@iohk.io` e-mail address.
+- Ensure that you have a [[Passwords|LastPass]] account associated with your `@iohk.io` e-mail address.
 - Follow the [[Jira#orientation-checklist|Jira Orientation Checklist]]
 - Skim the [ramp-up docs](#ramp-up-docs).
 - Ensure that you are able to edit Wikis. If you discover
@@ -28,15 +25,15 @@ This is the process for starting new developers on the project.
 
 Essential reading list for new team members.
 
-- [Building](https://github.com/input-output-hk/cardano-wallet/wiki/Building).
+- [[Building]]
     A quick guide to building the wallet from source.
-- [Testing](https://github.com/input-output-hk/cardano-wallet/wiki/Testing).
+- [[Testing]]
     An introduction on how to run tests for the wallet, once you've built it.
-- [Development Process](https://github.com/input-output-hk/cardano-wallet/wiki/Development-Process).
+- [[Development-Process]]
     Our team's development process and methodology.
 - [[Coding-Standards]]
     We strive to follow these shared standards for all newly-written code.
 - [[Code-Review-Guidelines]]
     We're always trying to improve our code review process. This document contains a few of the principles we've collected along the way. It's not complete, and we hope you can help to make it even better!
-- [[index|Adrestia Project Page]]
+- [[index]]
    General documentation about the Adrestia umbrella project, and what it is.