Zen

Source string Source string

201/10000 · 201

The string is read only.

English Actions
Fedora Team Directory
In order to provide visibility into what teams exist _and are active_ in Fedora, the {team_name} link:{COMMBLOG}/fedora-council-november-2019-meeting-more-miscellaneous-stuff[decided] to maintain a directory that receives regular checks. {team_name} representatives are responsible for periodic evaluation of the teams under their area (DEI, 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 (WGs)", or any other similar term.
Intent
The team directory is intended to make visible:
What teams are active in the community.
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 do not 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 the https://pagure.io/Fedora-Council/council-docs/blob/main/f/engineering/modules/ROOT/partials/TEMPLATE_team_info.adoc[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
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.
Responsibilities
Teams are responsible for ensuring their entries are up to date.
The DEI, Engineering, and Mindshare representatives to the {team_name} are responsible for ensuring that the team that falls under their area keeps the information up-to-date and removes 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.
Mechanism

Loading…

User avatar None

String updated in the repository
Teams should list the following information in the format specified by the https://pagure.io/Fedora-Council/council-docs/blob/main/f/engineering/modules/ROOT/partials/TEMPLATE_team_info.adoc[template]:
Teams should list the following information in the format specified by the https://pagure.io/Fedora-Council/council-docs/blob/main/f/engineering/modules/ROOT/partials/TEMPLATE_team_info.adoc[template]:
a year ago
Browse all string changes

Things to check

Long untranslated

The string has not been translated for a long time

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
type: Plain text
Flags
read-only
Source string location
./pages/procedures/team_directory.adoc:30
String age
a year ago
Last updated
a year ago
Source string age
a year ago
Translation file
pot/master/pages/procedures/team_directory.pot, string 10