English French
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).
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.
The directory requires a file that contains the information about the team. The suggested naming convention is `NAME_team_info.adoc`, but any valid file name is acceptable. The file may be stored in the team's own documentation repository or in the https://pagure.io/Fedora-Council/council-docs/[council-docs repository]. See the https://pagure.io/Fedora-Council/council-docs/blob/main/f/engineering/modules/ROOT/partials/TEMPLATE_team_info.adoc[example template] for format and structure.
Team website
Teams will appear in the directory if the team info file is included in the `{engineering,mindshare}/modules/ROOT/pages/index.adoc` directory of the https://pagure.io/Fedora-Council/council-docs/[council-docs repo]. After `include`-ing the info file, the index page must include the `team_render.adoc` file that defines the rendering.
Team summary
Team status (active or inactive)
Teams should list the following information in the format specified by https://pagure.io/Fedora-Council/council-docs/blob/main/f/engineering/modules/ROOT/partials/TEMPLATE_team_info.adoc[the template]:
Team's preferred synchronous communication channel (e.g. IRC channel, Telegram room, etc)
Team's preferred asynchronous communication channel (e.g. mailing list, forum category, etc)
Team's meeting (preferably a link to a Fedocal event, alternatively a static day and time)
Team's issue tracker
Teams can include their `NAME_team_info.adoc` file on their page(s), and then use `{team_name}`, `{team_summary}` etc. anywhere on the page.
Teams are responsible for ensuring their entries are up to date.
Team name
Team information files
Reusing the data on team pages
Rendering the directory