commops
MINUTES

#fedora-meeting-2: Fedora CommOps (2017-12-04)

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

Meeting summary

  1. Agenda (jwf, 15:29:27)
    1. https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next (jwf, 15:29:32)
    2. (1) Roll call / Q&A (jwf, 15:29:33)
    3. (2) Announcements (jwf, 15:29:33)
    4. (3) Action items from last meeting (jwf, 15:29:33)
    5. (4) Tickets (jwf, 15:29:33)
    6. (5) Open floor (jwf, 15:29:38)

  2. Roll call / Q&A (jwf, 15:29:42)
    1. Name; Timezone; Sub-projects/Interest Areas (jwf, 15:29:46)
    2. ACTION: commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] (jwf, 15:29:46)
    3. Justin W. Flory; UTC-5; CommOps, Diversity, Ambassador, sysadmin-badges (jwf, 15:30:00)
    4. Alberto Rodriguez S; UTC-6;CommOps (Metrics, Community engagement), DotNet (Testing), Infrastructure(Apprentice), Markerting (bt0, 15:30:05)
    5. Rhea the Bunny; UTC+1; CommOps, Diversity, Ambassador and all things C#/.NET (Rhea, 15:30:39)

  3. Announcements (jwf, 15:36:23)
    1. === Last day for election nominations === (jwf, 15:36:28)
    2. https://communityblog.fedoraproject.org/autumn-elections-2017/ (jwf, 15:36:32)
    3. Election nominations end on Dec. 4, 2017 at 23:59 UTC. If you have any nominations to make, be sure to get them in for the Council, FESCo, or Mindshare Committees now! (jwf, 15:36:36)
    4. https://fedoraproject.org/wiki/Council/Nominations (jwf, 15:36:41)
    5. https://fedoraproject.org/wiki/Mindshare/Nominations (jwf, 15:36:44)
    6. https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations (jwf, 15:36:47)
    7. === "Fedora 27 Atomic Offers Multi-Arch Support, Workstation, Containerized Kubernetes, and More" === (jwf, 15:37:20)
    8. https://fedoramagazine.org/fedora-27-atomic-offering/ (jwf, 15:37:23)
    9. New features from the Fedora 27 Atomuc Host. Helpful if you want a quick overview to what's new and happening in the Fedora Atomic world. (jwf, 15:37:27)
    10. === "LISA17 Event Report" === (jwf, 15:37:33)
    11. https://communityblog.fedoraproject.org/lisa17-event-report/ (jwf, 15:37:37)
    12. nb, codeblock, bethlynn, and quaid attended the 2017 edition of LISA. Learn more in the event report on the Community Blog. (jwf, 15:37:43)

  4. Action items from last meeting (jwf, 15:39:26)
    1. https://meetbot.fedoraproject.org/fedora-meeting-2/2017-11-27/commops.2017-11-27-15.31.html (jwf, 15:39:32)
    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:33)
    3. === [COMPLETE] "jwf Follow up with Pingou about an old patch to support Fedora Badges with Pagure commits" === (jwf, 15:39:44)
    4. https://pagure.io/fedora-badges/pull-request/579 (jwf, 15:39:44)
    5. === [POSTPONED] "jwf Document process in upcoming internal docs writing" === (jwf, 15:40:44)
    6. Won't have the bandwidth to actively tackle docs efforts until after FAD planning is finished (jwf, 15:40:44)
    7. === [IN PROGRESS] "jwf With FAD proposal, create a proposal draft and logic model flowchart, create new sub-tasks to divide and conquer FAD planning" === (jwf, 15:41:30)
    8. ACTION: jwf With FAD proposal, create a proposal draft and logic model flowchart, create new sub-tasks to divide and conquer FAD planning (jwf, 15:41:30)

  5. Tickets (jwf, 15:42:26)
    1. https://pagure.io/fedora-commops/issues?tags=meeting (jwf, 15:42:29)
    2. === Ticket #114: "Use metrics dashboard to visualize fedmsg data" === (jwf, 15:42:33)
    3. https://pagure.io/fedora-commops/issue/114 (jwf, 15:42:36)
    4. Last week, we brainstormed ideas for questions to answer and made a final decision on Grimoire Labs. Next steps are installing Grimoire into the CommOps cloud and figuring out the fedmsg plugin for Perceval. (jwf, 15:42:45)
    5. The CommOps cloud machine is now upgraded to F27. Plan is to install Grimoire on our cloud machine to use as a playground and test environment for the Perceval fedmsg plugin. (jwf, 15:47:46)
    6. HELP: A timeline to understand the work on the Perceval plugin is helpful, so we can make accurate estimates for how much work is required and roughly how long it will take (jwf, 15:48:10)
    7. ACTION: skamath Add comment to ticket #114 (Grimoire ticket) that estimates a timeline for the Perceval fedmsg plugin development. What is required? About how much work is involved? Do you foresee any possible blockers? (jwf, 15:49:16)
    8. === Ticket #120: "Elect a CommOps Mindshare representative" === (jwf, 15:51:05)
    9. https://pagure.io/fedora-commops/issue/120 (jwf, 15:51:09)
    10. Two weeks passed since the nomination opened. We agreed to finalize the seat in this meeting. As of now, jwf is the only candidate. This ticket will be closed and the seat will be confirmed with robyduck. (jwf, 15:51:18)
    11. === Ticket #125: "[TRACKER TICKET] Organize a CommOps FAD" === (jwf, 15:54:00)
    12. https://pagure.io/fedora-commops/issue/125 (jwf, 15:54:01)
    13. Rhea booked a room from Sunday, Jan. 28 to Wednesday, Jan. 31 in the Red Hat Brno office to help ensure we get a room (since they're in high demand). Our space is guaranteed for Brno. (jwf, 15:58:14)
    14. The logic model flowchart is due by end of day today (at hack session) (jwf, 15:58:38)
    15. https://pagure.io/fedora-commops/issue/125#comment-481645 (Rhea, 15:59:59)
    16. ACTION: Rhea Create the wiki page for the CommOps FAD, using the 2017 Diversity FAD page as a base (jwf, 16:06:21)
    17. ACTION: jwf Reach out to CommOps members and confirm participants, add to wiki page (jwf, 16:06:38)
    18. ACTION: Rhea Research hotel costs in Brno for the duration of the FAD (preferably near DevConf venue, but not required) (jwf, 16:07:03)

  6. Open floor (jwf, 16:14:21)
    1. ACTION: bt0 For 50% of all drafts in CommBlog, reach out to authors and confirm if they want their articles published or discarded (due: 2017-12-11) (jwf, 16:22:03)


Meeting ended at 16:24:00 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 With FAD proposal, create a proposal draft and logic model flowchart, create new sub-tasks to divide and conquer FAD planning
  3. skamath Add comment to ticket #114 (Grimoire ticket) that estimates a timeline for the Perceval fedmsg plugin development. What is required? About how much work is involved? Do you foresee any possible blockers?
  4. Rhea Create the wiki page for the CommOps FAD, using the 2017 Diversity FAD page as a base
  5. jwf Reach out to CommOps members and confirm participants, add to wiki page
  6. Rhea Research hotel costs in Brno for the duration of the FAD (preferably near DevConf venue, but not required)
  7. bt0 For 50% of all drafts in CommBlog, reach out to authors and confirm if they want their articles published or discarded (due: 2017-12-11)


Action items, by person

  1. bt0
    1. bt0 For 50% of all drafts in CommBlog, reach out to authors and confirm if they want their articles published or discarded (due: 2017-12-11)
  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 With FAD proposal, create a proposal draft and logic model flowchart, create new sub-tasks to divide and conquer FAD planning
    2. jwf Reach out to CommOps members and confirm participants, add to wiki page
  4. Rhea
    1. Rhea Create the wiki page for the CommOps FAD, using the 2017 Diversity FAD page as a base
    2. Rhea Research hotel costs in Brno for the duration of the FAD (preferably near DevConf venue, but not required)
  5. skamath
    1. skamath Add comment to ticket #114 (Grimoire ticket) that estimates a timeline for the Perceval fedmsg plugin development. What is required? About how much work is involved? Do you foresee any possible blockers?


People present (lines said)

  1. jwf (160)
  2. Rhea (33)
  3. bt0 (18)
  4. zodbot (13)
  5. skamath (3)
  6. commops (0)


Generated by MeetBot 0.1.4.