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

Meeting summary

1. Agenda (jwf, 15:30:40)
   1. https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next (jwf, 15:30:45)
   2. (1) Roll call / Q&A (jwf, 15:30:46)
   3. (2) Announcements (jwf, 15:30:46)
   4. (3) Action items from last meeting (jwf, 15:30:46)
   5. (4) Tickets (jwf, 15:30:46)
   6. (5) Open floor (jwf, 15:30:47)
   
   
2. Roll call / Q&A (jwf, 15:30:52)
   1. Name; Timezone; Sub-projects/Interest Areas (jwf, 15:30:59)
   2. ACTION: commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] (jwf, 15:30:59)
   3. Justin W. Flory; UTC-5; CommOps, Diversity, Ambassadors (jwf, 15:31:14)
   4. Dennis W. Otugo; UTC+1, CommOps (wesleyotugo, 15:31:50)
   5. Bhagyashree/Bee; UTC+1; Metrics, Diversity, CommOps (bee_, 15:32:32)
   6. Dhanesh B. Sabane, UTC+5:30, CommOps, RPM packaging, Python (dhanesh95, 15:35:31)
   
   
3. Announcements (jwf, 15:36:39)
   1. === Reminder: CommOps FAD next week! === (jwf, 15:36:48)
   2. https://fedoraproject.org/wiki/FAD_CommOps_2018 (jwf, 15:36:48)
   3. Wrapping up on the final week to do any supporting research before we arrive. Attendees, remote and in-person, please double-check your availability is still correct! (jwf, 15:36:48)
   4. === Elections are ongoing - voting ends Wed., Jan. 24 @ 23:59 UTC === (jwf, 15:37:04)
   5. https://admin.fedoraproject.org/voting/ (jwf, 15:37:05)
   6. https://communityblog.fedoraproject.org/tag/january-2018-elections-council/ (jwf, 15:37:12)
   7. https://communityblog.fedoraproject.org/tag/january-2018-elections-fesco/ (jwf, 15:37:12)
   8. https://communityblog.fedoraproject.org/tag/january-2018-elections-mindshare/ (jwf, 15:37:12)
   9. Elections are open for almost two more days. Make sure to get your votes in before the deadline! (jwf, 15:37:18)
   
   
4. Action items from last meeting (jwf, 15:39:14)
   1. https://meetbot.fedoraproject.org/fedora-meeting-2/2018-01-15/commops.2018-01-15-15.29.html (jwf, 15:39:17)
   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:39:21)
   3. === [COMPLETE] "jwf Create a logic model based on the current FAD template" === (jwf, 15:39:30)
   4. https://fedoraproject.org/wiki/File:CommOps_FAD_2018_Logic_Model.png (jwf, 15:39:34)
   5. Logic model is complete: helps demonstrate what we plan to carry out and how it will impact the Fedora community (jwf, 15:39:38)
   6. === [IN PROGRESS] "skamath Add comment to ticket #114 (Grimoire ticket) that estimates a timeline for the Perceval fedmsg plugin development" === (jwf, 15:39:43)
   7. Hacking on the dashboard today. Found potential blocker and will open a ticket on their issue tracker (jwf, 15:39:46)
   8. ACTION: skamath Add comment to ticket #114 (Grimoire ticket) that estimates a timeline for the Perceval fedmsg plugin development (jwf, 15:39:49)
   9. === [COMPLETE] "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:39:54)
   10. https://lists.fedoraproject.org/archives/list/magazine@lists.fedoraproject.org/thread/3A2FE4GFSWRERZPTZQCWG5A6VUNZKMB4/ (jwf, 15:39:58)
   11. Some helpful feedback; ryanlerch may add more, but for now, we'll have independent oversight to where we focus in on the FAD (jwf, 15:40:05)
   12. === [COMPLETE] "skamath Ask GrimoireLab team if they will be attending GSoC this year" === (jwf, 15:40:11)
   13. Emailed, waiting for response by Grimoire team (jwf, 15:40:15)
   14. === [COMPLETE] "jwf Review wesleyotugo's Bodhi Year in Review post, combined with bowlofeggs' feedback, get scheduled!" === (jwf, 15:40:19)
   15. https://communityblog.fedoraproject.org/?p=5073&preview=1&_ppp=3cbb4a624d (jwf, 15:40:22)
   16. Scheduled for Tuesday, Jan. 22 at 08:15 UTC! (jwf, 15:40:26)
   17. === [COMPLETE] "jwf Confirm with Rhea when the meeting room is available, make agenda to go on wiki" === (jwf, 15:40:56)
   18. https://fedoraproject.org/wiki/FAD_CommOps_2018#Schedule (jwf, 15:40:59)
   19. Schedule draft prepared. Please review and share any feedback you may have. (jwf, 15:41:02)
   
   
5. Tickets (jwf, 15:41:33)
   1. https://pagure.io/fedora-commops/issues?tags=meeting (jwf, 15:41:37)
   2. === Ticket #125: "[TRACKER TICKET] Organize a CommOps FAD" === (jwf, 15:41:44)
   3. https://pagure.io/fedora-commops/issue/125 (jwf, 15:41:44)
   4. Final week until FAD – some of us begin traveling this week, so it may be slower from the end of this week until the FAD. (jwf, 15:41:48)
   5. https://fedoraproject.org/wiki/File:CommOps_FAD_2018_Logic_Model.png (jwf, 15:42:58)
   6. https://fedoraproject.org/wiki/FAD_CommOps_2018#Schedule (jwf, 15:43:05)
   7. Schedule re-arranged: GrimoireLabs discussion on Tuesday, elections + fedmsg plugins on Wednesday (jwf, 15:52:27)
   8. ACTION: x3mboy Open new CommOps ticket with expanded idea on improving communication from public to Ambassadors (jwf, 15:58:43)
   9. IDEA: Coming up with a 1-year, high-level plan for CommOps post-FAD (covering ideas we want to include in 2018 but may not be discussed during FAD) (jwf, 16:10:54)
   
   
6. Open floor (jwf, 16:14:25)

Action items

1. commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
2. skamath Add comment to ticket #114 (Grimoire ticket) that estimates a timeline for the Perceval fedmsg plugin development
3. x3mboy Open new CommOps ticket with expanded idea on improving communication from public to Ambassadors

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. x3mboy
   1. x3mboy Open new CommOps ticket with expanded idea on improving communication from public to Ambassadors

People present (lines said)

1. jwf (157)
2. dhanesh95 (33)
3. x3mboy (27)
4. zodbot (16)
5. bee_ (13)
6. bt0_ (12)
7. nauticalnexus[m] (11)
8. bexelbie (3)
9. wesleyotugo (2)
10. commops (0)