#meeting:fedoraproject.org log

<@jflory7:fedora.im>

12:30:03

!startmeeting Community Blog editor roundtable

<@meetbot:fedora.im>

12:30:03

Meeting started at 2024-03-05 12:30:03 UTC

<@meetbot:fedora.im>

12:30:03

The Meeting name is 'Community Blog editor roundtable'

<@jflory7:fedora.im>

12:30:13

!topic Intros, welcomes, hellos

<@jflory7:fedora.im>

12:30:22

!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>

12:30:27

!link https://hackmd.io/@fedora-marketing-team/rJJXxxE66

<@jflory7:fedora.im>

12:30:30

!hi

<@zodbot:fedora.im>

12:30:31

Justin W. Flory (jflory7) - he / him / his

<@roseline:matrix.org>

12:30:52

"!hi"

<@jflory7:fedora.im>

12:31:05

Oh, try without the quotes!

<@amoloney:fedora.im>

12:31:08

!hi

<@zodbot:fedora.im>

12:31:09

Aoife Moloney (amoloney)

<@roseline:matrix.org>

12:31:13

!hi

<@zodbot:fedora.im>

12:31:15

No Fedora Accounts users have the @roseline:matrix.org Matrix Account defined

<@tosin_doreen:matrix.org>

12:31:19

<@jflory7:fedora.im>

12:31:19

zodbot listens for commands that start with `!`

<@roseline:matrix.org>

12:31:39

Okay.

<@jflory7:fedora.im>

12:31:40

And in this case, Roseline Bassey, I think you need to add your Matrix ID to your FAS account over at https://accounts.fedoraproject.org.

<@jflory7:fedora.im>

12:31:48

Then zodbot, our community chat bot, will know who you are :)

<@jflory7:fedora.im>

12:31:54

Hi Aoife Moloney! 👋

<@jflory7:fedora.im>

12:32:01

And hello tosin_doreen! 👋

<@amoloney:fedora.im>

12:32:03

hello, hello

<@roseline:matrix.org>

12:32:13

Will do that now.

<@kanyin:matrix.org>

12:32:33

<@jflory7:fedora.im>

12:32:47

Hi kanyin! 👋

<@jflory7:fedora.im>

12:33:14

Welcome to all the new folks :)

<@jflory7:fedora.im>

12:33:31

In this case, I suggest you can shadow this meeting and see how we run meetings in Fedora.

<@jflory7:fedora.im>

12:33:58

Fedora has run text meetings like this for a long time, because 20 years ago, bandwidth and hardware were not so great for video calls. Things are different now, but we still do a lot of text meetings like this.

<@jflory7:fedora.im>

12:34:25

So, this will give you a bit of a taste of how we do those things and also get to know our Meet Bot. It makes a nice summary of the meeting discussion at the end of the meeting!

<@tosin_doreen:matrix.org>

12:34:28

Very interesting. I'll see how it turns out. Never had a text meeting

<@jflory7:fedora.im>

12:34:30

Aoife Moloney: Shall we? :)

<@amoloney:fedora.im>

12:34:53

Fire ahead!

<@jflory7:fedora.im>

12:34:55

!info Present: jflory7, amoloney, Roseline Bassey, tosin_doreen, kanyin

<@jflory7:fedora.im>

12:35:00

!topic Pending article review

<@jflory7:fedora.im>

12:35:04

!info What We Do: Review the pending queue of Community Blog articles and assign pending posts to an editor.

<@jflory7:fedora.im>

12:35:07

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

<@jflory7:fedora.im>

12:35:20

This is anti-climatic, because we _don't_ have any articles in the queue :)

<@jflory7:fedora.im>

12:35:24

So, I am going to proceed!

<@jflory7:fedora.im>

12:35:33

!info No articles to review today. We are all caught up!

<@jflory7:fedora.im>

12:35:40

!topic Schedule planning '

<@jflory7:fedora.im>

12:35:52

!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>

12:36:03

!info No new articles. Skipping this topic.

<@jflory7:fedora.im>

12:36:10

!topic Administravia

<@jflory7:fedora.im>

12:36:17

!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>

12:36:25

!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>

12:36:36

OK, right…

<@jflory7:fedora.im>

12:37:01

Aoife Moloney: I was thinking, now that we have this meeting going and we are slowly building up a team, it would be nice to tackle the huge backlog of articles in the CommBlog

<@vintprox:envs.net>

12:37:01

Any demand for Meetbot Matrix widget (Element/ShildiChat)? Where there is text user interface, there is a way for GUI.

<@jflory7:fedora.im>

12:37:14

There are two articles pending review, and 57 drafts 😱

<@vintprox:envs.net>

12:37:40

Any demand for Meetbot Matrix widget (Element/ShildiChat)? Where there is text user interface, there is a way for GUI. *(Hope I'm not interrupting anything...)*

<@jflory7:fedora.im>

12:37:50

Some of them are obviously not going to publish, but I always like to reach out to authors before we trash their writing, in case they want to port it out somewhere else. Also, some things may be a good fit for the Fedora Magazine if they are user-focused, and we can coordinate with the Magazine to redirect good content there

<@amoloney:fedora.im>

12:38:08

yeah I agree with that. we had also said we would look at setting up a kanban style board and create issues in for task tracking. I *think* Marketing agreed to let us host a porject under their namespace on gitlab?

<@jflory7:fedora.im>

12:39:27

Huh, weird – my connection blipped there. Back now.

<@jflory7:fedora.im>

12:39:45

vintprox: I saw some bot-related question that is now deleted. Maybe try #zodbot-devel:fedoraproject.org?

<@jflory7:fedora.im>

12:40:09

Yes, I remember Joseph Gayoso and Daimar Stein giving a 👍️ for that :)

<@amoloney:fedora.im>

12:40:53

Great. I will go ahead and create a project now for the task tracking, and job one is divide and conquer the draft backlog then :)

<@amoloney:fedora.im>

12:41:01

We can start with that now though

<@jflory7:fedora.im>

12:41:13

OK, cool! You are okay to tackle that one Aoife?

<@amoloney:fedora.im>

12:41:17

shall we do from top down and see hwo far we get in this meeting?

<@jflory7:fedora.im>

12:41:45

Aoife Moloney: In what sense, porting to the GitLab board or reaching out to articles?

<@jflory7:fedora.im>

12:42:06

My wishlist was that if we could two articles every week, we could make good headway on clearing through the backlog

<@amoloney:fedora.im>

12:42:18

!action amoloney to create project under fedora marketing team namespace in gitlab to track tasks relating to community blog administration & management

<@jflory7:fedora.im>

12:42:27

To start, we could each do one article a week, but if you are doing the GitLab board, I could take the two articles in pending review

<@jflory7:fedora.im>

12:42:29

!link https://communityblog.fedoraproject.org/wp-admin/edit.php?post_status=pending&post_type=post

<@jflory7:fedora.im>

12:43:07

These are the two articles I was eyeing:

<@jflory7:fedora.im>

12:43:13

!info USB Device Emulation. Fedora Magazine candidate?

<@jflory7:fedora.im>

12:43:20

!link https://communityblog.fedoraproject.org/?p=10940&preview=1&_ppp=b8a232af29

<@amoloney:fedora.im>

12:43:25

lets start with your way until we have the board up and running. We can always import the rest when its ready, but we can get going now at least under your suggestion

<@jflory7:fedora.im>

12:43:41

!info Fedora Test Day Working. Check with Sumantro Mukherjee and/or adamw if there is useful/valuable content in this article to keep?

<@jflory7:fedora.im>

12:43:47

!link https://communityblog.fedoraproject.org/?p=9783&preview=1&_ppp=31694ed1b0

<@jflory7:fedora.im>

12:44:27

OK. Admittedly, putting in 57 draft articles spanning all the way back to 2018 might not be the best use of time. But I definitely see the value in setting that up for new articles that we _do_ want to publish.

<@amoloney:fedora.im>

12:44:47

agreed :-)

<@jflory7:fedora.im>

12:44:58

Cool then!

<@jflory7:fedora.im>

12:45:16

So, I will action myself for these two articles to kick off. I will get the emails sent out to the authors before our next roundtable.

<@amoloney:fedora.im>

12:45:40

ack

<@amoloney:fedora.im>

12:45:53

and +1 for the magazine for device emulation

<@jflory7:fedora.im>

12:46:20

!action due:2024-03-12 @jflory7 Reach out to USB Device Emulation and Fedora Test Day Working authors to see if they would still look to work on their drafts, or if they can be moved or trashed.

<@jflory7:fedora.im>

12:46:48

I think this is a good start for today.

<@jflory7:fedora.im>

12:47:35

I am happy with making this our charge for the next week. Aoife Moloney, anything else on administravia before open floor?

<@amoloney:fedora.im>

12:48:44

No the main thing is to set up the board and populate, which I'll take. And you have the reviews, so I think thats the most immediate tasls

<@amoloney:fedora.im>

12:48:48

No the main thing is to set up the board and populate, which I'll take. And you have the reviews, so I think thats the most immediate tasks

<@amoloney:fedora.im>

12:49:08

actually quick Q - when is the next 'available' slot for a community blog post?

<@jflory7:fedora.im>

12:49:31

Oh, yeah.

<@jflory7:fedora.im>

12:49:36

We do have an article publishing on Thursday morning.

<@jflory7:fedora.im>

12:49:42

But tomorrow and Friday are open.

<@jflory7:fedora.im>

12:49:44

What's up?

<@amoloney:fedora.im>

12:49:46

there is one I know will be coming on the changes in how the CPE team will prioritise work

<@jflory7:fedora.im>

12:49:51

Aha

<@amoloney:fedora.im>

12:50:02

I will nab friday for my weekly report

<@jflory7:fedora.im>

12:50:03

I am going to take this to open floor :)

<@jflory7:fedora.im>

12:50:10

!topic Open floor

<@amoloney:fedora.im>

12:50:11

cool

<@jflory7:fedora.im>

12:50:19

!info Topics and all other business that did not fit in elsewhere in the meeting agenda.

<@jflory7:fedora.im>

12:50:36

!info amoloney to publish a weekly report on this Friday, 2024-03-08

<@jflory7:fedora.im>

12:50:53

!info Upcoming article soon about how the CPE team will prioritize their work

<@jflory7:fedora.im>

12:51:13

Aoife Moloney: BTW, one way to check what the schedule looks like is that handy calendar post that Ben set up a while back. Let me see if I can fish out the link.

<@jflory7:fedora.im>

12:51:58

!link https://discussion.fedoraproject.org/t/upcoming-community-blog-commblog-posts/10890

<@jflory7:fedora.im>

12:52:22

Ah, I always forget about the usual Friday column from Infra & Releng

<@amoloney:fedora.im>

12:52:22

Nice, I will bookmark that!

<@jflory7:fedora.im>

12:52:31

But double-posting on that Friday is fine

<@amoloney:fedora.im>

12:52:46

yeah same

<@jflory7:fedora.im>

12:53:13

Aoife Moloney: Any forecast for when the CPE article will come? Or just curious about what the schedule was looking like?

<@jflory7:fedora.im>

12:55:10

Also, quick side note for our shadowing folks. A lot of Fedora meetings will have an "open floor" at the end. This is a general time for anyone to ask questions, discuss topics, or talk about anything that did not come up during the meeting discussion. If you want to add something in open floor, you can alert the meeting chair by using an emoji like ✋ or simply saying that you want to add something :)

<@amoloney:fedora.im>

12:55:37

more curious, but I know @ashcrow is driving it and would like to get it announced sooner rather than later. There are some bootstrapping activities to be done, like creating tags on discourse and a repo somewhere if needed, but they are small enough so I can suggest targeting Thursday

<@amoloney:fedora.im>

12:56:33

Actually I might suggest next Tuesday 12th...there is a communishift article for this thursday

<@amoloney:fedora.im>

12:57:24

doubling up can be fine for reporting-type articles, but both the communishift and cpe change should probably have their own spots

<@jflory7:fedora.im>

12:57:34

Agreed

<@jflory7:fedora.im>

12:57:54

It will also be on the day of our next editor roundtable.

<@amoloney:fedora.im>

12:58:07

something to review!

<@jflory7:fedora.im>

12:58:07

I know we are getting close to our time, so we can coordinate that one asynchronously over in #marketing:fedoraproject.org until next time.

<@jflory7:fedora.im>

12:58:16

Or discuss it that day itself :)

<@amoloney:fedora.im>

12:58:21

ack

<@jflory7:fedora.im>

12:58:26

Yes!

<@jflory7:fedora.im>

12:58:36

OK! So, we are two minutes left until the end of our slot.

<@jflory7:fedora.im>

12:58:46

I think we can wrap here.

<@amoloney:fedora.im>

12:58:46

I have no more :)

<@jflory7:fedora.im>

12:58:52

Then, let's wrap!

<@jflory7:fedora.im>

12:59:15

Thanks Aoife Moloney! And thanks to all of our folks for shadowing along. If you have general questions about meetings, we can chat more over in #marketing:fedoraproject.org :)

<@jflory7:fedora.im>

12:59:18

See ya next time!

<@jflory7:fedora.im>

12:59:19

!endmeeting