Comunicazione e riunioni

Fedora Docs attualmente tiene riunioni settimanali su IRC/Telegram/Matrix. Consulta il calendario della documentazione per gli orari aggiornati delle riunioni e la pagina principale per le informazioni su come partecipare.

Questa pagina descrive la struttura delle riunioni.

Pre-riunione

Gli argomenti da discutere durante le riunioni dovrebbero essere contrassegnati con il Riunione. Durante la preparazione dell’agenda, esaminare il bacheca delle attività per individuare gli elementi che devono essere contrassegnati per la riunione. Almeno uno o due giorni prima della riunione, il coordinatore dovrebbe pubblicare un thread con l’agenda sul forum. I membri del team possono proporre ulteriori argomenti all’interno di questi thread.

Riunione

Follow this general script for the meeting.

#topic Roll call ```

Wait 3–5 minutes to see who is present.

TIP: In case you need to step away or get disconnected, add other chairs (e.g. xref:index.adoc#_the_board[board members]) with: #chair <NICK>

List the agenda for the meeting:

``` #topic Agenda #info Announcements #info Review action items #info <topic 1> #info <topic 2> #info … ```

Start with any important announcements. (e.g. Release Notes that need to be written, upcoming deadlines, a link to the https://gitlab.com/groups/fedora/docs/-/boards[issue board], etc.)

Next, review action items from https://meetbot.fedoraproject.org/sresults/?group_id=docs&type=team[previous meetings]. Get updates when there are updates to get. If an action item is still open, use the `#action` command to assign it again. This keeps chairs from having to search many previous meetings.

``` #topic Previous action items #info <nick> was to <action> ```

Proceed through the other agenda topics. Use `#topic` to change the topic. Make frequent use of `#info` and `#link` commands to add context to the minutes. If someone needs to act, use `#action <nick> to <action>` to note it in the minutes. Note agreements with the `#agreed` command.

TIP: Most of the time, something that is #agreed should be recorded elsewhere after the meeting. For example, in the resolution of a ticket or as a new policy/procedure in the documentation.

NOTE: Should we add a regular content-related topic? https://discussion.fedoraproject.org/t/fedora-and-centos-docs-revitalization/36353/7[Peter Boy suggested this].

If time permits, open the floor for other discussion.

``` #topic Open floor ```

CAUTION: Do not make decisions in the open floor section. Decisions should, at a minimum, be made after appearing on the meeting agenda in advance. In most cases, decisions should happen asynchronously.

When time is up or there are no more topics to discuss, end the meeting.

``` #endmeeting ```

== Post-meeting

Paste the links to the minutes and logs in the Discussion thread you used for the agenda. Note any important outcomes. Update tickets or discussion threads with actions, agreements, etc.