[2018-12-04] Docs "contributability" tests and brainstorming on on-boarding

Project Discussion
1

Hi all! The minutes are making it to Discourse late, but a meeting happened this week! And it was actually a really interesting one too.

This week, we strayed from topic but ended up critically analyzing how to engage newcomers and also thinking about helpful things we want to write for our own docs. New Pagure tickets are coming soon, but here’s a high-level summary of what we talked about:

  • meskarune interested in helping with “contributability” tests (once created)
  • Creating “cheatsheet” of common Fedora tools, applications, and resources used across project
    • Helpful for people who may not contribute often and try to follow along with where things are happening
    • Feedback specifically around emergence of new tools, like Discourse and Fedora Docs site (as I understood it)
  • Find way to better document group contacts for different SIGs / sub-projects
    • For example: how does someone follow up with an unanswered ticket in CommOps? Infrastructure? Goal is to make it easier / less awkward to do that follow-up
  • Curate list of recurring “easyfix” tasks for CommOps
    • In the meeting, we talked about using a ticket template. Maybe docs makes sense too. It’s unclear. Could use more thoughts.
  • Write a “Fedora jargon cheatsheet”
    • Like a vocabulary sheet of different terms, phrases, and tools often used specifically in Fedora community
    • Sort of like a Fedora anthropological adventure!

Thanks everyone who contributed to this thoughtful discussion. I have a few action items open to get some of these things ticket-ified, so keep an eye out on Pagure for these.

Meeting ended Wed Dec 5 18:07:16 2018 UTC.

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

Meeting started by bt0 at 17:09:52 UTC. The full logs are available here.
.

Meeting summary

  • Agenda (jwf, 17:11:22)

  • Roll call / Q&A (jwf, 17:11:36)

    • Name; Timezone; Sub-projects/Interest Areas (jwf, 17:11:38)
    • ACTION: commops New members, please introduce yourself on the
      CommOps Discourse [
      https://discussion.fedoraproject.org/c/project/commops ] (jwf,
      17:11:40)
    • Justin W. Flory; UTC-5; CommOps, D&I Team, Fedora Badges (jwf,
      17:12:17)
    • Alberto Rodriguez S; UTC-6; CommOps, Marketing, dotnet and more
      (bt0, 17:13:23)

  • Announcements (jwf, 17:14:31)

  • Action items from last meeting (jwf, 17:17:50)

    • LINK: https://pagure.io/fedora-docs/docs-fp-o/issue/104 doesn’t get
      love from the docs folks. (bpabon, 17:18:17)
    • LINK:
      Meetbot Logs
      (jwf, 17:18:39)
    • 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)
    • === [IN PROGRESS] “bt0 Complete a first draft of new CommOps docs
      page on suggested Pagure tags (due: Monday, Dec. 3rd)” === (jwf,
      17:21:00)
    • Will discuss further during tickets part of meeting! (jwf,
      17:21:01)
    • === [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)
    • LINK:
      https://communityblog.fedoraproject.org/?p=6716&preview=1&_ppp=1017420676
      (jwf, 17:21:24)
    • Draft is complete and ready for review. bt0++ (jwf, 17:21:25)
    • === [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)
    • 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)
    • === [INCOMPLETE] “jwf Share test scenarios with Design Team to get
      additional feedback” === (jwf, 17:22:29)
    • ACTION: jwf Share test scenarios with Design Team to get additional
      feedback (jwf, 17:22:29)
    • === [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)
    • LINK: https://pagure.io/fedora-docs/docs-fp-o/issue/104 (jwf,
      17:23:22)
    • 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)
    • === [INCOMPLETE] “jwf Start new Discourse thread about the Dilemma
      of the Conflicting Meetings” === (jwf, 17:26:06)
    • ACTION: jwf Start new Discourse thread about the Dilemma of the
      Conflicting Meetings (jwf, 17:26:06)

  • Tickets (jwf, 17:26:42)

  • Ticket #159: “Run a “Write the Docs” event targeting Fedora support
    groups” (jwf, 17:28:43)

    • LINK: Issue #159: Run a "Write the Docs" event targeting Fedora support groups - fedora-commops - Pagure.io (jwf, 17:28:43)
    • meskarune interested in helping with running through the test cases
      once ready (jwf, 17:29:00)
    • HELP: bpabon looking for additional feedback from Fedora Docs team
      members on Discourse thread (jwf, 17:29:17)
    • LINK: https://pagure.io/fedora-docs/docs-fp-o/issue/104 (jwf,
      17:30:12)
    • IDEA: Should CommOps create a list of common tools with descriptions
      of what they are in our own documentation? (jwf, 17:38:53)
    • IDEA: What if we created a “Fedora vocabulary sheet” with the
      buzzwords / jargon / unique vocabulary from across the Fedora
      community (jwf, 17:39:19)
    • ACTION: jwf File new tickets to discuss / plan out these ideas
      further (jwf, 17:41:00)
    • 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)
    • HELP: Create an updated list of sub-project contact info (jwf,
      18:02:53)
    • IDEA: Create list of tasks for newbies to do in CommOps (jwf,
      18:03:01)
    • IDEA: New ticket templates for recurring, easy fix tasks (e.g.
      certain CommBlog articles, fedmsg mini-experiments, etc.) (jwf,
      18:04:58)
    • ACTION: jwf Post Discourse summary / do ticket updates from meeting
      this week (jwf, 18:07:10)

Meeting ended at 18:07:16 UTC.

Action Items

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

Action Items, by person

  • bpabon
    • bpabon Create a flowchart based on meeting discussion (around
      conventions / expectations for filing a CommOps ticket), review at
      next meeting
  • commops
  • jwf
    • jwf Draft set of user testing scenarios for contributing to docs,
      create new tickets for each test scenario. Due: before 2019.
    • jwf Share test scenarios with Design Team to get additional feedback
    • jwf Start new Discourse thread about the Dilemma of the Conflicting
      Meetings
    • jwf File new tickets to discuss / plan out these ideas further
    • jwf Post Discourse summary / do ticket updates from meeting this
      week
  • UNASSIGNED
    • (none)

People Present (lines said)

  • @jwf (150)
  • @blaise (47)
  • meskarune (46)
  • zodbot (16)
  • @bt0dotninja (15)
  • commops-bot (2)
  • tg-fedcommops (2)
  • VibroMax (2)
  • nb (1)
  • jbjorkang (0)
  • commops (0)

Generated by MeetBot_ 0.1.4

… _MeetBot: MeetBot - Debian Wiki