diff --git a/README.md b/README.md
index d133bb0158029aaf20b88175383ee92f129a2d07..c28635d231a5a7e8edb2ada123d810dd14c3b328 100644
--- a/README.md
+++ b/README.md
@@ -17,9 +17,6 @@ in a suggested reading order:
* Our [transparency](transparency.md) principles and practices.
-* How we conduct [meetings](meetings.md).
-
* How we [communicate](communication.md) among ourselves and to the world.
-* How we [store](storage.md) our information.
diff --git a/communication.md b/communication.md
index 4ebf4e90cdd2e0b116d73e31a8ea13df6828af4b..85f116662ff72d30579cfa301fa5a9e5451fbe35 100644
--- a/communication.md
+++ b/communication.md
@@ -3,6 +3,8 @@
This document describes how the Haskell Foundation Board communicates
among itself and to the broader Haskell community.
+## Asynchronous communication
+
1. Communication within the HF is via GNU Mailman [mailing lists](https://mail.haskell.org/mailman/listinfo). (TODO: Move these lists from `haskell.org` to `haskell.foundation`.)
The main mailing list of the Board is `board@lists.haskell.foundation`; other
sub-groups have their own lists, as viewable at the link above. Long-running
@@ -23,3 +25,98 @@ among itself and to the broader Haskell community.
1. TODO: How will the Haskell Foundation advertise e.g. new board positions? Should
we have a (non-exhaustive) list of social media websites, etc., to contact?
+
+## Synchronous communication (meetings)
+
+### General Terms
+
+1. Meetings are generally called by the Chair. It is expected that the Chair
+ be responsive to a request from another Member to call a meeting, but if
+ the Chair is unresponsive, any Member can call a meeting.
+
+2. Meetings are scheduled in a manner as equitable as possible to our varied
+ membership. Specifically, meetings will not be scheduled in such a way that
+ any one Member is regularly prevented from participating in all meetings.
+
+3. All Board meetings and official Task Force or Committee meetings are
+ posted on the official Haskell Foundation calendar. The public
+ may access this [calendar](https://calendar.google.com/calendar/u/1?cid=Mmc5OXI0azIxam02aXNyZmQyNmhpdTQ0cWNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ).
+
+### Agendas
+
+1. All meetings have an agenda posted beforehand by the Member who called
+ the meeting (generally the Chair), ideally at least 48 hours before the
+ meeting time.
+
+2. Agendas are posted in the appropriate folder in Google Drive.
+
+3. Agendas may be edited in advance of the meeting to add items or clarifying questions.
+
+4. Board Members will not remove others' agenda items or otherwise subvert agendas.
+
+5. After the meeting, the agenda is be made public by being added to the
+ [minutes repository](https://gitlab.haskell.org/hf/minutes).
+
+### Minutes
+
+See also our [Transparency](transparency.md) notes.
+
+1. Minutes are taken for all official meetings.
+
+2. For Task Force meetings, the Leader of the Task Force acts as its Secretary.
+
+3. The Secretary creates the minutes document in Google Drive before the meeting.
+
+4. All meeting participants are expected to collaboratively contribute to the
+ meeting minutes. The Secretary is ultimately responsible for the accurate
+ capturing of the meeting minutes.
+
+5. Attendees of the minutes edit the minutes within 24 hours of the meeting
+ to correct any misquotes, etc., that were recorded.
+
+5. The Secretary is responsible to review the minutes after the meeting to
+ ensure they are appropriate for publishing.
+
+8. Minutes are automatically ratified 24 hours after the end of the meeting or
+ as soon as all pending objections have been resolved, whichever comes
+ first.
+
+8. There is the possibility that some details are redacted in the minutes
+ before posting. These details might concern, for example, personnel decisions
+ or not-yet-closed fund-raising negotations.
+
+9. The Secretary is responsible for publishing the minutes in a timely manner
+ after ratification.
+
+1. Minutes are posted in the [hf/minutes](https://gitlab.haskell.org/hf/minutes)
+ repository.
+
+## Storage
+
+1. The Haskell Foundation maintains a [Google Drive
+ folder](https://drive.google.com/drive/folders/1gxc2miCWM0gwMoA7ywUH3qY--q277Ifc?usp=sharing)
+ and a [GitLab group](https://gitlab.haskell.org/hf). Google Drive is good
+ for co-editing documents; GitLab is good for long-term archiving and public
+ release.
+
+2. All Board members and the Executive Team have read/write access to both the
+ Drive folder and the GitLab group. The Chair, the Treasurer, and the Executive
+ Director have the ability to add/remove additional individuals.
+
+3. Sub-parts of both the Drive folder and the GitLab group may be made
+ public by a decision of the Board.
+
+4. It may be convenient to grant individuals who are not on the Board and not
+ employed by the Foundation full access to these resources; any such
+ decision will be documented with a rationale.
+
+### Current status
+
+The GitLab group currently hosts three repositories:
+
+* `meta`: Details of how the Haskell Foundation conducts its business. World-readable.
+
+* `minutes`: Ratified minutes of official meetings. World-readable.
+
+* `proposals`: Accepted proposals for what the Haskell Foundation should seek to do.
+ Merge Requests in this repository are pending proposals. World-readable.
diff --git a/meetings.md b/meetings.md
deleted file mode 100644
index df0d3378baba205d423ae292942f917c9c3cc936..0000000000000000000000000000000000000000
--- a/meetings.md
+++ /dev/null
@@ -1,68 +0,0 @@
-# Meetings
-
-This document describes the processes for all official Haskell Foundation
-meetings, including both meetings of the Board and meetings of Task Forces
-and Committees.
-
-## General Terms
-
-1. Meetings are generally called by the Chair. It is expected that the Chair
- be responsive to a request from another Member to call a meeting, but if
- the Chair is unresponsive, any Member can call a meeting.
-
-2. Meetings are scheduled in a manner as equitable as possible to our varied
- membership. Specifically, meetings will not be scheduled in such a way that
- any one Member is regularly prevented from participating in all meetings.
-
-3. All Board meetings and official Task Force or Committee meetings are
- posted on the official Haskell Foundation calendar. The public
- may access this [calendar](https://calendar.google.com/calendar/u/1?cid=Mmc5OXI0azIxam02aXNyZmQyNmhpdTQ0cWNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ).
-
-## Agendas
-
-1. All meetings have an agenda posted beforehand by the Member who called
- the meeting (generally the Chair), ideally at least 48 hours before the
- meeting time.
-
-2. Agendas are posted in the appropriate folder in Google Drive.
-
-3. Agendas may be edited in advance of the meeting to add items or clarifying questions.
-
-4. Board Members will not remove others' agenda items or otherwise subvert agendas.
-
-5. After the meeting, the agenda is be made public by being added to the
- [minutes repository](https://gitlab.haskell.org/hf/minutes).
-
-## Minutes
-
-See also our [Transparency](transparency.md) notes.
-
-1. Minutes are taken for all official meetings.
-
-2. For Task Force meetings, the Leader of the Task Force acts as its Secretary.
-
-3. The Secretary creates the minutes document in Google Drive before the meeting.
-
-4. All meeting participants are expected to collaboratively contribute to the
- meeting minutes. The Secretary is ultimately responsible for the accurate
- capturing of the meeting minutes.
-
-5. Attendees of the minutes edit the minutes within 24 hours of the meeting
- to correct any misquotes, etc., that were recorded.
-
-5. The Secretary is responsible to review the minutes after the meeting to
- ensure they are appropriate for publishing.
-
-8. Minutes are automatically ratified 24 hours after the end of the meeting or
- as soon as all pending objections have been resolved, whichever comes
- first.
-
-8. There is the possibility that some details are redacted in the minutes
- before posting. These details might concern, for example, personnel decisions
- or not-yet-closed fund-raising negotations.
-
-9. The Secretary is responsible for publishing the minutes in a timely manner
- after ratification.
-
-1. Minutes are posted in the [hf/minutes](https://gitlab.haskell.org/hf/minutes)
- repository.
diff --git a/storage.md b/storage.md
deleted file mode 100644
index 853d33443b114cf1fe49350326701e1543f8737a..0000000000000000000000000000000000000000
--- a/storage.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# Storage
-
-This document describes the practices of how the Haskell Foundation stores
-its digital assets.
-
-1. The Haskell Foundation maintains a [Google Drive
- folder](https://drive.google.com/drive/folders/1gxc2miCWM0gwMoA7ywUH3qY--q277Ifc?usp=sharing)
- and a [GitLab group](https://gitlab.haskell.org/hf). Google Drive is good
- for co-editing documents; GitLab is good for long-term archiving and public
- release.
-
-2. All Board members and the Executive Team have read/write access to both the
- Drive folder and the GitLab group. The Chair, the Treasurer, and the Executive
- Director have the ability to add/remove additional individuals.
-
-3. Sub-parts of both the Drive folder and the GitLab group may be made
- public by a decision of the Board.
-
-4. It may be convenient to grant individuals who are not on the Board and not
- employed by the Foundation full access to these resources; any such
- decision will be documented with a rationale.
-
-## Current status
-
-The GitLab group currently hosts three repositories:
-
-* `meta`: Details of how the Haskell Foundation conducts its business. World-readable.
-
-* `minutes`: Ratified minutes of official meetings. World-readable.
-
-* `proposals`: Accepted proposals for what the Haskell Foundation should seek to do.
- Merge Requests in this repository are pending proposals. World-readable.
diff --git a/transparency.md b/transparency.md
index ab84fe60f1b6fd14cf80333c4d25577cfd72a1f6..087f058523f97b68891761db9c6f6847e367321f 100644
--- a/transparency.md
+++ b/transparency.md
@@ -26,7 +26,7 @@ Haskell Foundation (HF).
## Practices
1. Minutes for all official meetings are posted publicly; details are in
- the [meetings](meetings.md) document.
+ the [communications](communications.md) document.
2. The Haskell Foundation [calendar](https://calendar.google.com/calendar/u/1?cid=Mmc5OXI0azIxam02aXNyZmQyNmhpdTQ0cWNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ) is public.