2024-01-23 12:30:20 <@jflory7:fedora.im> !startmeeting Community Blog editor roundtable
2024-01-23 12:30:20 <@meetbot:fedora.im> Meeting started at 2024-01-23 12:30:20 UTC
2024-01-23 12:30:20 <@meetbot:fedora.im> The Meeting name is 'Community Blog editor roundtable'
2024-01-23 12:31:04 <@jflory7:fedora.im> !topic Roll call & hello's
2024-01-23 12:31:07 <@jflory7:fedora.im> !hello jwf
2024-01-23 12:31:15 <@jflory7:fedora.im> !hello
2024-01-23 12:31:27 <@jflory7:fedora.im> !hi
2024-01-23 12:31:43 <@jflory7:fedora.im> I guess zodbot is feeling shy today :)
2024-01-23 12:32:22 <@jflory7:fedora.im> OK! So, this is the first go at getting the CommBlog editors together in a long time :)
2024-01-23 12:32:44 <@amoloney:fedora.im> .hello
2024-01-23 12:32:49 <@amoloney:fedora.im> !hello
2024-01-23 12:32:57 <@smooge:fedora.im> currently Fedora FAS is not working so various tools to look up users do not work
2024-01-23 12:33:04 <@amoloney:fedora.im> dang it
2024-01-23 12:33:08 <@smooge:fedora.im> so !hello, and such will not work
2024-01-23 12:33:11 <@jflory7:fedora.im> Aha. Then that explains it.
2024-01-23 12:33:24 <@smooge:fedora.im> once fasjson gets working again, this should work.
2024-01-23 12:33:30 <@jflory7:fedora.im> Hi Aoife Moloney 👋
2024-01-23 12:33:33 <@amoloney:fedora.im> thanks Smooge,. wasnt sure if it was still down
2024-01-23 12:33:40 <@smooge:fedora.im> it is still down
2024-01-23 12:33:54 <@amoloney:fedora.im> but not out :)
2024-01-23 12:34:12 <@jflory7:fedora.im> So, I think it will be just you and me today, Aoife Moloney 
2024-01-23 12:34:12 <@amoloney:fedora.im> Hi Justin W. Flory (he/him) :)
2024-01-23 12:34:18 <@jflory7:fedora.im> But I am optimistic about growing this group more :)
2024-01-23 12:34:24 <@jflory7:fedora.im> But for now, here is what I am thinking for the agenda:
2024-01-23 12:34:28 <@jflory7:fedora.im> !info Agenda
2024-01-23 12:34:43 <@jflory7:fedora.im> !info 1. Review pending queue of Community Blog articles and assign pending posts to an editor.
2024-01-23 12:34:52 <@jflory7:fedora.im> !info 2. Determine a weekly publishing schedule.
2024-01-23 12:35:00 <@jflory7:fedora.im> !info 3. Q&A for authors about their post.
2024-01-23 12:35:08 <@jflory7:fedora.im> !info 4. Administrative decisions to content, organization, and strategy.
2024-01-23 12:35:14 <@jflory7:fedora.im> !info 5. Guidance on becoming a Community Blog editor.
2024-01-23 12:35:23 <@jflory7:fedora.im> This is to start, can improvise as needed :)
2024-01-23 12:35:25 <@jflory7:fedora.im> Sound good?
2024-01-23 12:35:55 <@amoloney:fedora.im> Sounds good, point 5 might be an ongoing thing?
2024-01-23 12:36:01 <@jflory7:fedora.im> Right!
2024-01-23 12:36:15 <@jflory7:fedora.im> I thought that item for if we have any newcomers arrive at some point.
2024-01-23 12:36:22 <@jflory7:fedora.im> If just you and me, we can be brief :)
2024-01-23 12:36:29 <@jflory7:fedora.im> !topic Review pending queue of Community Blog articles and assign pending posts to an editor.
2024-01-23 12:36:34 <@jflory7:fedora.im> !link https://discussion.fedoraproject.org/c/workflows/community-blog-review/79
2024-01-23 12:37:01 <@jflory7:fedora.im> A few things have built up in the queue. I count four articles.
2024-01-23 12:37:21 <@jflory7:fedora.im> !link https://discussion.fedoraproject.org/t/review-publish-fedora-39-release-party-frankfurt-germany/99027
2024-01-23 12:37:29 <@jflory7:fedora.im> !link https://discussion.fedoraproject.org/t/review-publish-cpe-summary-2023/101759
2024-01-23 12:37:43 <@jflory7:fedora.im> !link https://discussion.fedoraproject.org/t/review-publish-i-r-2023-summary/101758
2024-01-23 12:37:54 <@jflory7:fedora.im> !link https://discussion.fedoraproject.org/t/review-and-publish-forthcoming-kubernetes-changes-in-rawhide/99308/4
2024-01-23 12:38:10 <@jflory7:fedora.im> I think that is all that is in the queue.
2024-01-23 12:38:19 <@amoloney:fedora.im> very basic, so i understand what Im looking at - the four articles that are in the 'backlog' of sorts can be identified by absence of the ticked checkbox on the left hand side of the title?
2024-01-23 12:38:41 <@jflory7:fedora.im> Ah, yeah. I try to use the "Solved" marker once a post has been edited and scheduled.
2024-01-23 12:38:58 <@amoloney:fedora.im> thats a nice process
2024-01-23 12:39:00 <@jflory7:fedora.im> As well as putting them here: https://discussion.fedoraproject.org/t/upcoming-commblog-posts/10890
2024-01-23 12:39:18 <@jflory7:fedora.im> Especially with onboarding more editors, the calendar feature is useful
2024-01-23 12:39:46 <@jflory7:fedora.im> I have not personally reviewed the articles, but I think all of the authors except maybe one have published on the CommBlog before
2024-01-23 12:40:05 <@jflory7:fedora.im> Here is what I am thinking for an editorial schedule
2024-01-23 12:41:01 <@jflory7:fedora.im> 1. 25 Jan: Frankfurt release party
2. 30 Jan: CPE 2023 summary
3. 1 February: K8s changes in Rawhide
4. 6 February: I&R 2023 summary
2024-01-23 12:41:03 <@jflory7:fedora.im> WDYT?
2024-01-23 12:41:42 <@amoloney:fedora.im> could we request the editor fold the CPE 2023 with the I+R 2023 summary? Its the same team, and would free up a slot for other content
2024-01-23 12:42:03 <@jflory7:fedora.im> I think that is fair feedback, although I have not compared the two drafts
2024-01-23 12:42:41 <@amoloney:fedora.im> neither have I, so I will do that and if there is enough crossover then I think consolidating them into one post is better
2024-01-23 12:42:58 <@jflory7:fedora.im> Oh I don't know if I will be able to log into the CommBlog or not 😅
2024-01-23 12:43:06 <@jflory7:fedora.im> I was trying to open a preview of the drafts
2024-01-23 12:43:51 <@jflory7:fedora.im> !idea Consolidate the CPE and I&R 2023 reviews into one post to free a slot for other content. Need to compare the two drafts when FAS is back online
2024-01-23 12:44:21 <@amoloney:fedora.im> I can access it, but the layout is super weird...probably something on my side
2024-01-23 12:44:30 <@amoloney:fedora.im> Ill take that action
2024-01-23 12:44:32 <@jflory7:fedora.im> Well, this is convenient timing for the first editor roundtable that I can't log into the CommBlog :)
2024-01-23 12:44:39 <@jflory7:fedora.im> Huh! Weird.
2024-01-23 12:44:57 <@jflory7:fedora.im> That was my next thought, about divying up the editing duties
2024-01-23 12:45:25 <@jflory7:fedora.im> I could take the K8s article since I worked on it previously before the author requested to hold.
2024-01-23 12:45:52 <@amoloney:fedora.im> +1 & Ill take the others (as two are possibly the same info)
2024-01-23 12:46:17 <@jflory7:fedora.im> OK! I was going to ask if you wanted me to take the release party one :)
2024-01-23 12:46:28 <@amoloney:fedora.im> if you'd like to you can?
2024-01-23 12:46:48 <@jflory7:fedora.im> I would like to read that one anyways so I can take it
2024-01-23 12:46:55 <@amoloney:fedora.im> perfecto 
2024-01-23 12:47:21 <@jflory7:fedora.im> !action JWF Frankfurt Release Party, K8s changes in Rawhide
2024-01-23 12:47:53 <@jflory7:fedora.im> !action amoloney Request CPE + I&R author to consolidate if possible, review + schedule after request
2024-01-23 12:48:05 <@jflory7:fedora.im> And then I think that works through our holiday backlog :)
2024-01-23 12:48:24 <@amoloney:fedora.im> I like your editorial schedule though so lets stick to that
2024-01-23 12:48:33 <@amoloney:fedora.im> indeed it does too!
2024-01-23 12:48:36 <@jflory7:fedora.im> !topic Determine a weekly publishing schedule.
2024-01-23 12:49:12 <@jflory7:fedora.im> !agreed 25 Jan: Frankfurt release party; 30 Jan: CPE 2023 summary; 1 February: K8s changes in Rawhide
2024-01-23 12:49:32 <@jflory7:fedora.im> !topic Q&A for authors about their post.
2024-01-23 12:49:38 <@jflory7:fedora.im> !info No authors present today. Skipping.
2024-01-23 12:49:45 <@jflory7:fedora.im> !topic Administrative decisions to content, organization, and strategy.
2024-01-23 12:50:16 <@jflory7:fedora.im> At some point, I would like to revisit some category and tag reorganization, but this can be post-FOSDEM et al.
2024-01-23 12:50:34 <@amoloney:fedora.im> I am following your lead a little bit here as Im still pretty fresh to this  part of the work
2024-01-23 12:50:53 <@amoloney:fedora.im> tag reorg would be nice
2024-01-23 12:50:59 <@jflory7:fedora.im> I am feeling a little rusty TBH, but getting back into a weekly cadence will help a lot with that :)
2024-01-23 12:51:00 <@amoloney:fedora.im> there are a lot built up with past dates 
2024-01-23 12:51:16 <@amoloney:fedora.im> do the tags even need to be dated?
2024-01-23 12:51:23 <@amoloney:fedora.im> eg Elections 2019
2024-01-23 12:51:36 <@amoloney:fedora.im> (dont know thats an exact one, but Ive seen a few like that)
2024-01-23 12:51:40 <@jflory7:fedora.im> Yes, I think there could be more consolidation. I tried to do some before but realized I was probably doing it too unilaterally, especially when I broke some Discourse posting bot
2024-01-23 12:51:59 <@amoloney:fedora.im> darn intergations :)
2024-01-23 12:52:06 <@amoloney:fedora.im> darn integrations :)
2024-01-23 12:52:06 <@jflory7:fedora.im> I think tags can be organized around a date, like for a specific election cycle
2024-01-23 12:52:21 <@jflory7:fedora.im> But WordPress does have a way to view posts by year already
2024-01-23 12:52:27 <@jflory7:fedora.im> So no purpose in duplicating the year only
2024-01-23 12:52:50 <@amoloney:fedora.im> Hmmm, I can see the value for looking up specific posts wth this, but it means generating a new tag every time
2024-01-23 12:53:02 <@amoloney:fedora.im> its a small task though either way so might be a preference thing
2024-01-23 12:53:19 <@amoloney:fedora.im> food for thought methinks
2024-01-23 12:53:47 <@jflory7:fedora.im> It would be good to take a desk review of the existing tags. But yeah, I agree, food for thought :) If we ever have one of these weeklies and there are no articles to review, that would be a good topic
2024-01-23 12:53:55 <@amoloney:fedora.im> post FOSDEM we should try have a few tasks built up to work on as the Editors group
2024-01-23 12:54:08 <@jflory7:fedora.im> What do you have in mind?
2024-01-23 12:54:10 <@amoloney:fedora.im> so maybe the action here is to create a little backlog of sorts
2024-01-23 12:54:19 <@amoloney:fedora.im> or a kanban board with tickets?
2024-01-23 12:54:28 <@amoloney:fedora.im> ie, check onboarding documentation & update
2024-01-23 12:54:35 <@amoloney:fedora.im> review tag & edi
2024-01-23 12:54:39 <@amoloney:fedora.im> review tag & edit
2024-01-23 12:54:40 <@jflory7:fedora.im> I like that – what would be the right thing to use? GitLab tickets?
2024-01-23 12:54:49 <@jflory7:fedora.im> Not sure if GitLab is overkill or not
2024-01-23 12:55:07 <@amoloney:fedora.im> It might not be
2024-01-23 12:55:20 <@amoloney:fedora.im> would this fit as a subset of another project?
2024-01-23 12:55:43 <@amoloney:fedora.im> maybe the marketing folks would be interested in having this live in their gitlab house? 
2024-01-23 12:55:49 <@amoloney:fedora.im> but managed by the editors of course
2024-01-23 12:56:07 <@jflory7:fedora.im> !idea Build up more tasks and a backlog to grow the Editors group, e.g. tickets/issues, a kanban board.
2024-01-23 12:56:31 <@jflory7:fedora.im> Not a bad idea. As a Marketing Team member, it seems like a good fit :)
2024-01-23 12:56:37 <@jflory7:fedora.im> I can ask the team.
2024-01-23 12:56:48 <@jflory7:fedora.im> I do like the idea of perhaps moving to a ticket workflow instead of Fedora Discussion for this
2024-01-23 12:56:49 <@amoloney:fedora.im> thank you :)
2024-01-23 12:56:59 <@jflory7:fedora.im> It would be easier to get some data and metrics about our churn too with GitLab issues
2024-01-23 12:57:29 <@jflory7:fedora.im> !action JWF Ask the Marketing Team if we can launch a new repository for Community Blog review requests and task tracking
2024-01-23 12:57:31 <@amoloney:fedora.im> its worth a try, worst case scenario is that it doesnt get traction and we are not really any worse off than we are now
2024-01-23 12:57:39 <@jflory7:fedora.im> True!
2024-01-23 12:57:55 <@jflory7:fedora.im> OK, we have three minutes left… I feel like for a first meeting, we covered good ground :)
2024-01-23 12:58:04 <@amoloney:fedora.im> Same
2024-01-23 12:58:07 <@jflory7:fedora.im> Some of our work is blocked on FAS, but once that is resolved, we will be in business :)
2024-01-23 12:58:31 <@amoloney:fedora.im> its good to be leaving this with some tasks 
2024-01-23 12:58:40 <@jflory7:fedora.im> I will go ahead and call it here, and we will pick back up next week. I expect we might cancel for the following week or two due to FOSDEM / Council Hackfest.
2024-01-23 12:58:42 <@amoloney:fedora.im> so I call it a successful first meeting
2024-01-23 12:58:54 <@amoloney:fedora.im> yeah exactly
2024-01-23 12:59:00 <@jflory7:fedora.im> Aoife Moloney++ Thanks for partnering with me on it!
2024-01-23 12:59:05 <@jflory7:fedora.im> See ya next time :)
2024-01-23 12:59:07 <@jflory7:fedora.im> !endmeeting