From Fedora Project Wiki

No edit summary
No edit summary
Line 17: Line 17:
** #info (1) Roll call / Q&A
** #info (1) Roll call / Q&A
** #info (2) Announcements
** #info (2) Announcements
** #info (3) Action items from last meeting
** #info (3) Tickets
** #info (4) Tickets
** #info (4) Open floor
** #info (5) Open floor





Revision as of 14:51, 22 August 2017

Fedora CommOps Team Meeting Minutes 2017-08-22

Meeting Time

Participants

This week's CommOps Meeting will be led by bt0dotninja.

  • The participants will be posted after the meeting.

Meeting Protocol

  • To help improve the flow of the meeting, using the IRC Meeting Protocol is encouraged, as modeled by the EMEA Ambassadors.
  • Please follow the Meeting Protocol where possible.

Agenda

CommOpsers, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora CommOps (2017-08-22)
  • #meetingname commops
  • #nick commops
  • #chair <given to approved members of FAS group at meeting>



  • #topic Roll call / Q&A
    • #info Name; Timezone; Sub-projects/Interest Areas
    • #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
    • If this is your first time at a CommOps meeting, feel free to introduce yourself to everyone and say hello! If anyone has any questions before we get started with the rest of the agenda, now is also a good time to ask.


  • #topic Announcements



  • #topic Action items from last meeting
    • #link https://meetbot.fedoraproject.org/teams/commops/commops.2017-08-15-16.39.log.html
    • #info How This Works: We look at past #action items from the last meeting for quick follow-up. If a task is completed, we move on to the next one. If it isn't, we get an update and re-action it if needed. If no status, we'll try to get a quick update and move forward.
    • #info === [IN PROGRESS] skamath Post weekly updates about GrimoireLabs on Planet ===
    • #info === [IN PROGRESS] skamath triage all open metrics tickets and figure out if it can fit into #114 ===
    • #info === [IN PROGRESS] x3mboy Add survey responses to the issue and tag it for next meeting ===



  • #topic Open floor

Meeting summary and action items

Full meeting log

Next Meeting