Diretori des scuadris di Fedora

Par podê dâ visibilitât a cualis scuadris a esistin e a son ativis in Fedora, il consei al à decidût di mantignî un diretori che al ricêf controi regolârs. Il rapresentants dal consei a son responsabii pe valutazion periodiche des scuadris sot de lôr aree (diversitât e inclusion, inzegnerie, notorietât e difusion). Si varès di lei "scuadris" tant che tiermin gjeneric pai grups in Fedora che a podaressin clamâsi "Grups di interès speciâl (SIGs)", "Grups di lavôr" o cualsisei altri tiermin simil.

Intindiment

La finalitât dal diretori des scuadris e je chê di rindi visibil: 1. cualis scuadris a son ativis te comunitât e 2. ce mût contatâlis. Fedora e je une grande comunitât cun tantis ativitâts diferentis e il diretori al judarà i membris de comunitât esistents e potenziâi a cjatâ la scuadre che a stan cirint. Vint controi periodics al jude a sei sigûrs che lis informazions a sedin justis e precisis, e che no si mandi la int viers scuadris che no son plui ativis.

La finalitât no je chê di aumentâ la cjame aministrative su scuadris o aumentâ lis dificoltâts par scomençâ une gnove scuadre. L’intindiment nol è chel di dî "se no tu sês in liste no tu puedis jessi une scuadre in Fedora". Dut câs, la presince intal diretori e pues vignî doprade di altris scuadris par valutâ il finanziament o lis richiestis di lavôr (p.e. lavôr sul sît web o risorsis di progjetazion).

Contignût

Lis scuadris e àn di listâ chestis informazions intal formât specificât dal model:

  • Non de scuadre

  • Sintesi scuadre

  • Sît web de scuadre

  • Stât de scuadre (atîf o inatîf)

  • Canâl di comunicazion asincron preferît de scuadre (p.e. mailing list, categorie di forum, e v.i.)

  • Canâl di comunicazion sincron preferît (p.e. Canâl IRC, stanzie Telegram, e v.i.)

  • Segnadôr di problemis de scuadre

  • Riunions de scuadre (miôr un colegament a un event Fedocal, in alternative une date e ore statiche)

  • Informazions adizionâls che la scuadre e desidere publicâ tal diretori

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 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.

Mechanism

Team information files

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.

Rendering the directory

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.

Reusing the data on team pages

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.