#fedora-meeting-2: Fedora CommOps (2018-01-15)

Meeting started by jwf at 15:29:19 UTC (full logs).

Meeting summary

  1. Agenda (jwf, 15:29:25)
    1. https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next (jwf, 15:29:34)
    2. (1) Roll call / Q&A (jwf, 15:29:35)
    3. (2) Announcements (jwf, 15:29:37)
    4. (3) Action items from last meeting (jwf, 15:29:39)
    5. (4) Tickets (jwf, 15:29:41)
    6. (5) Open floor (jwf, 15:29:43)

  2. Roll call / Q&A (jwf, 15:29:45)
    1. Name; Timezone; Sub-projects/Interest Areas (jwf, 15:29:47)
    2. ACTION: commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] (jwf, 15:29:51)
    3. Justin W. Flory; UTC-5 (for now); CommOps, Diversity, Ambassadors (jwf, 15:30:18)
    4. Sachin S. Kamath; UTC +5.30; CommOps, SoC, Join, Classroom, * (skamath, 15:30:18)
    5. Alberto Rodríguez; UTC-5; CommOps, marketing, Ambassador, dotnet sig (bt0_, 15:30:58)

  3. Announcements (jwf, 15:37:00)
    1. === "10 Fedora Women Days across the world" === (jwf, 15:37:04)
    2. https://communityblog.fedoraproject.org/fedora-women-days-2017/ (jwf, 15:37:08)
    3. jonatoni summarizes the ten Fedora Women Day events around the world in 2017. Read more in her article covering what the Diversity Team was up to last year! (jwf, 15:37:12)
    4. === "An update on ongoing Meltdown and Spectre work" === (jwf, 15:37:22)
    5. https://fedoramagazine.org/update-ongoing-meltdown-spectre-work/ (jwf, 15:37:26)
    6. labbott continues coverage of the Meltdown / Spectre vulnerability fixes in Fedora. Helpful summary if you're having a hard time keeping up with all the news! (jwf, 15:37:33)
    7. === Two weeks until CommOps FAD (Jan. 29-31, 2018) === (jwf, 15:37:43)
    8. https://fedoraproject.org/wiki/FAD_CommOps_2018 (jwf, 15:37:49)
    9. The CommOps FAD is on approach this month. Most of the activity in the next two weeks will likely be in support of the FAD! (jwf, 15:37:49)

  4. Action items from last meeting (jwf, 15:41:19)
    1. https://meetbot.fedoraproject.org/fedora-meeting-1/2017-12-18/commops.2017-12-18-15.30.html (jwf, 15:41:24)
    2. 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 if needed. If no status, we'll try to get a quick update and move forward. (jwf, 15:41:24)
    3. === [INCOMPLETE] "jwf Create a logic model based on the current FAD template" === (jwf, 15:41:41)
    4. This fell off during the holidays, but jwf is planning to complete by 2017-01-21 (jwf, 15:41:45)
    5. ACTION: jwf Create a logic model based on the current FAD template (jwf, 15:41:49)
    6. === [INCOMPLETE] "skamath Add comment to ticket #114 (Grimoire ticket) that estimates a timeline for the Perceval fedmsg plugin development" === (jwf, 15:42:41)
    7. ACTION: skamath Add comment to ticket #114 (Grimoire ticket) that estimates a timeline for the Perceval fedmsg plugin development (jwf, 15:42:44)
    8. === [] "dhanesh95 Reach out to Fedora Magazine team to get feedback on helpful data to incorporate into fedmsg via WordPress's REST API (note limitations of REST API too – what's helpful for what we can extract?)" === (jwf, 15:42:54)
    9. ACTION: dhanesh95 Reach out to Fedora Magazine team to get feedback on helpful data to incorporate into fedmsg via WordPress's REST API (note limitations of REST API too – what's helpful for what we can extract?) (jwf, 15:44:16)
    10. === [COMPLETE] "meskarune Open new ticket in Fedora CommOps Pagure for our Year in Review, and a ticket in Fedora Diversity Pagure for Year in Review" === (jwf, 15:44:59)
    11. https://pagure.io/fedora-commops/issue/130 (jwf, 15:44:59)
    12. https://pagure.io/fedora-diversity/issue/49 (jwf, 15:45:00)

  5. Tickets - Active (jwf, 15:45:33)
    1. https://pagure.io/fedora-commops/issues?tags=meeting (jwf, 15:45:38)
    2. === Ticket #125: "[TRACKER TICKET] Organize a CommOps FAD" === (jwf, 15:45:46)
    3. https://pagure.io/fedora-commops/issue/125 (jwf, 15:45:46)
    4. https://fedoraproject.org/wiki/FAD_CommOps_2018 (jwf, 15:45:46)
    5. ACTION: skamath Ask GrimoireLab team if they will be attending GSoC this year (skamath, 15:49:11)
    6. https://pagure.io/fedora-commops/issues?tags=meeting (meskarune, 15:50:55)
    7. https://fedoraproject.org/wiki/FAD_CommOps_2018 (skamath, 15:52:17)

  6. Tickets - Open (jwf, 15:54:40)
    1. A special section to the meeting agenda! This section is for tickets that are open and need help. If you're looking to work on something or get started, look at these and feel free to ask questions now! (jwf, 15:54:45)
    2. === Ticket #96: "Community blog post explaining how to use the easyfix tag to get tickets to show up on the easyfix list" === (jwf, 15:54:53)
    3. https://pagure.io/fedora-commops/issue/96 (jwf, 15:54:53)
    4. https://fedoraproject.org/easyfix/ (jwf, 15:54:53)
    5. The easyfix page highlights good "starter" bugs or tasks in various projects across Fedora. But it's not obvious how to get your bugs listed there! You have to add your project to a wiki page in a specific format. We need someone to share how to do this. (jwf, 15:55:06)
    6. https://fedoraproject.org/wiki/Easyfix (jwf, 15:55:06)
    7. === Ticket #127: "Write a "How to" commblog post to explain a little bit the changes in the wiki" === (jwf, 15:57:29)
    8. https://pagure.io/fedora-commops/issue/127 (jwf, 15:57:29)
    9. The wiki got a lot of love in December. There's new features or ways of doing things that need to be documented. This ticket involves some research about the changes, and then writing a short informative article about the changes. Bonus points for writing a doc! (jwf, 15:57:37)
    10. === Ticket #128: "Create Pagure pull request how-to documentation" === (jwf, 15:57:52)
    11. https://pagure.io/fedora-commops/issue/128 (jwf, 15:57:52)
    12. Making a pull request may sound obvious, but to many people, it's not. This ticket helps explain how to make a Pagure pull request. This helps many teams in Fedora. It should be in the form of a Fedora doc. We can help you get started! (jwf, 15:57:58)

  7. Open floor (jwf, 16:11:43)
    1. ACTION: jwf Review wesleyotugo's Bodhi Year in Review post, combined with bowlofeggs' feedback, get scheduled! (jwf, 16:11:47)
    2. ACTION: jwf Confirm with Rhea when the meeting room is available, make agenda to go on wiki (jwf, 16:17:04)


Meeting ended at 16:17:34 UTC (full logs).

Action items

  1. commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
  2. jwf Create a logic model based on the current FAD template
  3. skamath Add comment to ticket #114 (Grimoire ticket) that estimates a timeline for the Perceval fedmsg plugin development
  4. dhanesh95 Reach out to Fedora Magazine team to get feedback on helpful data to incorporate into fedmsg via WordPress's REST API (note limitations of REST API too – what's helpful for what we can extract?)
  5. skamath Ask GrimoireLab team if they will be attending GSoC this year
  6. jwf Review wesleyotugo's Bodhi Year in Review post, combined with bowlofeggs' feedback, get scheduled!
  7. jwf Confirm with Rhea when the meeting room is available, make agenda to go on wiki


Action items, by person

  1. commops
    1. commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
  2. dhanesh95
    1. dhanesh95 Reach out to Fedora Magazine team to get feedback on helpful data to incorporate into fedmsg via WordPress's REST API (note limitations of REST API too – what's helpful for what we can extract?)
  3. jwf
    1. jwf Create a logic model based on the current FAD template
    2. jwf Review wesleyotugo's Bodhi Year in Review post, combined with bowlofeggs' feedback, get scheduled!
    3. jwf Confirm with Rhea when the meeting room is available, make agenda to go on wiki
  4. Rhea
    1. jwf Confirm with Rhea when the meeting room is available, make agenda to go on wiki
  5. skamath
    1. skamath Add comment to ticket #114 (Grimoire ticket) that estimates a timeline for the Perceval fedmsg plugin development
    2. skamath Ask GrimoireLab team if they will be attending GSoC this year
  6. wesleyotugo
    1. jwf Review wesleyotugo's Bodhi Year in Review post, combined with bowlofeggs' feedback, get scheduled!


People present (lines said)

  1. jwf (142)
  2. skamath (44)
  3. nauticalnexus[m] (30)
  4. dhanesh95 (19)
  5. zodbot (15)
  6. meskarune (14)
  7. wesleyotugo (4)
  8. bt0_ (2)
  9. bt0__ (2)
  10. DiscordBridge (1)
  11. jonatoni|m (1)
  12. bt0 (0)
  13. Rhea (0)
  14. commops (0)


Generated by MeetBot 0.1.4.