Meeting asynchronously with mailing lists
draft-shmoo-async-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Mallory Knodel , Karel Novotný | ||
Last updated | 2021-05-06 (Latest revision 2020-11-02) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
For when we can't meet in person, when there's interim work to be done, or just because the task calls for it, an asynchronous text- based meeting can sometimes be perfectly productive and useful. Given how much the IETF uses email already [RFC3934] this document aims to create additional guidance for co-chairs and meeting facilitators who might want to host a meeting asynchronously with mailing lists. Drawing from decades of facilitation experience in global networks, the document also treats unique considerations for facilitators that are introduced by this meeting methodology.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)