#fedora-commops: Fedora CommOps (2018-12-05)

Meeting summary

1. Agenda (jwf, 17:11:22)
   1. https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next (jwf, 17:11:28)
   2. (1) Roll call / Q&A (jwf, 17:11:28)
   3. (2) Announcements (jwf, 17:11:28)
   4. (3) Action items from last meeting (jwf, 17:11:28)
   5. (4) Tickets (jwf, 17:11:29)
   6. (5) Open floor (jwf, 17:11:30)
   
   
2. Roll call / Q&A (jwf, 17:11:36)
   1. Name; Timezone; Sub-projects/Interest Areas (jwf, 17:11:38)
   2. ACTION: commops New members, please introduce yourself on the CommOps Discourse [ https://discussion.fedoraproject.org/c/project/commops ] (jwf, 17:11:40)
   3. Justin W. Flory; UTC-5; CommOps, D&I Team, Fedora Badges (jwf, 17:12:17)
   4. Alberto Rodriguez S; UTC-6; CommOps, Marketing, dotnet and more (bt0, 17:13:23)
   
   
3. Announcements (jwf, 17:14:31)
   1. === "FPgM report: 2018-48" === (jwf, 17:14:55)
   2. https://communityblog.fedoraproject.org/fpgm-report-2018-48/ (jwf, 17:15:01)
   3. Papa Charlie: GMT CommOps (VibroMax, 17:15:31)
   4. https://pagure.io/fedora-docs/docs-fp-o/issue/104 (bpabon, 17:17:33)
   
   
4. Action items from last meeting (jwf, 17:17:50)
   1. https://pagure.io/fedora-docs/docs-fp-o/issue/104 doesn't get love from the docs folks. (bpabon, 17:18:17)
   2. https://meetbot.fedoraproject.org/fedora-commops/2018-11-28/commops.2018-11-28-17.03.html (jwf, 17:18:39)
   3. 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, 17:18:43)
   4. === [IN PROGRESS] "bt0 Complete a first draft of new CommOps docs page on suggested Pagure tags (due: Monday, Dec. 3rd)" === (jwf, 17:21:00)
   5. Will discuss further during tickets part of meeting! (jwf, 17:21:01)
   6. === [COMPLETE] "bt0 Write a CommBlog draft to link and explain two or three CommOps "easyfix" tasks for Winter 2018 (due: Monday, Dec. 3rd)" === (jwf, 17:21:24)
   7. https://communityblog.fedoraproject.org/?p=6716&preview=1&_ppp=1017420676 (jwf, 17:21:24)
   8. Draft is complete and ready for review. bt0++ (jwf, 17:21:25)
   9. === [INCOMPLETE] "jwf Draft set of user testing scenarios for contributing to docs, create new tickets for each test scenario. Due: Friday, Nov. 30th." === (jwf, 17:22:05)
   10. ACTION: jwf Draft set of user testing scenarios for contributing to docs, create new tickets for each test scenario. Due: before 2019. (jwf, 17:22:17)
   11. === [INCOMPLETE] "jwf Share test scenarios with Design Team to get additional feedback" === (jwf, 17:22:29)
   12. ACTION: jwf Share test scenarios with Design Team to get additional feedback (jwf, 17:22:29)
   13. === [COMPLETE] "bpabon Investigate ways to visualize diagrams from text further and then open new Pagure / docs-fp-o tickets for rendering support" === (jwf, 17:23:22)
   14. https://pagure.io/fedora-docs/docs-fp-o/issue/104 (jwf, 17:23:22)
   15. bpabon opened ticket, but needs additional follow-up from Docs Team members. Will look closer later in meeting too. bpabon++ for leading on this. (jwf, 17:23:22)
   16. === [INCOMPLETE] "jwf Start new Discourse thread about the Dilemma of the Conflicting Meetings" === (jwf, 17:26:06)
   17. ACTION: jwf Start new Discourse thread about the Dilemma of the Conflicting Meetings (jwf, 17:26:06)
   
   
5. Tickets (jwf, 17:26:42)
   1. https://pagure.io/fedora-commops/issues?status=Open&priority=20 (jwf, 17:26:42)
   
   
6. Ticket #159: "Run a "Write the Docs" event targeting Fedora support groups" (jwf, 17:28:43)
   1. https://pagure.io/fedora-commops/issue/159 (jwf, 17:28:43)
   2. meskarune interested in helping with running through the test cases once ready (jwf, 17:29:00)
   3. HELP: bpabon looking for additional feedback from Fedora Docs team members on Discourse thread (jwf, 17:29:17)
   4. https://pagure.io/fedora-docs/docs-fp-o/issue/104 (jwf, 17:30:12)
   5. IDEA: Should CommOps create a list of common tools with descriptions of what they are in our own documentation? (jwf, 17:38:53)
   6. IDEA: What if we created a "Fedora vocabulary sheet" with the buzzwords / jargon / unique vocabulary from across the Fedora community (jwf, 17:39:19)
   7. ACTION: jwf File new tickets to discuss / plan out these ideas further (jwf, 17:41:00)
   8. ACTION: bpabon Create a flowchart based on meeting discussion (around conventions / expectations for filing a CommOps ticket), review at next meeting (jwf, 18:01:56)
   9. HELP: Create an updated list of sub-project contact info (jwf, 18:02:53)
   10. IDEA: Create list of tasks for newbies to do in CommOps (jwf, 18:03:01)
   11. IDEA: New ticket templates for recurring, easy fix tasks (e.g. certain CommBlog articles, fedmsg mini-experiments, etc.) (jwf, 18:04:58)
   12. ACTION: jwf Post Discourse summary / do ticket updates from meeting this week (jwf, 18:07:10)

Action items

1. commops New members, please introduce yourself on the CommOps Discourse [ https://discussion.fedoraproject.org/c/project/commops ]
2. jwf Draft set of user testing scenarios for contributing to docs, create new tickets for each test scenario. Due: before 2019.
3. jwf Share test scenarios with Design Team to get additional feedback
4. jwf Start new Discourse thread about the Dilemma of the Conflicting Meetings
5. jwf File new tickets to discuss / plan out these ideas further
6. bpabon Create a flowchart based on meeting discussion (around conventions / expectations for filing a CommOps ticket), review at next meeting
7. jwf Post Discourse summary / do ticket updates from meeting this week

Action items, by person

1. bpabon
   1. bpabon Create a flowchart based on meeting discussion (around conventions / expectations for filing a CommOps ticket), review at next meeting
2. commops
   1. commops New members, please introduce yourself on the CommOps Discourse [ https://discussion.fedoraproject.org/c/project/commops ]
3. jwf
   1. jwf Draft set of user testing scenarios for contributing to docs, create new tickets for each test scenario. Due: before 2019.
   2. jwf Share test scenarios with Design Team to get additional feedback
   3. jwf Start new Discourse thread about the Dilemma of the Conflicting Meetings
   4. jwf File new tickets to discuss / plan out these ideas further
   5. jwf Post Discourse summary / do ticket updates from meeting this week

People present (lines said)

1. jwf (150)
2. bpabon (47)
3. meskarune (46)
4. zodbot (16)
5. bt0 (15)
6. commops-bot (2)
7. tg-fedcommops (2)
8. VibroMax (2)
9. nb (1)
10. jbjorkang (0)
11. commops (0)