commops
MINUTES

#fedora-commops: Fedora CommOps (2018-09-26)

Meeting started by jwf at 16:08:35 UTC (full logs).

Meeting summary

  1. Agenda (jwf, 16:08:43)
    1. https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next (jwf, 16:08:47)
    2. (1) Roll call / Q&A (jwf, 16:08:50)
    3. (2) Announcements (jwf, 16:08:52)
    4. (3) Action items from last meeting (jwf, 16:08:54)
    5. (4) Tickets (jwf, 16:08:56)
    6. (5) Open floor (jwf, 16:08:58)

  2. Roll call / Q&A (jwf, 16:09:02)
    1. Name; Timezone; Sub-projects/Interest Areas (jwf, 16:09:04)
    2. ACTION: commops New members, please introduce yourself on the CommOps mailing list [ https://docs.fedoraproject.org/en-US/commops/contribute/join/ ] (jwf, 16:09:08)
    3. Justin W. Flory; UTC-5; CommOps, D&I Team, Mindshare (for a month more), Fedora Badges sysadmin (jwf, 16:09:34)
    4. Ben Cotton; UTC-4; FPgM (bcotton, 16:09:45)

  3. Announcements (jwf, 16:11:57)
    1. === "FPgM report: 2018-38" === (jwf, 16:12:04)
    2. https://communityblog.fedoraproject.org/fpgm-report-2018-38/ (jwf, 16:12:04)
    3. This week in Fedora is brought to you in part by bcotton. (jwf, 16:12:04)
    4. === "Submit a Fedora talk to DevConf.cz 2019" === (jwf, 16:12:46)
    5. https://communityblog.fedoraproject.org/submit-fedora-talk-devconf-cz-2019/ (jwf, 16:12:46)
    6. The CfP for the DevConf devops conference in Brno, Czech Republic is now open. Fedora topics welcome! (jwf, 16:12:46)
    7. === "Announcing the release of Fedora 29 Beta" === (jwf, 16:14:06)
    8. https://fedoramagazine.org/announcing-fedora-29-beta/ (jwf, 16:14:11)
    9. Fedora 29 Beta launched this week! Get a sneak peek into what's ahead for Fedora and what's planned for the final release next month. (jwf, 16:14:36)

  4. Action items from last meeting (jwf, 16:15:35)
    1. https://meetbot.fedoraproject.org/fedora-commops/2018-09-19/commops.2018-09-19-16.01.html (jwf, 16:15:38)
    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, 16:15:42)
    3. === [COMPLETE] "bt0 Write a second contributor story for FAW (due no later than Monday, 2018-09-24)" === (jwf, 16:15:54)
    4. === [DELAYED] "jwf Write a CommBlog article summarizing CommOps @ Flock by Wednesday, Sept. 26" === (jwf, 16:16:31)
    5. ACTION: jwf Write a CommBlog article summarizing CommOps @ Flock by Wednesday, Oct. 3 (jwf, 16:16:31)
    6. === [COMPLETE] "jwf Work with bt0 and pingou to configure a new event to collect and vote on community photos in Nuancier for Fedora Appreciation Week" === (jwf, 16:17:13)
    7. We reached out to pingou via email to see if Nuancier can be used for FAW. Might be a slow response since a major Pagure update released this week too. (jwf, 16:17:13)
    8. === [IN PROGRESS] "bt0 Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3)" === (jwf, 16:17:52)
    9. ACTION: bt0 Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3) (jwf, 16:17:53)
    10. === [COMPLETE] "bcotton File a new CommOps ticket about an editorial calendar for the CommBlog to prevent editors stepping on toes for scheduling articles (and other ways to improve awareness of CommBlog happenings)" === (jwf, 16:18:25)
    11. === [COMPLETE] "bcotton File a new CommOps ticket about an editorial calendar for the CommBlog to prevent editors stepping on toes for scheduling articles (and other ways to improve awareness of CommBlog happenings)" === (jwf, 16:18:53)
    12. https://pagure.io/fedora-commops/issue/184 (jwf, 16:18:53)

  5. Tickets (jwf, 16:19:47)
    1. https://pagure.io/fedora-commops/issues?status=Open&priority=20 (jwf, 16:19:50)

  6. Ticket #110: "Fedora Appreciation Week 2018" (jwf, 16:20:34)
    1. https://pagure.io/fedora-commops/issue/110 (jwf, 16:20:34)
    2. https://screenshots.firefox.com/xu7fdJ4v3sVLlQYh/etherpad.gnome.org (jwf, 16:20:34)
    3. No updates as of now; bt0 and jwf working with pingou for using Nuancier. dhanesh95 filed tickets for Design and Badges. Still need a common header for CommBlog posts published during FAW, but may slip to next month. (jwf, 16:23:38)

  7. Ticket #178: "Pilot run a CommOps section on discussion.fedoraproject.org" (jwf, 16:24:34)
    1. https://pagure.io/fedora-commops/issue/178 (jwf, 16:24:34)
    2. https://discussion.fedoraproject.org/ (jwf, 16:24:34)
    3. Work to do before Monday, Oct. 1 launch: (1) explicitly announce transition on list, (2) set up an auto-mailer message for the mailing list about Discourse, (3) set up / configure the CommOps subforum with help from sanja (jwf, 16:27:34)
    4. Fedocal automated email messages need consideration (jwf, 16:31:12)
    5. ACTION: jwf Send an email announcement to CommOps list to boost awareness of upcoming Mailman => Discourse migration experiment by end of day Wednesday, Sept. 26 (jwf, 16:32:29)
    6. ACTION: jwf Set up auto-email response for new threads on CommOps list to explain Discourse migration by Sunday, Sept. 30 (jwf, 16:33:01)

  8. Ticket #168: "Propose a set of Pagure tags than help the onboarding process" (jwf, 16:34:35)
    1. https://pagure.io/fedora-commops/issue/168 (jwf, 16:34:36)
    2. Next Steps: find the correct place for this docs (CommOps docs?? another repo, a brand new docs page?) (jwf, 16:34:36)
    3. ACTION: bt0 Update Ticket #168 (Pagure tags ticket) by next meeting on Wednesday, Oct. 3 (jwf, 16:36:20)

  9. Open floor (jwf, 16:36:47)
    1. https://pagure.io/wordcloudbot (jwf, 16:38:40)


Meeting ended at 16:40:37 UTC (full logs).

Action items

  1. commops New members, please introduce yourself on the CommOps mailing list [ https://docs.fedoraproject.org/en-US/commops/contribute/join/ ]
  2. jwf Write a CommBlog article summarizing CommOps @ Flock by Wednesday, Oct. 3
  3. bt0 Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3)
  4. jwf Send an email announcement to CommOps list to boost awareness of upcoming Mailman => Discourse migration experiment by end of day Wednesday, Sept. 26
  5. jwf Set up auto-email response for new threads on CommOps list to explain Discourse migration by Sunday, Sept. 30
  6. bt0 Update Ticket #168 (Pagure tags ticket) by next meeting on Wednesday, Oct. 3


Action items, by person

  1. bt0
    1. bt0 Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3)
    2. bt0 Update Ticket #168 (Pagure tags ticket) by next meeting on Wednesday, Oct. 3
  2. commops
    1. commops New members, please introduce yourself on the CommOps mailing list [ https://docs.fedoraproject.org/en-US/commops/contribute/join/ ]
    2. bt0 Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3)
  3. jwf
    1. jwf Write a CommBlog article summarizing CommOps @ Flock by Wednesday, Oct. 3
    2. jwf Send an email announcement to CommOps list to boost awareness of upcoming Mailman => Discourse migration experiment by end of day Wednesday, Sept. 26
    3. jwf Set up auto-email response for new threads on CommOps list to explain Discourse migration by Sunday, Sept. 30


People present (lines said)

  1. jwf (127)
  2. zodbot (11)
  3. fcommops-tg1 (7)
  4. bcotton (6)
  5. nb (2)
  6. labbott (1)
  7. bt0 (0)
  8. commops (0)
  9. bee2502 (0)


Generated by MeetBot 0.1.4.
Meetbot Logs © 2021-2022 Fedora Websites and Apps Team (Sources)