Fedoras gruppkatalog

In order to provide visibility into what teams exist and are active in Fedora, the Fedora Council decided to maintain a directory that receives regular checks. Fedora Council 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.

Avsikt

The team directory is intended to make visible:

  1. What teams are active in the community.

  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 do not point people toward teams that are no longer active.

Avsikten är inte att öka den administrativa bördan på grupper eller att höja tröskeln för att starta en grupp. Avsikten är inte att säga ”om man inte är listad får man inte vara en grupp inom Fedora”. Dock kan förekomst i katalogen användas av andra grupper för att utvärdera finansiering eller arbetsbegäranden (t.ex. webbsajtarbete eller designtillgångar).

Innehåll

Teams should list the following information in the format specified by the template:

  • Gruppnamn

  • Gruppsammanfattning

  • Gruppens webbplats

  • Gruppstatus (aktiv eller inaktiv)

  • Gruppens föredragna asynkrona kommunikationskanal (t.ex. e-postlista, forumkategori, etc.)

  • Gruppen föredragna synkrona kommunikationskanal (t.ex. IRC-kanal, Telegram-rum, etc.)

  • Gruppens ärendehanterare

  • Gruppens möten (helst en länk till en Fedcal-händelse, alternativt en statisk dag och tid)

  • Ytterligare information gruppen önskar publicera i katalogen

Det är väntat att inte alla grupper kommer ha svar på ovanstående. De skall ges när de finns.

Content may be stored in the 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

Grupper är ansvariga för att se till att deras poster är aktuella.

The DEI, Engineering, and Mindshare representatives to the Fedora Council 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.

Mekanism

Gruppinformationsfiler

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 council-docs repository. See the example template for format and structure.

Visa katalogen

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 council-docs repo. After include-ing the info file, the index page must include the team_render.adoc file that defines the rendering.

Återanvändning av data på gruppsidor

Grupper kan inkludera sin fil NAMN_team_info.adoc på sina sidor, och sedan använda Fedora Council, The Fedora Council is our top-level community leadership and governance body. It is responsible for stewardship of the Fedora Project as a whole, and supports the health and growth of the Fedora community. etc. var som helst på sidan.

Want to help? Learn how to contribute to Fedora Docs ›