<@jflory7:fedora.im>
11:34:03
!startmeeting Community Blog editor roundtable
<@meetbot:fedora.im>
11:34:03
Meeting started at 2024-04-02 11:34:03 UTC
<@meetbot:fedora.im>
11:34:03
The Meeting name is 'Community Blog editor roundtable'
<@amoloney:fedora.im>
11:34:16
!hi
<@zodbot:fedora.im>
11:34:18
Aoife Moloney (amoloney)
<@jflory7:fedora.im>
11:34:23
!topic Intros, welcomes, hellos
<@jflory7:fedora.im>
11:34:30
!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:35
!link https://hackmd.io/@fedora-marketing-team/rJJXxxE66
<@jflory7:fedora.im>
11:34:42
Howdy Aoife Moloney! 👋
<@amoloney:fedora.im>
11:34:56
Hi Justin W. Flory (he/him) ! Hope you had a lovely weekend :)
<@jflory7:fedora.im>
11:35:48
Thanks, I did! I made a decent effort at not spending it on xz 😅 I hope yours was also pleasant!
<@roseline:matrix.org>
11:36:34
!hi
<@zodbot:fedora.im>
11:36:35
Roseline Bassey (roseline-bassey) - she / her / hers
<@omooba1:matrix.org>
11:36:46
Hi!. Justin W. Flory (he/him): I you're fine
Will be glad to learn and enjoy the moment
<@jflory7:fedora.im>
11:36:47
Hey Roseline Bassey! 👋
<@omooba1:matrix.org>
11:37:01
> <@jflory7:fedora.im> !link https://hackmd.io/@fedora-marketing-team/rJJXxxE66
Hi!. Justin W. Flory (he/him): I hope you're fine
Will be glad to learn and enjoy the moment
<@jflory7:fedora.im>
11:37:12
ThePerfectPlace: Sure, you are welcome to join along! The flow and style of this meeting is described in the HackMD pad :)
<@jflory7:fedora.im>
11:37:28
Speaking of which, let's go ahead and get into the agenda since this is a short meeting :)
<@jflory7:fedora.im>
11:37:41
!hi ThePerfectPlace
<@zodbot:fedora.im>
11:37:43
EMMANUEL KOMOLAFE (omooba1) - he / him / his
<@roseline:matrix.org>
11:37:49
Hey, Justin W. Flory (he/him) Great to be here again!
<@jflory7:fedora.im>
11:38:03
!info Present: @jflory7, @amoloney, @roseline-bassey, @omooba1
<@jflory7:fedora.im>
11:38:08
!topic Pending article review
<@jflory7:fedora.im>
11:38:14
!info What We Do: Review the pending queue of Community Blog articles and assign pending posts to an editor.
<@jflory7:fedora.im>
11:38:18
!link https://discussion.fedoraproject.org/c/workflows/community-blog-review/79
<@jflory7:fedora.im>
11:38:36
I did an editor pass yesterday on articles
<@jflory7:fedora.im>
11:38:50
One published this morning, Matthew's LWN article publishes Thursday.
<@jflory7:fedora.im>
11:39:01
Fedora Council flurry of messages presumably begin from next week.
<@jflory7:fedora.im>
11:39:08
There are two articles I am thinking to defer to the Magazine.
<@amoloney:fedora.im>
11:39:16
Is that better in the Magazine? the LWN one
<@jflory7:fedora.im>
11:39:47
Aoife Moloney: For that one specifically, I think no, because it is a contributor-specific discount and we only have two slots. The reach on Magazine is more broad than the CommBlog
<@amoloney:fedora.im>
11:39:48
we have the git forge piece publishing thurs on the commnblog according to your and I's calendar tasks
<@amoloney:fedora.im>
11:40:04
ahh ok, makes ense
<@jflory7:fedora.im>
11:40:10
Oh wait. I thought that was going Tue April 9th?
<@amoloney:fedora.im>
11:40:11
ahh ok, makes sense
<@jflory7:fedora.im>
11:40:27
It is foreseeable that I have that wrong
<@amoloney:fedora.im>
11:40:52
it had to be written by thurs, I thought it was being published
<@amoloney:fedora.im>
11:41:01
I do think we should publish it this week though
<@jflory7:fedora.im>
11:41:23
OK. We could slide the LWN article around as needed.
<@amoloney:fedora.im>
11:41:35
could that go tomorrow?
<@jflory7:fedora.im>
11:41:42
I was thinking so
<@amoloney:fedora.im>
11:41:48
or is that too much content per week?
<@jflory7:fedora.im>
11:42:03
Next couple of weeks will be busy and we are planning some major comms in the next couple of weeks
<@omooba1:matrix.org>
11:42:06
Checking this right away
Hope to get along 💯
<@jflory7:fedora.im>
11:42:34
Nah, it is fine. 2-3 articles is a loose guideline, but if we have more content in a week, it's fine
<@jflory7:fedora.im>
11:42:42
Let me go and adjust the LWN article now for tomorrow.
<@amoloney:fedora.im>
11:42:50
+1
<@jflory7:fedora.im>
11:44:04
!link https://discussion.fedoraproject.org/t/review-publish-lwn-subscription-slots-available-for-fedora-contributors/108129/3
<@jflory7:fedora.im>
11:44:05
Done.
<@jflory7:fedora.im>
11:44:36
!agreed Bumped the LWN article to Wednesday to account for the git forge announcement coming on Thursday.
<@jflory7:fedora.im>
11:45:22
As for other pending articles, there are two, but I think they are better fits on the Magazine
<@jflory7:fedora.im>
11:45:30
I see there is a conversation unfolding in one of them as we speak :)
<@jflory7:fedora.im>
11:45:36
!link https://discussion.fedoraproject.org/t/review-publish-how-to-rebase-to-fedora-silverblue-40-beta/109793/3
<@amoloney:fedora.im>
11:45:38
yeah I was just skimming through them
<@jflory7:fedora.im>
11:45:51
!link https://discussion.fedoraproject.org/t/review-publish-automation-through-accessibility/108070/3
<@jflory7:fedora.im>
11:46:30
I don't think anything else is pending action in the editor queue right now, though.
<@jflory7:fedora.im>
11:46:43
I have started to follow up with authors on unfinished drafts.
<@jflory7:fedora.im>
11:46:58
I scheduled two follow-ups that sent this morning to two authors with old articles.
<@jflory7:fedora.im>
11:47:20
(I want to leave some time for open floor this time, so I am going to bump us forward to the schedule confirmation)
<@jflory7:fedora.im>
11:47:21
!topic Schedule planning
<@jflory7:fedora.im>
11:47:28
!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:33
!link https://discussion.fedoraproject.org/t/upcoming-community-blog-commblog-posts/10890
<@jflory7:fedora.im>
11:47:40
Here is how it is looking then…
<@jflory7:fedora.im>
11:48:06
!info 2024-04-02: Join us! Restarting Community Ops team meetings in 2024
<@jflory7:fedora.im>
11:48:19
!info 2024-04-03: LWN subscription slots available for Fedora contributors
<@jflory7:fedora.im>
11:48:43
!info 2024-04-04: Git forge announcement (pending)
<@jflory7:fedora.im>
11:48:58
Aoife Moloney: Where did we record the list of articles in the next two weeks? Council meeting minutes?
<@jflory7:fedora.im>
11:49:08
I am trying to remember what my source of truth was for that timeline 😅
<@amoloney:fedora.im>
11:49:13
for the hackfest write up
<@amoloney:fedora.im>
11:49:16
for the hackfest write up?
<@jflory7:fedora.im>
11:49:22
Right.
<@amoloney:fedora.im>
11:49:24
If so, yes its in a meeting log
<@amoloney:fedora.im>
11:49:27
Ill fish it out
<@jflory7:fedora.im>
11:50:07
I think here? https://discussion.fedoraproject.org/t/fedora-council-meeting-agenda-2024-03-13/107997/4
<@amoloney:fedora.im>
11:50:27
yep am in the logs
<@jflory7:fedora.im>
11:50:31
Who, but not when!
<@amoloney:fedora.im>
11:50:48
hahaha I know!
<@jflory7:fedora.im>
11:50:49
> AGREED: Tentatively aiming for the weeks of April 8th - 26th to run our Council Hackfest mini-series posts. Authors should come with a first go or full draft of their content by the Council meeting on 27 March. We will build out scheduling for the posts based on what is furthest along and urgency of topic. (@jflory7:fedora.im, 14:52:37)
<@amoloney:fedora.im>
11:50:58
the closest we came was that
<@jflory7:fedora.im>
11:51:13
I thought April 9th and April 11th were our first targeted days, with git forge and Strategy prioritized first
<@amoloney:fedora.im>
11:51:14
technically....we are still on track :)
<@jflory7:fedora.im>
11:51:30
If we want to do git forge this week, that's early, but it is fine.
<@amoloney:fedora.im>
11:51:38
yeah but if the git forge piece is ready I wouldnt wait
<@jflory7:fedora.im>
11:51:43
Agreed
<@jflory7:fedora.im>
11:52:14
OK. In interest of time, I will note a Fedora Strategy article from mattdm for next week too, but we can follow up in next week's roundtable.
<@amoloney:fedora.im>
11:52:39
ha exactly! was just typing that 😅
<@jflory7:fedora.im>
11:52:41
!info Next week: A Fedora Strategy article from @mattdm and possibly another Council communication.
<@jflory7:fedora.im>
11:52:59
So, I'm feeling good about our schedule :)
<@jflory7:fedora.im>
11:53:17
I think this is the main agenda for today, was to check in on this
<@jflory7:fedora.im>
11:53:24
I don't think there is any administravia to cover today
<@amoloney:fedora.im>
11:53:50
no I still owe some work to our issue tracking board too
<@jflory7:fedora.im>
11:54:04
!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:18
Do you want to discuss it now, or an action for next time?
<@amoloney:fedora.im>
11:54:51
theres not too much to discuss, other than I need to pad it out with some tickets
<@amoloney:fedora.im>
11:55:00
I only have 2 in there as of now :/
<@jflory7:fedora.im>
11:55:34
!topic Administravia
<@amoloney:fedora.im>
11:55:35
But! someone has asked to be assigned to one of them! So the 'if you build it, they will come' is showing it works :)
<@jflory7:fedora.im>
11:55:39
!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:45
!link https://gitlab.com/fedora/marketing/commblog/-/issues
<@jflory7:fedora.im>
11:56:30
Hahah, in rare cases, it happens. :) I think that task is very ambitious though, maybe I can add sub-tasks with more articles later.
<@jflory7:fedora.im>
11:56:57
!info Some tickets are there in GitLab, but we will need to integrate this more into our workflow. A topic for next week?
<@amoloney:fedora.im>
11:57:17
yes definitely
<@jflory7:fedora.im>
11:57:38
Sounds good to me.
<@amoloney:fedora.im>
11:58:11
can you add a topic to discuss formalizing the workflow now that we have the tools please? Eg, how does the tracker board and discourse and this meeting all fit together
<@amoloney:fedora.im>
11:58:45
I might open a ticket for it too for discussion before next meeting
<@jflory7:fedora.im>
11:58:56
!action @jflory7 Add topic for next week on formalizing the CommBlog workflow
<@jflory7:fedora.im>
11:59:06
Let's plan for this to be the primary topic next week
<@jflory7:fedora.im>
11:59:24
And we will dedicate the time to it.
<@amoloney:fedora.im>
11:59:52
sounds good to me!
<@jflory7:fedora.im>
11:59:59
Excellent!
<@jflory7:fedora.im>
12:00:27
We are at the end of the half hour, and we need to yield the meeting room. I wanted to save room for open floor but these 30 minutes go fast 😅
<@jflory7:fedora.im>
12:00:42
I'll wrap it up here for now.
<@jflory7:fedora.im>
12:00:48
Thanks for participating today!
<@jflory7:fedora.im>
12:00:54
See ya next time.
<@jflory7:fedora.im>
12:00:57
!endmeeting