@evan some time ago you queried about what would be a good comms channel for #ActivityPub API.

I have some ideas / recommendations on the #Github repo that the #W3C TF uses.

- Structure the repo to hold the work of the full task force, not just for the creation of a single specification document.

- Use GH Discussions for all the general elaboration, feedback collection, etc. The repo forms a self-contained body of work. Move most current Issues in the tracker to become Discussions.

- Issues are created by task force members, and always represent actionable items. They are tracked on a Project kanban board where the swimlanes represent a simple protocol development #Process with a number of stages.

Then:

- Primary comms channel is Discussions.
- Issues + kanban represent work tracks.
- Secondary comms channel can be #fedi.

I'd reserve #SocialCG mailing list to #governance and organizational matters concerning the CG itself, and point mails on other subject to appropriate channel.