English Odia
Additional information the team desires to publish in the directory
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.
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). "Teams" should be read as a catch-all term for groups in Fedora that may call themselves "Special Interest Groups (SIGs)", "Working Groups", or any other similar term.
It is expected that not all teams will have answers for the above. They should be provided when they exist.
Rendering the directory
Reusing the data on team pages
Team information files
Team name
Teams are responsible for ensuring their entries are up to date.
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.
Team's issue tracker
Team's meeting (preferably a link to a Fedocal event, alternatively a static day and time)
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)
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 status (active or inactive)
Team summary