Directorio de Equipos de Fedora

Para proporcionar visibilidad a qu茅 equipos existen y est谩n activos en Fedora, el Fedora Council decidi贸 mantener un directorio que recibe comprobaciones regulares. Los representantes del Fedora Council son los responsables de una evaluaci贸n peri贸dica de los equipos de su 谩rea (DEI, Ingenier铆a y Conocimiento de Marca). "Equipos" debe leerse como un t茅rmino general para los grupos en Fedora que pueden llamarse "Grupos de Inter茅s Especial (SIGs)", "Grupos de Trabajo (WGs)" o cualquier otro t茅rmino similar.

Intenci贸n

El directorio del equipo tiene como objetivo hacer visible:

  1. Qu茅 equipos est谩n activos en la comunidad.

  2. C贸mo contactarlos.

Fedora es una gran comunidad con muchas actividades diferentes y el directorio ayudar谩 a los miembros de la comunidad existentes y potenciales a encontrar el equipo que est谩n buscando. Tener comprobaciones peri贸dicas ayuda a asegurar que la informaci贸n es preisa y que no dirigimos a la gente hacia equipos que no est谩n activos.

La intenci贸n es no aumentar la carga administrativa sobre los equipos o las barreras para crear un equipo. La intenci贸n no es decir "si no est谩s en la lista, no tiene permitido ser un equipo en Fedora". Sin embargo, la presencia en el directorio puede ser usada por otros equipos para evaluar solicitudes de financiaci贸n o trabajo (por ejemplo, trabajo de sitio web o activos de dise帽o).

Content

Teams should list the following information in the format specified by the 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 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 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.

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 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. anywhere on the page.