<@amoloney:fedora.im>
14:02:42
!startmeeting Fedora Council Meeting
<@meetbot:fedora.im>
14:02:44
Meeting started at 2025-04-09 14:02:42 UTC
<@meetbot:fedora.im>
14:02:44
The Meeting name is 'Fedora Council Meeting'
<@asamalik:fedora.im>
14:02:49
!hi
<@zodbot:fedora.im>
14:02:50
Adam Samalik (asamalik) - he / him / his
<@bookwar:fedora.im>
14:02:52
!hi
<@zodbot:fedora.im>
14:02:53
Aleksandra Fedorova (bookwar) - she / her / hers
<@dcantrell:fedora.im>
14:02:58
!hi
<@jflory7:fedora.im>
14:02:59
!hi
<@zodbot:fedora.im>
14:02:59
David Cantrell (dcantrell) - he / him / his
<@zodbot:fedora.im>
14:03:01
Justin W. Wheeler (jflory7) - he / him / his
<@jonatoni:fedora.im>
14:03:13
!hi
<@zodbot:fedora.im>
14:03:14
Jona Azizaj (jonatoni) - she / her / hers
<@mattdm:fedora.im>
14:03:28
!hi
<@zodbot:fedora.im>
14:03:30
Matthew Miller (mattdm) - he / him / his
<@jflory7:fedora.im>
14:03:58
It is a nice crowd 🙂
<@amoloney:fedora.im>
14:04:03
Cool, this might be one of our main attended in a while!
<@jflory7:fedora.im>
14:04:08
I should have brought birthday cake to our meeting though 🙂
<@jflory7:fedora.im>
14:04:14
Happy birthday Jona Azizaj (she/her) 🎂
<@amoloney:fedora.im>
14:04:39
Aw happy birthday Jona Azizaj (she/her) !!🎉
<@jonatoni:fedora.im>
14:05:13
Thank you 💙🎉
<@jflory7:fedora.im>
14:05:20
!link https://discussion.fedoraproject.org/t/fedora-council-meeting-agenda-2025-04-09/148464
<@jflory7:fedora.im>
14:05:26
^^ Today's agenda, for the curious
<@jflory7:fedora.im>
14:05:48
A git forge update, oh my 🙂
<@darkaxl017:fedora.im>
14:06:16
HBD Jona Azizaj (she/her) !! 🎉🥳🎂
<@dcantrell:fedora.im>
14:06:33
I heard git has been a failure and we are just going back to cvs.
<@dcantrell:fedora.im>
14:06:50
/////////////////////////////////////////////////////////////////
<@mattdm:fedora.im>
14:06:54
I think we should info the agenda rather than link it, so that things don't bitrot in the future. i mean, not that it really matters but it makes the meetbot summary better
<@amoloney:fedora.im>
14:06:58
Well Im putting foward good ole fashioned pen and paper
<@amoloney:fedora.im>
14:07:25
Justin W. Wheeler (@jflory7): are you running todays call or will I?
<@jflory7:fedora.im>
14:07:31
I can run it!
<@amoloney:fedora.im>
14:07:32
*meeting
<@mattdm:fedora.im>
14:07:33
(like, !topic agenda, and then list the things, that's all)
<@asamalik:fedora.im>
14:07:33
cvs?! why have I been proactively emailing tarballs to people then?
<@jflory7:fedora.im>
14:07:34
Let's get going.
<@jflory7:fedora.im>
14:07:42
!topic Follow-ups for today
<@jflory7:fedora.im>
14:07:48
!info Git Forge Update
<@jflory7:fedora.im>
14:07:53
!info Proven Packager incident
<@jflory7:fedora.im>
14:08:01
!info Initiative vote: https://discussion.fedoraproject.org/t/rfc-new-community-initiative-gitops-for-fedora-packaging/146990
<@dcantrell:fedora.im>
14:08:01
you should consider sharballs, they are more portable
<@jflory7:fedora.im>
14:08:06
!topic Git Forge Update
<@jflory7:fedora.im>
14:08:12
Who is chairing this topic?
<@amoloney:fedora.im>
14:08:16
this is my topic
<@jflory7:fedora.im>
14:08:16
Or who has the update? 😄
<@jflory7:fedora.im>
14:08:25
Floor is yours, Aoife Moloney 🙌
<@dcantrell:fedora.im>
14:09:13
(also, the floor is lava)
<@amoloney:fedora.im>
14:09:22
Parcour
<@amoloney:fedora.im>
14:09:56
So the dev team are getting ready to send a communication announcing pagure is no longer available for *new* projects to be hosted
<@amoloney:fedora.im>
14:10:00
https://codeberg.org/fedora/forgejo-deployment/issues/23
<@amoloney:fedora.im>
14:10:36
I owed them an ack from council on this, specifically wording we may want to use in the email and/or on a banner on the pagure.io site
<@amoloney:fedora.im>
14:11:56
I believe its being, or has been, discussed with infra too https://pagure.io/fedora-infra/forgejo-deployment/issue/13
<@mattdm:fedora.im>
14:12:17
ack from me to the email in that messag
<@mattdm:fedora.im>
14:12:25
ack from me to the email in that ticket
<@bookwar:fedora.im>
14:12:51
+1 from me too
<@amoloney:fedora.im>
14:13:22
There will be more comms going out, but this will be the first official 'heads up, this is happening'
<@amoloney:fedora.im>
14:13:48
exciting :)
<@jflory7:fedora.im>
14:14:13
Ryan's specific email, FYI:
<@jflory7:fedora.im>
14:14:15
!link https://codeberg.org/fedora/forgejo-deployment/issues/23#issuecomment-3493760
<@jflory7:fedora.im>
14:14:17
I am +1 to that.
<@jflory7:fedora.im>
14:14:47
Yes, it is!!
<@jflory7:fedora.im>
14:14:50
A long time coming.
<@amoloney:fedora.im>
14:14:59
final thoughts Jona Azizaj (she/her) dcantrell asamalik ?
<@asamalik:fedora.im>
14:15:07
+1 too if this is a vote :)
<@dcantrell:fedora.im>
14:15:08
+1
<@jflory7:fedora.im>
14:15:12
Also, a little nostalgic because Pagure has had quite a 10-year journey 🥹
<@jonatoni:fedora.im>
14:15:15
+1 from me too
<@amoloney:fedora.im>
14:15:31
more of an ack than a vote, but the +1 serves the same purpose in this case :)
<@amoloney:fedora.im>
14:15:52
thanks! Ill let the team know 'Council Approves This Message'
<@jflory7:fedora.im>
14:15:54
pingou++
<@zodbot:fedora.im>
14:15:57
jflory7 gave a cookie to pingou. They now have 319 cookies, 2 of which were obtained in the Fedora 41 release cycle
<@jflory7:fedora.im>
14:16:47
Anything else here, Aoife Moloney?
<@amoloney:fedora.im>
14:17:05
nope, it can have an agreed statement. Ill add it now
<@amoloney:fedora.im>
14:17:59
!agreed Council approves the email communication the Forgejo Dev team have proposed to send to the Fedora community notifying people that pagure.io will no longer be able to host new projects
<@jflory7:fedora.im>
14:18:25
OK. So, congrats all, this was probably the fastest git forge topic in the history of any Fedora Council meeting ever.
<@jflory7:fedora.im>
14:18:28
🏆️
<@jflory7:fedora.im>
14:18:32
Let's keep plugging along.
<@jflory7:fedora.im>
14:18:43
!topic Proven Packager incident
<@amoloney:fedora.im>
14:18:49
this one is mine too
<@jflory7:fedora.im>
14:18:57
The lava floor is back to you 🙂
<@amoloney:fedora.im>
14:19:23
I guess Im a glutton for punishment 🙊
<@amoloney:fedora.im>
14:21:01
this is very quick - I have started a draft for the councils official statement on the topic. I meant to have something in place last week, but life I guess. Apologies. Its in a google doc, I will share it with you all now via the google doc and my aim is to have something to send to FESCo members and Peter Robinson to have a read of first before we publish it by early next week
<@dcantrell:fedora.im>
14:21:20
sounds good to me
<@amoloney:fedora.im>
14:21:28
All going well, we should try get this published by April 18?
<@jflory7:fedora.im>
14:21:44
+1 from me
<@mattdm:fedora.im>
14:22:08
sounds good
<@mattdm:fedora.im>
14:22:16
and thanks, Aoife!
<@amoloney:fedora.im>
14:22:26
no problem at all
<@jflory7:fedora.im>
14:22:55
Was this the only update though?
<@jflory7:fedora.im>
14:23:00
Or do you need input from us?
<@amoloney:fedora.im>
14:23:08
yeah that was it, no action needed, just an FYI
<@jflory7:fedora.im>
14:23:19
Ah, okay.
<@jflory7:fedora.im>
14:23:27
Well, anyone else have something to add for this topic?
<@jflory7:fedora.im>
14:23:32
Otherwise, we will keep plugging along.
<@jflory7:fedora.im>
14:23:39
I'll write some summaries for the minutes meanwhile.
<@jflory7:fedora.im>
14:24:20
!info @amoloney is working on a draft with an official statement. Currently it is in a Google Doc and open to feedback with other Council members. Next, it will go to FESCo members and Peter Robinson before review. The targeted publication date is April 18th.
<@jflory7:fedora.im>
14:24:45
!info Thanks @amoloney for pushing this important communication forward.
<@jflory7:fedora.im>
14:25:14
!topic New Community Initiative discussion & vote
<@jflory7:fedora.im>
14:25:17
!link https://discussion.fedoraproject.org/t/rfc-new-community-initiative-gitops-for-fedora-packaging/146990
<@jflory7:fedora.im>
14:25:34
bookwar: This one is you, I think?
<@amoloney:fedora.im>
14:26:11
this is a follow up from last meeting. Council asked for more time to read the proposal before we vote, so I assume everyone is now in a better position to vote?
<@amoloney:fedora.im>
14:26:20
I am +1 to this initiative
<@mattdm:fedora.im>
14:26:45
Justin, are you still -1?
<@jflory7:fedora.im>
14:27:01
I am looking in the proposal for details about communication milestones
<@jflory7:fedora.im>
14:27:09
Any feedback on my feedback last time?
<@mattdm:fedora.im>
14:27:37
is bookwar here?
<@bookwar:fedora.im>
14:27:42
Yes
<@jflory7:fedora.im>
14:27:54
I see the last edit to the proposal was Matthew on March 18th
<@mattdm:fedora.im>
14:27:56
Then I will let you speak for yourself :)
<@bookwar:fedora.im>
14:29:01
My understanding of the current state is that: I don't want to add communication work council must do for itself into the initiative
<@bookwar:fedora.im>
14:29:45
This should be part of the generic Council initiave process, where we announce council decisions and keep the community uptodate on what current active council initiatives are
<@jflory7:fedora.im>
14:30:20
Can we identify what that communication work is?
<@jflory7:fedora.im>
14:30:50
As I understand the process today, this is not part of the Council Initiative process and was one of the biggest challenges we have had with our two previous and one ongoing Initiative too
<@jflory7:fedora.im>
14:31:13
We need some accountability for the communication work somewhere
<@mattdm:fedora.im>
14:31:37
I agree with both of you. We should have this, but we should add it to an SOP for https://docs.fedoraproject.org/en-US/project/initiatives/, rather than to each initiative
<@jflory7:fedora.im>
14:31:59
We still have to take a vote on this today, though.
<@mattdm:fedora.im>
14:32:01
Maybe this is something CommOps can draft?
<@jflory7:fedora.im>
14:32:26
CommOps hasn't been included on this proposal? I am mindful that we are trying to gear up on Flock and Mentor Summit right now too.
<@jflory7:fedora.im>
14:32:48
I need to know that this work is going to be under active consideration and not deferred until it is either forgotten or too late.
<@jflory7:fedora.im>
14:33:00
I need to know that this communication work is going to be under active consideration and not deferred until it is either forgotten or too late.
<@jflory7:fedora.im>
14:33:09
Who takes accountability?
<@amoloney:fedora.im>
14:33:21
who is the council sponsor for this initiative?
<@bookwar:fedora.im>
14:33:28
Justin W. Wheeler (@jflory7): We need to separate the topics of how Council handles the initiative and "what are the work items within the initiative"
<@bookwar:fedora.im>
14:33:39
Justin W. Wheeler (@jflory7): We need to separate the topics of how Council handles initiatives and "what are the work items within the initiative"e
<@mattdm:fedora.im>
14:33:48
It's me. I'm the sponsor it's me.
<@jflory7:fedora.im>
14:34:17
Communication about a change as large as this should be a work item. I don't know who should own it, but it needs to be accounted for and explicitly present.
<@amoloney:fedora.im>
14:34:30
ok, exec sponsor should work with this team to make sure communication milestones are in place and looked after
<@jflory7:fedora.im>
14:34:35
I have just seen us charge forward too many times over the years without a plan of how we will talk about big change with the community 🤷♂️
<@mattdm:fedora.im>
14:34:47
Agreed, but let's separate it.
<@jflory7:fedora.im>
14:34:55
Sometimes those decisions end up causing expensive problems later.
<@dcantrell:fedora.im>
14:34:55
Our anti-hero.
<@jflory7:fedora.im>
14:35:38
At the current moment, I am still -1 because I don't feel like any of my concerns were accounted for or addressed. This was the #1 thing for me.
<@amoloney:fedora.im>
14:35:50
so mattdm I trust you will follow up and do some due diligence with bookwar and those working on this initiative that there'll be appropriate communication
<@jflory7:fedora.im>
14:36:35
All I want for my +1 is some accountability and advance identification of what appropriate communication looks like and what it is supposed to mean.
<@amoloney:fedora.im>
14:36:49
As a reminder, I believe this came up the last time and its important to note that this work is investigatory
<@amoloney:fedora.im>
14:37:02
bookwar: correct me if Im wrong
<@bookwar:fedora.im>
14:37:24
Aoife Moloney: you are right. The initiative on its own does not create a change
<@amoloney:fedora.im>
14:37:25
I understood that this work needs to be investigated first and proved viable before a larger, more permanent change happpens
<@jflory7:fedora.im>
14:37:33
Because it is investigatory and the community has strong opinions about this, it reinforces my belief that communication planning is critical
<@jflory7:fedora.im>
14:38:05
Somehow, we need to talk about this work as we go instead of doing it in a silo and then presenting a finished product
<@bookwar:fedora.im>
14:38:07
It is not clear to me what kind of work item we are supposed to request from CommOps team, which is also already known to be overwhelmed with all other tasks
<@jflory7:fedora.im>
14:38:30
I am confused about how CommOps came into this frankly, because I thought the challenge others had was that the communication should be a Council-owned thing.
<@jflory7:fedora.im>
14:38:32
Now it is CommOps?
<@mattdm:fedora.im>
14:38:35
I will take accountability for making sure that good communications happen.
<@jflory7:fedora.im>
14:38:35
I am not following this.
<@jflory7:fedora.im>
14:38:55
mattdm: I want a plan.
<@mattdm:fedora.im>
14:39:00
I brought up CommOps as possibly helping us draft a standard comms plan for initiatives
<@mattdm:fedora.im>
14:39:17
But if that group isn't the right place to do it, we can do that at a council level.
<@jflory7:fedora.im>
14:39:20
I see. That could potentially be a fit, but that is not going to solve the issue we have right now
<@bookwar:fedora.im>
14:39:40
There is a plan. It includes communication steps required to request feedback about the initiative from the community
<@amoloney:fedora.im>
14:39:44
this issue is a bit silly to me to block on
<@mattdm:fedora.im>
14:39:45
Are the things you see as _particularly specific_ to this initiative? That's where I'm a little lost.
<@jflory7:fedora.im>
14:40:12
<@jflory7:fedora.im>
14:40:12
This is the only detail I see about communication in the proposal:
<@jflory7:fedora.im>
14:40:12
> "Support for presenting the work at Flock and other relevant places and collecting feedback"
<@jflory7:fedora.im>
14:40:26
This is super vague 😕
<@bookwar:fedora.im>
14:40:30
February, FOSDEM 2026 - Collect feedback, present the result, and propose next steps at CentOS Connect or Distribution Devroom.
<@bookwar:fedora.im>
14:40:30
August 15, 2025 - Announce the work on Fedora Magazine and start the feedback gathering
<@bookwar:fedora.im>
14:40:36
There are two items ^^
<@jflory7:fedora.im>
14:43:07
I guess I want to see a gradual onramp of increased communication as things are either successful or unsuccessful.
<@jflory7:fedora.im>
14:43:07
<@jflory7:fedora.im>
14:43:07
- How is feedback going to be transparently collected? Is this going to happen in the public or in Red Hat internal ticketing systems? Where is the community engagement piece?
<@jflory7:fedora.im>
14:43:07
- Specific stakeholders to collect feedback from other than "community". Who do we involve at different points? Different groups of contributors have different feedback. We don't always need to do something massively public, as much as it is talk to specific stakeholders, packagers, or leaders in the community.
<@jflory7:fedora.im>
14:43:07
<@jflory7:fedora.im>
14:43:07
I am pretty sure I provided something like this last time in the Council meeting, but off the top of my head, here are some specifics:
<@jflory7:fedora.im>
14:44:18
I don't like it when we say "ask the community for feedback" because that does not seem to account for how wide and spread-out our community is. For instance, there are different things you post to the Magazine from what goes to devel@
<@mattdm:fedora.im>
14:44:40
that's fair
<@jflory7:fedora.im>
14:44:41
I just feel like we are setting ourselves up for challenges when we are already going through so many huge changes at once
<@jflory7:fedora.im>
14:44:53
We need to make sure we are not giving the community whiplash
<@jflory7:fedora.im>
14:45:07
I remember a comment someone shared about a notable Python packager who felt like he has no idea how the project collaborates anymore
<@jflory7:fedora.im>
14:45:14
And I felt that one
<@jflory7:fedora.im>
14:45:21
This is something that touches on that specific in my eyes
<@mattdm:fedora.im>
14:45:50
<@mattdm:fedora.im>
14:45:50
So
<@mattdm:fedora.im>
14:45:50
<@mattdm:fedora.im>
14:45:50
"* August 15, 2025 - Announce the work on Fedora Magazine and start the feedback gathering from packagers and the infrastructure team"
<@mattdm:fedora.im>
14:45:50
and "feedback will be collected through an initiative-specific tag on discourse"
<@mattdm:fedora.im>
14:46:34
and maybe "significant findings from investigation and feedback will be tracked in a forgejo project"
<@jflory7:fedora.im>
14:47:27
I know this is frustrating, but I also hope that you can see my perspective of how we have handled (and often fumbled) communicating about really big shifts on how we collaborate and work together as a community. I am not going to change my vote until I see something in writing on the proposal. I was a little disappointed that we had this long conversation last time, and it took until this moment in this meeting for it to come up that my feedback was vetoed and decided it was not relevant.
<@jflory7:fedora.im>
14:47:33
I wish we had this conversation weeks ago 😕
<@bookwar:fedora.im>
14:48:28
We had discussed it. And I did ask explicitly to put the suggestions you have into the thread on Discourse
<@jflory7:fedora.im>
14:48:54
mattdm: Those things are improvements, yes. I would like to see at least a few more things integrated into the timeline.
<@jflory7:fedora.im>
14:49:16
I'm sorry, I must have missed that action. I can take some accountability myself and get this feedback articulated in the Discourse thread.
<@amoloney:fedora.im>
14:49:42
Id wager this is more discourse v email than much else. but thats a topic for another day
<@jflory7:fedora.im>
14:49:57
Hah, yeah, Discourse still hurts me but I won't get into that either 😛
<@bookwar:fedora.im>
14:50:15
Currently you are going a bit too deep in the details, to my taste. I am not expected to write which bug tracker I am going to use to track this initiative in the initiative proposal. The same way - I am not specifying which exact category the communication should go into.
<@jflory7:fedora.im>
14:50:53
I don't expect you to tell me which git repo or bug tracker you will use to collect feedback, but I expect to know from whom you will collect feedback, when you will start collecting feedback, and at about what times you are expecting input from people in the community
<@bookwar:fedora.im>
14:51:02
The initiative has multiple stakeholders, users, contributors, packagers, developers, and infrastructure people. Yes, gathering feedback from the community means all of them
<@jflory7:fedora.im>
14:51:06
Because people will want to know, and for me, I want to know where to direct people at what points
<@amoloney:fedora.im>
14:51:12
Im pretty sure the 'mode of communication' was going to be discourse anyway
<@amoloney:fedora.im>
14:51:24
I dont get why this needs to be spelled out in an investigation phase
<@jflory7:fedora.im>
14:51:25
But that is too much at once, it is overwhelming to try to talk to everyone at once.
<@bookwar:fedora.im>
14:51:27
Do i know exactly which channel I am going to use right now - I am not sure I have to write it down to every single one
<@jflory7:fedora.im>
14:51:41
That is not what I am looking for
<@jflory7:fedora.im>
14:51:44
Now it is going too deep
<@bookwar:fedora.im>
14:51:50
That's why I have several months allocated for this work
<@mattdm:fedora.im>
14:52:23
<@mattdm:fedora.im>
14:52:23
Council will need some additional time to review this proposal, but do support the investigation into an alternative git-based workflow for packaging, however we are reluctant to approve it yet without a clearer understanding of the 'grand end goal' of this work and need more communication milestones to exist as part of the proposal. We will make a formal decision on this at the next council meeting on April 9th and engage with the proposers for additional context in the discussion thread in the meantime
<@mattdm:fedora.im>
14:52:23
FWIW what we agreed on was:
<@jflory7:fedora.im>
14:52:26
I'd like to break it down into smaller pieces around communication. The technical work is well-represented in this way but I see the piece about integrating community feedback milestones in the proposal as critical
<@asamalik:fedora.im>
14:53:14
The way I see this, it's an investigation. It's not changing anything for anyone.
<@asamalik:fedora.im>
14:53:14
<@asamalik:fedora.im>
14:53:14
In my opinion this gives way less pressure about having refined communication plans before this even starts. By definition, an investigation can go multiple ways, attracting different people with different problems etc. So I'm personally quite OK with it being open like this.
<@asamalik:fedora.im>
14:53:14
<@asamalik:fedora.im>
14:53:14
It starts with "The goal of the initiative is to explore the possibility to..." which makes that super clear.
<@jflory7:fedora.im>
14:53:17
That looks right mattdm but I don't see the communication milestones as part of the proposal
<@mattdm:fedora.im>
14:54:08
Since you were the one advocating for those,we were kind of of waiting for you to provide more detail in the discussion thread
<@jflory7:fedora.im>
14:54:15
I want to know who is being included when 😕
<@jflory7:fedora.im>
14:54:29
I missed the action that I was supposed to reply on Fedora Discussion
<@mattdm:fedora.im>
14:54:30
I am still not sure what exactly you mean by "communications milestones"
<@amoloney:fedora.im>
14:54:34
bookwar: can you stick in 'Announcing the investigation' and then 'reminder about feedback deadline' and 'publishing of feedback' as a few milestones? Is that good enough for an *investigation*?
<@mattdm:fedora.im>
14:54:47
Like, can you give an example of what one would look like?
<@jflory7:fedora.im>
14:55:22
These are my unanswered questions
<@bookwar:fedora.im>
14:55:26
I do treat "gathering feedback" as big part of an actual work on that initiative. It is definitely not just code it, run it, and say "done". And I think it is reflected in the timeline. I can adjust the wording around it, but this is where I am looking for explicit suggestions.
<@mattdm:fedora.im>
14:56:00
From that...
<@mattdm:fedora.im>
14:56:00
<@mattdm:fedora.im>
14:56:00
Actions to improve initiatives
<@mattdm:fedora.im>
14:56:00
<@mattdm:fedora.im>
14:56:00
Add requirements to initiatives page, similar to Editions promotion
<@mattdm:fedora.im>
14:56:00
[??] Create a playbook for a lead to follow when running an initiative
<@mattdm:fedora.im>
14:56:00
[Jason] Create a playbook for exec sponsor to follow for initatives
<@mattdm:fedora.im>
14:56:07
ping Jason Brooks :)
<@amoloney:fedora.im>
14:56:14
those are not milestones. they're open quesitons
<@amoloney:fedora.im>
14:56:23
those are not milestones. they're open questions
<@mattdm:fedora.im>
14:56:55
Also from the council hackfest, we said that we want a weekly update on each initiative posted to DIscussion
<@jflory7:fedora.im>
14:56:56
- "Include input and interviews with proven packages in Month X"
<@jflory7:fedora.im>
14:56:56
- "Invite feedback over 2-3 weeks around Month Y in a public discussion with the development community on devel@ and Fedora Discussion"
<@jflory7:fedora.im>
14:56:56
- "Create documentation about ongoing findings of the investigatory work by Month Z"
<@amoloney:fedora.im>
14:57:17
thats a timeline
<@amoloney:fedora.im>
14:57:19
not milestones
<@bookwar:fedora.im>
14:57:20
If change the word 'community' to 'community: users, contributors, packagers, developers, and infrastructure people', will it be enough?
<@mattdm:fedora.im>
14:57:47
so that's the _start_ of a standards comms SoP
<@jflory7:fedora.im>
14:57:59
No, the community definition is too broad. I really want to know who we are talking with when. A proven packager is going to have very different feedback on this than an everyday user
<@bookwar:fedora.im>
14:58:03
I honestly just don't get the core argument, so if you'd like a change, please work _with_ me on what exactly the change should be.
<@amoloney:fedora.im>
14:58:16
I owe some work to the initiatives process from the hackfest so I will take ownership of that
<@asamalik:fedora.im>
14:58:21
that's quite a specific window for feedback
<@asamalik:fedora.im>
14:58:21
August 15, 2025 - Announce the work on Fedora Magazine and start gathering feedback ...
<@asamalik:fedora.im>
14:58:21
February, FOSDEM 2026 - Collect feedback, present the result, and propose next steps...
<@asamalik:fedora.im>
14:58:21
<@asamalik:fedora.im>
14:58:21
It says:
<@asamalik:fedora.im>
14:58:21
<@jflory7:fedora.im>
14:58:29
This might be better over A/V than text, because I feel like I am trying to work with y'all on this but maybe we are communicating past each other 😕
<@asamalik:fedora.im>
14:58:55
I really hope this won't get withdrawn out of frustration, because it's trying to explore an interesting thing.
<@mattdm:fedora.im>
14:58:57
thanks Aoife. But let's not let Jason off the hook completely :)
<@amoloney:fedora.im>
14:59:06
Ill tag him
<@jflory7:fedora.im>
14:59:10
Feedback from who? Feedback on what? The whole world? 😕
<@amoloney:fedora.im>
14:59:13
and I agree
<@bookwar:fedora.im>
14:59:23
I think it is better to work on Discourse. Ssuggest the edits as you see fit, and I will incorporate them in the text.
<@amoloney:fedora.im>
14:59:24
this is becoming really ridiculous
<@mattdm:fedora.im>
14:59:43
I have already edited it to say " Announce the work on Fedora Magazine and start gathering feedback from Fedora packagers and from Infrastructure, Release Engineering, and Quality Teams"
<@asamalik:fedora.im>
14:59:45
also, time over, we have to free this channel
<@asamalik:fedora.im>
14:59:51
we have 12 seconds
<@jflory7:fedora.im>
14:59:53
I also agree, because I value the work and I think it would have a positive impact. But I don't want to leave our community behind when we are already making so many huge changes in a relatively short time
<@asamalik:fedora.im>
14:59:56
there's a meeting right after us
<@jflory7:fedora.im>
15:00:12
OK. I also have to drop for another meeting too
<@amoloney:fedora.im>
15:00:30
!endmeeting