#meeting:fedoraproject.org log

<@jflory7:fedora.im>

12:30:20

!startmeeting Community Blog editor roundtable

<@meetbot:fedora.im>

12:30:20

Meeting started at 2024-01-23 12:30:20 UTC

<@meetbot:fedora.im>

12:30:20

The Meeting name is 'Community Blog editor roundtable'

<@jflory7:fedora.im>

12:31:04

!topic Roll call & hello's

<@jflory7:fedora.im>

12:31:07

!hello jwf

<@jflory7:fedora.im>

12:31:15

!hello

<@jflory7:fedora.im>

12:31:27

!hi

<@jflory7:fedora.im>

12:31:43

I guess zodbot is feeling shy today :)

<@jflory7:fedora.im>

12:32:22

OK! So, this is the first go at getting the CommBlog editors together in a long time :)

<@amoloney:fedora.im>

12:32:44

.hello

<@amoloney:fedora.im>

12:32:49

!hello

<@smooge:fedora.im>

12:32:57

currently Fedora FAS is not working so various tools to look up users do not work

<@amoloney:fedora.im>

12:33:04

dang it

<@smooge:fedora.im>

12:33:08

so !hello, and such will not work

<@jflory7:fedora.im>

12:33:11

Aha. Then that explains it.

<@smooge:fedora.im>

12:33:24

once fasjson gets working again, this should work.

<@jflory7:fedora.im>

12:33:30

Hi Aoife Moloney 👋

<@amoloney:fedora.im>

12:33:33

thanks Smooge,. wasnt sure if it was still down

<@smooge:fedora.im>

12:33:40

it is still down

<@amoloney:fedora.im>

12:33:54

but not out :)

<@jflory7:fedora.im>

12:34:12

So, I think it will be just you and me today, Aoife Moloney

<@amoloney:fedora.im>

12:34:12

Hi Justin W. Flory (he/him) :)

<@jflory7:fedora.im>

12:34:18

But I am optimistic about growing this group more :)

<@jflory7:fedora.im>

12:34:24

But for now, here is what I am thinking for the agenda:

<@jflory7:fedora.im>

12:34:28

!info Agenda

<@jflory7:fedora.im>

12:34:43

!info 1. Review pending queue of Community Blog articles and assign pending posts to an editor.

<@jflory7:fedora.im>

12:34:52

!info 2. Determine a weekly publishing schedule.

<@jflory7:fedora.im>

12:35:00

!info 3. Q&A for authors about their post.

<@jflory7:fedora.im>

12:35:08

!info 4. Administrative decisions to content, organization, and strategy.

<@jflory7:fedora.im>

12:35:14

!info 5. Guidance on becoming a Community Blog editor.

<@jflory7:fedora.im>

12:35:23

This is to start, can improvise as needed :)

<@jflory7:fedora.im>

12:35:25

Sound good?

<@amoloney:fedora.im>

12:35:55

Sounds good, point 5 might be an ongoing thing?

<@jflory7:fedora.im>

12:36:01

Right!

<@jflory7:fedora.im>

12:36:15

I thought that item for if we have any newcomers arrive at some point.

<@jflory7:fedora.im>

12:36:22

If just you and me, we can be brief :)

<@jflory7:fedora.im>

12:36:29

!topic Review pending queue of Community Blog articles and assign pending posts to an editor.

<@jflory7:fedora.im>

12:36:34

!link https://discussion.fedoraproject.org/c/workflows/community-blog-review/79

<@jflory7:fedora.im>

12:37:01

A few things have built up in the queue. I count four articles.

<@jflory7:fedora.im>

12:37:21

!link https://discussion.fedoraproject.org/t/review-publish-fedora-39-release-party-frankfurt-germany/99027

<@jflory7:fedora.im>

12:37:29

!link https://discussion.fedoraproject.org/t/review-publish-cpe-summary-2023/101759

<@jflory7:fedora.im>

12:37:43

!link https://discussion.fedoraproject.org/t/review-publish-i-r-2023-summary/101758

<@jflory7:fedora.im>

12:37:54

!link https://discussion.fedoraproject.org/t/review-and-publish-forthcoming-kubernetes-changes-in-rawhide/99308/4

<@jflory7:fedora.im>

12:38:10

I think that is all that is in the queue.

<@amoloney:fedora.im>

12:38:19

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?

<@jflory7:fedora.im>

12:38:41

Ah, yeah. I try to use the "Solved" marker once a post has been edited and scheduled.

<@amoloney:fedora.im>

12:38:58

thats a nice process

<@jflory7:fedora.im>

12:39:00

As well as putting them here: https://discussion.fedoraproject.org/t/upcoming-commblog-posts/10890

<@jflory7:fedora.im>

12:39:18

Especially with onboarding more editors, the calendar feature is useful

<@jflory7:fedora.im>

12:39:46

I have not personally reviewed the articles, but I think all of the authors except maybe one have published on the CommBlog before

<@jflory7:fedora.im>

12:40:05

Here is what I am thinking for an editorial schedule

<@jflory7:fedora.im>

12:41:01

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

<@jflory7:fedora.im>

12:41:03

WDYT?

<@amoloney:fedora.im>

12:41:42

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

<@jflory7:fedora.im>

12:42:03

I think that is fair feedback, although I have not compared the two drafts

<@amoloney:fedora.im>

12:42:41

neither have I, so I will do that and if there is enough crossover then I think consolidating them into one post is better

<@jflory7:fedora.im>

12:42:58

Oh I don't know if I will be able to log into the CommBlog or not 😅

<@jflory7:fedora.im>

12:43:06

I was trying to open a preview of the drafts

<@jflory7:fedora.im>

12:43:51

!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

<@amoloney:fedora.im>

12:44:21

I can access it, but the layout is super weird...probably something on my side

<@amoloney:fedora.im>

12:44:30

Ill take that action

<@jflory7:fedora.im>

12:44:32

Well, this is convenient timing for the first editor roundtable that I can't log into the CommBlog :)

<@jflory7:fedora.im>

12:44:39

Huh! Weird.

<@jflory7:fedora.im>

12:44:57

That was my next thought, about divying up the editing duties

<@jflory7:fedora.im>

12:45:25

I could take the K8s article since I worked on it previously before the author requested to hold.

<@amoloney:fedora.im>

12:45:52

+1 & Ill take the others (as two are possibly the same info)

<@jflory7:fedora.im>

12:46:17

OK! I was going to ask if you wanted me to take the release party one :)

<@amoloney:fedora.im>

12:46:28

if you'd like to you can?

<@jflory7:fedora.im>

12:46:48

I would like to read that one anyways so I can take it

<@amoloney:fedora.im>

12:46:55

perfecto

<@jflory7:fedora.im>

12:47:21

!action JWF Frankfurt Release Party, K8s changes in Rawhide

<@jflory7:fedora.im>

12:47:53

!action amoloney Request CPE + I&R author to consolidate if possible, review + schedule after request

<@jflory7:fedora.im>

12:48:05

And then I think that works through our holiday backlog :)

<@amoloney:fedora.im>

12:48:24

I like your editorial schedule though so lets stick to that

<@amoloney:fedora.im>

12:48:33

indeed it does too!

<@jflory7:fedora.im>

12:48:36

!topic Determine a weekly publishing schedule.

<@jflory7:fedora.im>

12:49:12

!agreed 25 Jan: Frankfurt release party; 30 Jan: CPE 2023 summary; 1 February: K8s changes in Rawhide

<@jflory7:fedora.im>

12:49:32

!topic Q&A for authors about their post.

<@jflory7:fedora.im>

12:49:38

!info No authors present today. Skipping.

<@jflory7:fedora.im>

12:49:45

!topic Administrative decisions to content, organization, and strategy.

<@jflory7:fedora.im>

12:50:16

At some point, I would like to revisit some category and tag reorganization, but this can be post-FOSDEM et al.

<@amoloney:fedora.im>

12:50:34

I am following your lead a little bit here as Im still pretty fresh to this part of the work

<@amoloney:fedora.im>

12:50:53

tag reorg would be nice

<@jflory7:fedora.im>

12:50:59

I am feeling a little rusty TBH, but getting back into a weekly cadence will help a lot with that :)

<@amoloney:fedora.im>

12:51:00

there are a lot built up with past dates

<@amoloney:fedora.im>

12:51:16

do the tags even need to be dated?

<@amoloney:fedora.im>

12:51:23

eg Elections 2019

<@amoloney:fedora.im>

12:51:36

(dont know thats an exact one, but Ive seen a few like that)

<@jflory7:fedora.im>

12:51:40

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

<@amoloney:fedora.im>

12:51:59

darn intergations :)

<@amoloney:fedora.im>

12:52:06

darn integrations :)

<@jflory7:fedora.im>

12:52:06

I think tags can be organized around a date, like for a specific election cycle

<@jflory7:fedora.im>

12:52:21

But WordPress does have a way to view posts by year already

<@jflory7:fedora.im>

12:52:27

So no purpose in duplicating the year only

<@amoloney:fedora.im>

12:52:50

Hmmm, I can see the value for looking up specific posts wth this, but it means generating a new tag every time

<@amoloney:fedora.im>

12:53:02

its a small task though either way so might be a preference thing

<@amoloney:fedora.im>

12:53:19

food for thought methinks

<@jflory7:fedora.im>

12:53:47

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

<@amoloney:fedora.im>

12:53:55

post FOSDEM we should try have a few tasks built up to work on as the Editors group

<@jflory7:fedora.im>

12:54:08

What do you have in mind?

<@amoloney:fedora.im>

12:54:10

so maybe the action here is to create a little backlog of sorts

<@amoloney:fedora.im>

12:54:19

or a kanban board with tickets?

<@amoloney:fedora.im>

12:54:28

ie, check onboarding documentation & update

<@amoloney:fedora.im>

12:54:35

review tag & edi

<@amoloney:fedora.im>

12:54:39

review tag & edit

<@jflory7:fedora.im>

12:54:40

I like that – what would be the right thing to use? GitLab tickets?

<@jflory7:fedora.im>

12:54:49

Not sure if GitLab is overkill or not

<@amoloney:fedora.im>

12:55:07

It might not be

<@amoloney:fedora.im>

12:55:20

would this fit as a subset of another project?

<@amoloney:fedora.im>

12:55:43

maybe the marketing folks would be interested in having this live in their gitlab house?

<@amoloney:fedora.im>

12:55:49

but managed by the editors of course

<@jflory7:fedora.im>

12:56:07

!idea Build up more tasks and a backlog to grow the Editors group, e.g. tickets/issues, a kanban board.

<@jflory7:fedora.im>

12:56:31

Not a bad idea. As a Marketing Team member, it seems like a good fit :)

<@jflory7:fedora.im>

12:56:37

I can ask the team.

<@jflory7:fedora.im>

12:56:48

I do like the idea of perhaps moving to a ticket workflow instead of Fedora Discussion for this

<@amoloney:fedora.im>

12:56:49

thank you :)

<@jflory7:fedora.im>

12:56:59

It would be easier to get some data and metrics about our churn too with GitLab issues

<@jflory7:fedora.im>

12:57:29

!action JWF Ask the Marketing Team if we can launch a new repository for Community Blog review requests and task tracking

<@amoloney:fedora.im>

12:57:31

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

<@jflory7:fedora.im>

12:57:39

True!

<@jflory7:fedora.im>

12:57:55

OK, we have three minutes left… I feel like for a first meeting, we covered good ground :)

<@amoloney:fedora.im>

12:58:04

Same

<@jflory7:fedora.im>

12:58:07

Some of our work is blocked on FAS, but once that is resolved, we will be in business :)

<@amoloney:fedora.im>

12:58:31

its good to be leaving this with some tasks

<@jflory7:fedora.im>

12:58:40

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.

<@amoloney:fedora.im>

12:58:42

so I call it a successful first meeting

<@amoloney:fedora.im>

12:58:54

yeah exactly

<@jflory7:fedora.im>

12:59:00

Aoife Moloney++ Thanks for partnering with me on it!

<@jflory7:fedora.im>

12:59:05

See ya next time :)

<@jflory7:fedora.im>

12:59:07

!endmeeting