From bc78f05513fe82d2954486cf76d3f19fa03ef0a6 Mon Sep 17 00:00:00 2001
From: Ben Cotton <bcotton@fedoraproject.org>
Date: Aug 26 2020 16:23:25 +0000
Subject: Add documentation about the team directory


This should help address the concerns raised in last week's Council meeting.

---

diff --git a/council/modules/ROOT/pages/procedures/team_directory.adoc b/council/modules/ROOT/pages/procedures/team_directory.adoc
new file mode 100644
index 0000000..d45ae92
--- /dev/null
+++ b/council/modules/ROOT/pages/procedures/team_directory.adoc
@@ -0,0 +1,45 @@
+= Fedora Team Directory
+
+In order to provide visibility into what teams exist _and are active_ in Fedora, the Council https://communityblog.fedoraproject.org/fedora-council-november-2019-meeting-more-miscellaneous-stuff[decided] to maintain a directory that receives regular checks.
+Council representatives are responsible for periodic evaluation of the teams under their area (D&I, Engineering, and Mindshare).
+
+== Intent
+
+The team directory is intended to make visible: 1. what teams are active in the community, and 2. how to contact them.
+Fedora is a large community with many different activities, and the directory will help existing and potential community members find the team they are looking for.
+Having periodic checks helps to ensure that the information is accurate and that we don't point people toward teams that are no longer active.
+
+The intent is _not_ to increase the administrative burden on teams or the barriers to starting a team.
+The intent is _not_ to say "if you are not listed, you are not allowed to be a team in Fedora".
+However, presence in the directory may be used by other teams to evaluate funding or work requests (e.g. website work or design assets).
+
+== Content
+
+Teams should list the following information in the format specified by https://pagure.io/Fedora-Council/council-docs/blob/master/f/engineering/modules/ROOT/partials/TEMPLATE_team_info.adoc[the template]:
+
+* Team name
+* Team summary
+* Team website
+* Team status (active or inactive)
+* Team's preferred asynchronous communication channel (e.g. mailing list, forum category, etc)
+* Team's preferred synchronous communication channel (e.g. IRC channel, Telegram room, etc)
+* Team's issue tracker
+* Team's meeting (preferably a link to a Fedocal event, alternatively a static day and time)
+* Additional information the team desires to publish in the directory
+
+NOTE: It is expected that not all teams will have answers for the above.
+They should be provided when they exist.
+
+Content may be stored in the https://pagure.io/Fedora-Council/council-docs[council-docs] repo if the team does not have its own docs repo.
+If a team has its own docs repo, the content can be kept in that repo so that it can be used to render the team's own documentation.
+This allows for a single source of truth and prevents content from diverging.
+
+== Responsibilites
+
+Teams are responsible for ensuring their entries are up to date.
+
+The Diversity & Inclusion, Engineering, and Mindshare representatives to the Fedora Council are responsible for ensuring that the team that fall under their area keep the information is up-to-date and removing teams that do not appear to be active.
+They are _not_ responsible for _providing_ the information.
+Representatives may delegate sections of their area as they see fit.
+Checks can be done at any time, but should be done around the branch date for each release at a minimum.
+