===================================== # #meeting:fedoraproject.org: Community Blog editor roundtable ===================================== Meeting started by @jflory7:fedora.im at 2024-04-02 11:34:03 Meeting summary --------------- * TOPIC: Intros, welcomes, hellos (@jflory7:fedora.im, 11:34:23) * INFO: Welcome to the Community Blog editor roundtable. If you are attending, please introduce yourself by typing "!hi" in the chat. See the meeting agenda at the link below. (@jflory7:fedora.im, 11:34:30) * LINK: https://hackmd.io/@fedora-marketing-team/rJJXxxE66 (@jflory7:fedora.im, 11:34:35) * INFO: Present: @jflory7, @amoloney, @roseline-bassey, @omooba1 (@jflory7:fedora.im, 11:38:03) * TOPIC: Pending article review (@jflory7:fedora.im, 11:38:08) * INFO: What We Do: Review the pending queue of Community Blog articles and assign pending posts to an editor. (@jflory7:fedora.im, 11:38:14) * LINK: https://discussion.fedoraproject.org/c/workflows/community-blog-review/79 (@jflory7:fedora.im, 11:38:18) * LINK: https://discussion.fedoraproject.org/t/review-publish-lwn-subscription-slots-available-for-fedora-contributors/108129/3 (@jflory7:fedora.im, 11:44:04) * AGREED: Bumped the LWN article to Wednesday to account for the git forge announcement coming on Thursday. (@jflory7:fedora.im, 11:44:36) * LINK: https://discussion.fedoraproject.org/t/review-publish-how-to-rebase-to-fedora-silverblue-40-beta/109793/3 (@jflory7:fedora.im, 11:45:36) * LINK: https://discussion.fedoraproject.org/t/review-publish-automation-through-accessibility/108070/3 (@jflory7:fedora.im, 11:45:51) * TOPIC: Schedule planning (@jflory7:fedora.im, 11:47:21) * INFO: Review all the articles discussed previously. Determine the publishing schedule. Editors should either +1 or -1 the proposed schedule to ratify it. (@jflory7:fedora.im, 11:47:28) * LINK: https://discussion.fedoraproject.org/t/upcoming-community-blog-commblog-posts/10890 (@jflory7:fedora.im, 11:47:33) * INFO: 2024-04-02: Join us! Restarting Community Ops team meetings in 2024 (@jflory7:fedora.im, 11:48:06) * INFO: 2024-04-03: LWN subscription slots available for Fedora contributors (@jflory7:fedora.im, 11:48:19) * INFO: 2024-04-04: Git forge announcement (pending) (@jflory7:fedora.im, 11:48:43) * INFO: Next week: A Fedora Strategy article from @mattdm and possibly another Council communication. (@jflory7:fedora.im, 11:52:41) * INFO: @jflory7 has started to reach out to authors with old article drafts to determine if they wish to finish or trash their old drafts. (@jflory7:fedora.im, 11:54:04) * TOPIC: Administravia (@jflory7:fedora.im, 11:55:34) * INFO: Administrative decisions to content, organization, and strategy. This is not about articles but about structure and organization of the CommBlog itself. (@jflory7:fedora.im, 11:55:39) * LINK: https://gitlab.com/fedora/marketing/commblog/-/issues (@jflory7:fedora.im, 11:55:45) * INFO: Some tickets are there in GitLab, but we will need to integrate this more into our workflow. A topic for next week? (@jflory7:fedora.im, 11:56:57) * ACTION: @jflory7 Add topic for next week on formalizing the CommBlog workflow (@jflory7:fedora.im, 11:58:56) Meeting ended at 2024-04-02 12:00:57 Action items ------------ * @jflory7 Add topic for next week on formalizing the CommBlog workflow People Present (lines said) --------------------------- * @jflory7:fedora.im (75) * @amoloney:fedora.im (30) * @omooba1:matrix.org (3) * @zodbot:fedora.im (3) * @roseline:matrix.org (2) * @meetbot:fedora.im (2)