commops
MINUTES

#fedora-meeting-2: Fedora CommOps (2017-10-30)

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

Meeting summary

  1. Agenda (jwf, 14:29:22)
    1. https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next (jwf, 14:29:30)
    2. (1) Roll call / Q&A (jwf, 14:29:37)
    3. (2) Announcements (jwf, 14:29:42)
    4. (3) Action items from last meeting (jwf, 14:29:46)
    5. (4) Tickets (jwf, 14:29:52)
    6. (5) Open floor (jwf, 14:29:56)

  2. Roll call / Q&A (jwf, 14:30:01)
    1. Name; Timezone; Sub-projects/Interest Areas (jwf, 14:30:07)
    2. ACTION: commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] (jwf, 14:30:12)
    3. Justin W. Flory; UTC-5; CommOps, Diversity, badges-sysadmin, Ambassador (jwf, 14:30:48)

  3. Announcements (jwf, 14:36:28)
    1. === "Fedora Classroom Session: Fedora QA 101" === (jwf, 14:36:34)
    2. https://fedoramagazine.org/fedora-classroom-session-fedora-qa-101/ (jwf, 14:36:38)
    3. sumantrom leads a Fedora Classroom for Fedora QA on November 7th, 15:00 UTC. Learn how to get started with Fedora QA and help test new releases of Fedora. (jwf, 14:36:46)
    4. === "What I have found interesting in Fedora during the week 43 of 2017" === (jwf, 14:36:52)
    5. https://communityblog.fedoraproject.org/found-interesting-fedora-week-43-2017/ (jwf, 14:36:56)
    6. Fedora 27 no-go, Mindshare, and Autumn Elections (jwf, 14:37:00)
    7. === "Teaching metrics and contributor docs at Flock 2017" === (jwf, 14:37:06)
    8. https://communityblog.fedoraproject.org/metrics-docs-flock-2017/ (jwf, 14:37:10)
    9. Quick overview over what CommOps covered at their work session at Flock 2017. (jwf, 14:37:15)

  4. Action items from last meeting (jwf, 14:40:07)
    1. https://meetbot.fedoraproject.org/teams/commops/commops.2017-10-16-14.31.html (jwf, 14:40:14)
    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, 14:40:22)
    3. === [IN PROGRESS] jwf Follow up with sayan about Fedora Badges related to Fedora Infrastructure (i.e. fedora-badges #434, #441, #442); update Infrastructure on-boarding ticket once new info is available (DUE: 2017-10-23) === (jwf, 14:40:31)
    4. Comments left in ticket, but need follow-up; re-actioning to keep on agenda (jwf, 14:40:38)
    5. ACTION: jwf Follow up with sayan about Fedora Badges related to Fedora Infrastructure (i.e. fedora-badges #434, #441, #442); update Infrastructure on-boarding ticket once new info is available (jwf, 14:40:43)
    6. === [IN PROGRESS] bt0 work on Issue #48 and break the information into smaller actions for Marketing team, file tickets and/or contact Marketing team about it. === (jwf, 14:40:49)
    7. https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/ML53D7YORTQMUS3D55QNP6DCSPETMUP6/ (jwf, 14:40:56)
    8. ACTION: bt0 work on Issue #48 and break the information into smaller actions for Marketing team, file tickets and/or contact Marketing team about it (jwf, 14:41:02)
    9. === [COMPLETE] jwf File a new ticket against Fedora Hubs with research on Marketing team for designing the Marketing Hub later on === (jwf, 14:41:08)
    10. https://pagure.io/fedora-hubs/issue/404 (jwf, 14:41:13)
    11. === [INCOMPLETE] bee2502 open a new ticket for F27 Release party badge. === (jwf, 14:41:20)
    12. ACTION: bee2502 open a new ticket for F27 Release party badge (jwf, 14:41:25)
    13. === [COMPLETE] bee2502 open a new ticket to gather tickets, information CommOps wants to port to Fedora Docs. Add a link to ticket 102 === (jwf, 14:41:32)
    14. https://pagure.io/fedora-commops/issue/118 (jwf, 14:41:37)
    15. === [INCOMPLETE] jwf Initialize the Asciidoc environment in the Fedora CommOps repo === (jwf, 14:41:45)
    16. https://pagure.io/fedora-commops/issue/123 (jwf, 14:41:50)
    17. ACTION: bexelbie Initialize the Asciidoc environment in the Fedora CommOps repo (jwf, 14:46:39)
    18. === [COMPLETE] bt0 start an email thread linking ticket 103 that we need feedback on voting badge and AMA idea or any more ideas === (jwf, 14:46:54)
    19. https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/KGETPOLZV7ILSJD7EDYXNBBGJJXFLWSN/ (jwf, 14:46:59)
    20. === [COMPLETE] bt0 send bi-weekly reminders for pending CommBlog posts on mailing list and IRC === (jwf, 14:47:04)
    21. https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/ML53D7YORTQMUS3D55QNP6DCSPETMUP6/ (jwf, 14:47:10)
    22. === [COMPLETE] bee2502 open new ticket where we can discuss how we can actions/suggestions for making CommBlog better. === (jwf, 14:47:16)
    23. https://pagure.io/fedora-commops/issue/119 (jwf, 14:47:21)

  5. Tickets (jwf, 14:47:37)
    1. https://pagure.io/fedora-commops/issues?tags=meeting (jwf, 14:47:40)
    2. === Ticket #103: "Improving Fedora Elections Process: Improving Voter Participation" === (jwf, 14:47:44)
    3. https://pagure.io/fedora-commops/issue/103 (jwf, 14:47:48)
    4. https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/KGETPOLZV7ILSJD7EDYXNBBGJJXFLWSN/ (jwf, 14:49:16)
    5. HELP: Badge for voting requires changes to Elections app (to let someone click a link after voting or click a box to receive badge after voting): https://pagure.io/elections (jwf, 14:52:12)
    6. ACTION: skamath file a RFE ticket against the Elections app for badge support (skamath, 14:55:27)
    7. skamath going to spend some time development time to improve the Elections app and try to implement some of the RFEs filed against project; will check in on development progress on 2017-11-20 meeting (jwf, 14:56:53)
    8. Too late to have AMAs for this election cycle, but we can revisit next election (start planning in spring) (jwf, 14:57:56)
    9. AGREED: Will follow up again on this ticket on 2017-11-20 (jwf, 14:58:45)
    10. === Ticket #107: "Automated Fedocal reminders to send to all mailing lists for upcoming Elections" === (jwf, 14:59:08)
    11. https://pagure.io/fedora-commops/issue/107 (jwf, 14:59:13)
    12. ACTION: x3mboy Set up Fedocal events for the upcoming F27 election cycle, set up automatic reminders for mailing lists mentioned in ticket #107 (due:2017-11-06) (jwf, 15:02:39)
    13. AGREED: Ticket can be closed once Fedocal events are set up (jwf, 15:03:29)
    14. === Ticket #114: "Use GrimoireLab tools to centralize metrics" === (jwf, 15:09:45)
    15. https://pagure.io/fedora-commops/issue/114 (jwf, 15:09:50)
    16. https://communityblog.fedoraproject.org/metrics-docs-flock-2017/#comment-5756 (jwf, 15:11:30)
    17. We received feedback in our CommBlog Flock 2017 article about Grimoire Labs and a recommendation to consider other projects that offer better long-term viability. (jwf, 15:13:38)
    18. Other alternatives to Grimoire Labs could be Grafana, Chronograf, and plenty of other types of dashboard / metric visualization suites… (jwf, 15:14:08)
    19. https://www.linuxfoundation.org/blog/chaoss-project-creates-tools-to-analyze-software-development-and-measure-open-source-community-health/ (jwf, 15:14:44)
    20. fedmsg stores metrics / data in PostgreSQL database (jwf, 15:16:53)
    21. https://github.com/fedora-infra/datanommer (skamath, 15:16:57)
    22. ACTION: skamath Add comment to ticket #114 about possible blocker with Grimoire / Kibiter (jwf, 15:21:21)
    23. ACTION: jwf Research and compare pros / cons between Grafana and Grimoire Labs, add overview comparison to ticket #114 (jwf, 15:21:50)
    24. === Ticket #117: "How-to create Onboading guidelines for your team" === (jwf, 15:24:32)
    25. https://pagure.io/fedora-commops/issue/117 (jwf, 15:24:36)
    26. https://pagure.io/fedora-contribution-howto (jwf, 15:25:15)
    27. Next best step for this ticket is to get our own docs published and created, then we can try to document the process for helping other sub-projects and teams do this too; jwf is already working on this in other tickets, so ticket dependency metadata will be updated and will be removed from meeting agenda (jwf, 15:27:53)
    28. AGREED: Will follow up with this ticket after #114 ("Porting CommOps Information to Fedora Docs") is closed (jwf, 15:33:58)
    29. === Ticket #120: "Elect a CommOps Mindshare representative" === (jwf, 15:34:21)
    30. https://pagure.io/fedora-commops/issue/120 (jwf, 15:34:25)
    31. ACTION: jwf Outline CommOps Mindshare seat nomination process in ticket #120 (jwf, 15:40:49)
    32. ACTION: jwf Review inactive CommOps FAS group members, send personalized emails to inactive accounts, remove from FAS group (jwf, 15:41:11)
    33. === Ticket #125: "[TRACKER TICKET] Organize a CommOps FAD" === (jwf, 15:42:01)
    34. https://pagure.io/fedora-commops/issue/125 (jwf, 15:42:05)
    35. HELP: Need to begin highlighting long-term tickets / major tasks for FAD, figuring out what "pre-work" needs to be accomplished for a FAD, put together a proposal to fit into this fiscal year, before 2017 March 1 (jwf, 15:45:27)

  6. Open floor (jwf, 15:46:26)


Meeting ended at 15:48:17 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 Follow up with sayan about Fedora Badges related to Fedora Infrastructure (i.e. fedora-badges #434, #441, #442); update Infrastructure on-boarding ticket once new info is available
  3. bt0 work on Issue #48 and break the information into smaller actions for Marketing team, file tickets and/or contact Marketing team about it
  4. bee2502 open a new ticket for F27 Release party badge
  5. bexelbie Initialize the Asciidoc environment in the Fedora CommOps repo
  6. skamath file a RFE ticket against the Elections app for badge support
  7. x3mboy Set up Fedocal events for the upcoming F27 election cycle, set up automatic reminders for mailing lists mentioned in ticket #107 (due:2017-11-06)
  8. skamath Add comment to ticket #114 about possible blocker with Grimoire / Kibiter
  9. jwf Research and compare pros / cons between Grafana and Grimoire Labs, add overview comparison to ticket #114
  10. jwf Outline CommOps Mindshare seat nomination process in ticket #120
  11. jwf Review inactive CommOps FAS group members, send personalized emails to inactive accounts, remove from FAS group


Action items, by person

  1. bexelbie
    1. bexelbie Initialize the Asciidoc environment in the Fedora CommOps repo
  2. commops
    1. commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
  3. jwf
    1. jwf Follow up with sayan about Fedora Badges related to Fedora Infrastructure (i.e. fedora-badges #434, #441, #442); update Infrastructure on-boarding ticket once new info is available
    2. jwf Research and compare pros / cons between Grafana and Grimoire Labs, add overview comparison to ticket #114
    3. jwf Outline CommOps Mindshare seat nomination process in ticket #120
    4. jwf Review inactive CommOps FAS group members, send personalized emails to inactive accounts, remove from FAS group
  4. skamath
    1. skamath file a RFE ticket against the Elections app for badge support
    2. skamath Add comment to ticket #114 about possible blocker with Grimoire / Kibiter
  5. x3mboy
    1. x3mboy Set up Fedocal events for the upcoming F27 election cycle, set up automatic reminders for mailing lists mentioned in ticket #107 (due:2017-11-06)
  6. UNASSIGNED
    1. bt0 work on Issue #48 and break the information into smaller actions for Marketing team, file tickets and/or contact Marketing team about it
    2. bee2502 open a new ticket for F27 Release party badge


People present (lines said)

  1. jwf (213)
  2. skamath (51)
  3. bexelbie (40)
  4. zodbot (12)
  5. x3mboy (12)
  6. commops (0)


Generated by MeetBot 0.1.4.
Meetbot Logs © 2021-2022 Fedora Websites and Apps Team (Sources)