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

Meeting started by jwf at 17:00:45 UTC (full logs).

Meeting summary

  1. Agenda (jwf, 17:00:50)
    1. https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next (jwf, 17:00:55)
    2. (1) Roll call / Q&A (jwf, 17:01:00)
    3. (2) Announcements (jwf, 17:01:01)
    4. (3) Action items from last meeting (jwf, 17:01:01)
    5. (4) Tickets (jwf, 17:01:01)
    6. (5) Open floor (jwf, 17:01:01)

  2. Roll call / Q&A (jwf, 17:01:07)
    1. Name; Timezone; Sub-projects/Interest Areas (jwf, 17:01:12)
    2. ACTION: commops New members, please introduce yourself on the CommOps Discourse [ https://discussion.fedoraproject.org/c/project/commops ] (jwf, 17:01:12)
    3. Justin W. Flory; UTC-5; CommOps, Diversity and Inclusion Team, Fedora Badges (jwf, 17:01:28)
    4. Alberto Rodriguez S; UTC-6;CommOps, Marketing, Fedora-join, dotnet and more (bt0, 17:02:27)
    5. John M. Harris, Jr.; UTC-5; CommOps (member), Games (member), 3D Printing (member) (JohnMH, 17:05:54)

  3. Announcements (jwf, 17:05:59)
    1. === Fedora Elections in progress - voting closes Thu, Dec. 20 === (jwf, 17:06:09)
    2. https://admin.fedoraproject.org/voting/ (jwf, 17:06:09)
    3. Find candidate interviews on the Community Blog or linked from the voting app. Be sure to get your votes in before the polls close on Thursday, Dec. 20th. (jwf, 17:06:09)
    4. === "Fedora's Strategic Direction: An Update from the Council" === (jwf, 17:06:24)
    5. https://communityblog.fedoraproject.org/fedoras-strategic-direction-an-update-from-the-council/ (jwf, 17:06:24)
    6. mattdm shares a vision of the future, as discussed last week at the Fedora Council hackfest. The Council is looking for feedback on the proposal. (jwf, 17:06:24)
    7. === "FPgM report: 2018-49" === (jwf, 17:06:38)
    8. https://communityblog.fedoraproject.org/fpgm-report-2018-49/ (jwf, 17:06:38)
    9. You didn't even have to guess – bcotton has the inside scoop of Fedora development in this week's report. Note the major Red Hat Bugzilla upgrade and the cassandra package maintainers looking for help. (jwf, 17:06:38)

  4. Action items from last meeting (jwf, 17:09:00)
    1. https://discussion.fedoraproject.org/t/2018-12-04-docs-contributability-tests-and-brainstorming-on-on-boarding/778 (jwf, 17:09:07)
    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, 17:09:07)
    3. === [INCOMPLETE] "jwf Draft set of user testing scenarios for contributing to docs, create new tickets for each test scenario. Due: before 2019." === (jwf, 17:09:19)
    4. ACTION: jwf Draft set of user testing scenarios for contributing to docs, create new tickets for each test scenario, ask for Design Team feedback. Due: before 2019 (jwf, 17:09:25)
    5. Note: Another action item to request Design Team feedback is part of the required follow-up for this to be complete. It is now included in this action item. (jwf, 17:09:25)
    6. === [COMPLETE] "jwf Start new Discourse thread about the Dilemma of the Conflicting Meetings" === (jwf, 17:09:31)
    7. https://discussion.fedoraproject.org/t/new-commops-meeting-time-in-2019/787 (jwf, 17:09:39)
    8. Choosing a new time for meetings in 2019. Please review the suggested options and let us know your preference if one time works better than another for you to join. (jwf, 17:09:39)
    9. === [INCOMPLETE] "jwf File new tickets to discuss / plan out ideas from 2018-12-04 meeting further" === (jwf, 17:09:49)
    10. HELP: If some folks are willing to help with this, it would help to distribute the ticket filing. And then jwf doesn't have to re-explain the original ideas that came from others last week. (this is on the agenda for tickets — we will revisit soon!) (jwf, 17:09:58)
    11. ACTION: bpabon Create a flowchart based on 2018-12-04 meeting discussion (around conventions / expectations for filing a CommOps ticket), ready for review by Wed, Dec. 19th (jwf, 17:11:31)
    12. === [PARTIALLY COMPLETE] "jwf Post Discourse summary / do ticket updates from meeting this week" === (jwf, 17:11:38)
    13. https://discussion.fedoraproject.org/t/2018-12-04-docs-contributability-tests-and-brainstorming-on-on-boarding/778 (jwf, 17:11:45)
    14. Summary is up, but not all tickets have updates. Some of the things we discussed need new tickets, as per an earlier action item. (jwf, 17:11:45)

  5. Tickets (jwf, 17:12:05)
    1. https://pagure.io/fedora-commops/issues?status=Open&priority=20 (jwf, 17:12:05)

  6. Ticket #159: "Run a "Write the Docs" event targeting Fedora support groups" (jwf, 17:12:26)
    1. https://pagure.io/fedora-commops/issue/159 (jwf, 17:12:26)
    2. Next steps: This ticket is currently too big, now that we had a chance to talk it through. We had several great ideas from last week's meeting about how to divide this up. Let's try to come up with how we want to break this up and file new tickets for these ideas. (jwf, 17:12:26)
    3. IDEA: Creating “cheatsheet” of common Fedora tools, applications, and resources used across project (jwf, 17:14:55)
    4. IDEA: Find way to better document group contacts for different SIGs / sub-projects (jwf, 17:15:03)
    5. IDEA: Curate list of recurring “easyfix” tasks for CommOps (jwf, 17:15:11)
    6. IDEA: Write a "Fedora jargon cheatsheet" (jwf, 17:15:19)
    7. IDEA: "Game-ifying" a docs event, possibly having teams to compete for different goals (e.g. "edit X number of pages", "create X number of new pages", etc.) (jwf, 17:16:16)
    8. IDEA: Offering prizes for different categories, e.g. UnixStickers swag, gift cards, etc. (jwf, 17:18:46)
    9. ACTION: jwf File a new ticket to better document and offer up recurring "easyfix" tasks for CommOps by Wed, Dec. 19th (jwf, 17:29:17)
    10. ACTION: bt0 File a new ticket to create a "Fedora jargon" cheatsheet, to help explain different terms and phrases often used in Fedora (but not obvious to a newcomer or first-timer) by Wed, Dec. 19th (jwf, 17:30:34)
    11. ACTION: JohnMH Fix dead links in README of the fedora-commops repo by Wed, Dec. 19th (JohnMH, 17:31:03)
    12. ACTION: bpabon File a new ticket to better document procedure and best practices on cross-team communication and collaboration by Wed, Dec. 19th (and maybe add the flowchart from previous action there once it is ready!) (jwf, 17:32:59)
    13. ACTION: meskarune File a new ticket for a "cheatsheet" to explain different Fedora tools, apps, and resources and how they are used, by Wed, Dec. 19th (jwf, 17:37:04)
    14. ACTION: meskarune File a new ticket for brainstorming docs event "competition" categories and possible prizes to go with them, by Wed, Dec. 19th (jwf, 17:37:33)
    15. IDEA: Using Badges to correspond with some of the competition categories? (e.g. "Most docs edited in 2019 contribute-athon event", "Most new pages created in 2019 contribute-athon event", etc.) (jwf, 17:39:06)
    16. IDEA: Using page views / metrics as an incentive for a "highest visibility" fix category? (jwf, 17:42:34)

  7. Open floor (jwf, 17:43:41)


Meeting ended at 18:03:16 UTC (full logs).

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, ask for Design Team feedback. Due: before 2019
  3. bpabon Create a flowchart based on 2018-12-04 meeting discussion (around conventions / expectations for filing a CommOps ticket), ready for review by Wed, Dec. 19th
  4. jwf File a new ticket to better document and offer up recurring "easyfix" tasks for CommOps by Wed, Dec. 19th
  5. bt0 File a new ticket to create a "Fedora jargon" cheatsheet, to help explain different terms and phrases often used in Fedora (but not obvious to a newcomer or first-timer) by Wed, Dec. 19th
  6. JohnMH Fix dead links in README of the fedora-commops repo by Wed, Dec. 19th
  7. bpabon File a new ticket to better document procedure and best practices on cross-team communication and collaboration by Wed, Dec. 19th (and maybe add the flowchart from previous action there once it is ready!)
  8. meskarune File a new ticket for a "cheatsheet" to explain different Fedora tools, apps, and resources and how they are used, by Wed, Dec. 19th
  9. meskarune File a new ticket for brainstorming docs event "competition" categories and possible prizes to go with them, by Wed, Dec. 19th


Action items, by person

  1. bpabon
    1. bpabon Create a flowchart based on 2018-12-04 meeting discussion (around conventions / expectations for filing a CommOps ticket), ready for review by Wed, Dec. 19th
    2. bpabon File a new ticket to better document procedure and best practices on cross-team communication and collaboration by Wed, Dec. 19th (and maybe add the flowchart from previous action there once it is ready!)
  2. bt0
    1. bt0 File a new ticket to create a "Fedora jargon" cheatsheet, to help explain different terms and phrases often used in Fedora (but not obvious to a newcomer or first-timer) by Wed, Dec. 19th
  3. commops
    1. commops New members, please introduce yourself on the CommOps Discourse [ https://discussion.fedoraproject.org/c/project/commops ]
    2. JohnMH Fix dead links in README of the fedora-commops repo by Wed, Dec. 19th
  4. JohnMH
    1. JohnMH Fix dead links in README of the fedora-commops repo by Wed, Dec. 19th
  5. jwf
    1. jwf Draft set of user testing scenarios for contributing to docs, create new tickets for each test scenario, ask for Design Team feedback. Due: before 2019
    2. jwf File a new ticket to better document and offer up recurring "easyfix" tasks for CommOps by Wed, Dec. 19th
  6. meskarune
    1. meskarune File a new ticket for a "cheatsheet" to explain different Fedora tools, apps, and resources and how they are used, by Wed, Dec. 19th
    2. meskarune File a new ticket for brainstorming docs event "competition" categories and possible prizes to go with them, by Wed, Dec. 19th


People present (lines said)

  1. jwf (148)
  2. bpabon_ (37)
  3. meskarune (24)
  4. nb (17)
  5. JohnMH (17)
  6. zodbot (16)
  7. bt0 (8)
  8. wa1em (7)
  9. bpabon (3)
  10. commops-watch (3)
  11. commops-bot (2)
  12. commops (0)


Generated by MeetBot 0.1.4.