[2018-11-28] Publicity for WordCloudBot ticket, user experience tests for contributing to Fedora Docs

Hi all! Today’s meeting happened earlier today. We split the discussion between two tickets: the WordCloudBot ticket and the Fedora Docs contribute-athon ticket. We walked through some first steps for how to move forward and assigned some action items to get momentum going.

Details and minutes are below. Thanks everyone who came out and participated today. :grinning:


Meeting ended Wed Nov 28 18:02:25 2018 UTC.


#fedora-commops: Fedora CommOps (2018-11-28)

Meeting started by jwf at 17:03:04 UTC. The full logs are available at

.

Meeting summary

  • Agenda (jwf, 17:03:12)

  • Roll call / Q&A (jwf, 17:03:33)

    • Name; Timezone; Sub-projects/Interest Areas (jwf, 17:03:35)
    • ACTION: commops New members, please introduce yourself on the
      CommOps Discourse [
      https://discussion.fedoraproject.org/c/project/commops ] (jwf,
      17:03:37)
    • Alberto Rodriguez S; UTC-6; CommOps, Marketing, Fedora Join, dotnet
      and more (bt0, 17:08:00)
    • Justin W. Flory; UTC-5; CommOps, D&I Team, Fedora Badges (jwf,
      17:08:18)
  • Announcements (jwf, 17:08:46)

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

    • LINK:
      Meetbot Logs
      (jwf, 17:12:06)
    • 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:12:06)
    • ACTION: bt0 Complete a first draft of new CommOps docs page on
      suggested Pagure tags (due: Monday, Dec. 3rd) (jwf, 17:13:21)
    • === [COMPLETE] “jwf Archive CommOps mailing list” === (jwf,
      17:13:29)
    • LINK: Issue #178: Pilot run a CommOps section on discussion.fedoraproject.org - fedora-commops - Pagure.io
      (jwf, 17:13:29)
    • CommOps list now has an updated description, rejects new posts to
      the list, and requires moderation for new subscriptions. (jwf,
      17:13:29)
    • === [COMPLETE] “jwf Start a new Discourse thread to solicit feedback
      on F30 planning focus” === (jwf, 17:13:37)
    • LINK:
      Secret plans revealed: what CommOps hopes to accomplish in Fedora 30 release cycle
      (jwf, 17:13:37)
    • Link also shared over to Mindshare mailing list. (jwf, 17:13:37)
  • Tickets (jwf, 17:14:08)

  • Ticket #186: “Run worldcloudbot on @fedoracommunity Twitter account”
    (jwf, 17:14:47)

    • LINK: Issue #186: Run worldcloudbot on @fedoracommunity Twitter account - fedora-commops - Pagure.io (jwf, 17:14:47)
    • Next steps: Need to find a willing volunteer to play with Python and
      fedmsg. Some coding background is helpful, but it should not be
      complex. If no volunteers in the meeting, let’s find a way to make
      this task more visible in the Fedora community. Discourse? CommBlog?
      Reddit…? We can be creative. (jwf, 17:15:10)
    • IDEA: Write up a CommBlog article (like a “CommOps winter 2018
      easyfix newsletter”) and try sharing that more widely on social
      media or user communities (jwf, 17:19:02)
    • ACTION: 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:32)
    • IDEA: Using Instagram stories to highlight contribution
      opportunities once CommBlog article publishes (cc: jonatoni) (jwf,
      17:23:41)
  • Ticket #159: “Run a “Write the Docs” event targeting Fedora support
    groups” (jwf, 17:25:43)

  • Open floor (jwf, 17:58:16)

    • ACTION: jwf Start new Discourse thread about the Dilemma of the
      Conflicting Meetings (jwf, 18:00:18)

Meeting ended at 18:02:25 UTC.

Action Items

  • commops New members, please introduce yourself on the CommOps
    Discourse [ https://discussion.fedoraproject.org/c/project/commops ]
  • bt0 Complete a first draft of new CommOps docs page on suggested
    Pagure tags (due: Monday, Dec. 3rd)
  • bt0 Write a CommBlog draft to link and explain two or three CommOps
    “easyfix” tasks for Winter 2018 (due: Monday, Dec. 3rd)
  • jwf Draft set of user testing scenarios for contributing to docs,
    create new tickets for each test scenario. Due: Friday, Nov. 30th.
  • jwf Share test scenarios with Design Team to get additional feedback
  • bpabon Investigate ways to visualize diagrams from text further and
    then open new Pagure / docs-fp-o tickets for rendering support
  • jwf Start new Discourse thread about the Dilemma of the Conflicting
    Meetings

Action Items, by person

  • bpabon
    • bpabon Investigate ways to visualize diagrams from text further and
      then open new Pagure / docs-fp-o tickets for rendering support
  • bt0
    • bt0 Complete a first draft of new CommOps docs page on suggested
      Pagure tags (due: Monday, Dec. 3rd)
    • bt0 Write a CommBlog draft to link and explain two or three CommOps
      “easyfix” tasks for Winter 2018 (due: Monday, Dec. 3rd)
  • commops
  • jwf
    • jwf Draft set of user testing scenarios for contributing to docs,
      create new tickets for each test scenario. Due: Friday, Nov. 30th.
    • jwf Share test scenarios with Design Team to get additional feedback
    • jwf Start new Discourse thread about the Dilemma of the Conflicting
      Meetings
  • UNASSIGNED
    • (none)

People Present (lines said)

Generated by MeetBot_ 0.1.4

… _MeetBot: MeetBot - Debian Wiki

1 Like

Sorry I missed the meeting, was in a meeting with $WORK.

see: Issue #104: [RFE]Support for creating diagrams from text (eg. Graphviz, diagrams.js, PlantUML, etc.) - docs-fp-o - Pagure.io

1 Like