Hi,
According to the schedule[1], the voting period was supposed to begin on Friday, but elections.fedoraproject.org does not list any open elections yet. Does anyone have an ETA for when voting will start?
Thanks, Tom
[1] https://fedorapeople.org/groups/schedule/f-38/f-38-elections-tasks.html
On Wed, May 24, 2023, at 12:03 PM, Tom Stellard wrote:
Hi,
According to the schedule[1], the voting period was supposed to begin on Friday, but elections.fedoraproject.org does not list any open elections yet. Does anyone have an ETA for when voting will start?
I'm pretty sure we no longer have a program manager? So I'm kinda expecting a lot of things to just silently break. I don't know what the fallback plan is.
Am 24.05.2023 um 20:30 schrieb Chris Murphy lists@colorremedies.com:
I'm pretty sure we no longer have a program manager?
What’s that about?
-- Peter Boy https://fedoraproject.org/wiki/User:Pboy PBoy@fedoraproject.org
Timezone: CET (UTC+1) / CEST /UTC+2)
Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast
On Wed, May 24, 2023, at 2:55 PM, Peter Boy wrote:
Am 24.05.2023 um 20:30 schrieb Chris Murphy lists@colorremedies.com:
I'm pretty sure we no longer have a program manager?
What’s that about?
As I understand it, part of recent Red Hat layoffs. Red Hat and Fedora program/project managers were impacted.
And also no emails or matrix messages from Ben Cotton in two weeks. He is the one who announces elections and sets up that whole system, reports the results, updates everything related to the subsequent changes, etc.
That's all I know.
On Wed, May 24, 2023 at 2:55 PM Peter Boy pboy@uni-bremen.de wrote:
Am 24.05.2023 um 20:30 schrieb Chris Murphy lists@colorremedies.com:
I'm pretty sure we no longer have a program manager?
What’s that about?
Red Hat recently announced a round of layoffs[1] and the Fedora Program Manager role was impacted.
Ben posted this blog: https://funnelfiasco.com/blog/2023/05/12/inaction-bcotton/
josh
[1] https://www.redhat.com/en/blog/message-red-hat-associates-today
On 5/24/23 12:19, Josh Boyer wrote:
On Wed, May 24, 2023 at 2:55 PM Peter Boy pboy@uni-bremen.de wrote:
Am 24.05.2023 um 20:30 schrieb Chris Murphy lists@colorremedies.com:
I'm pretty sure we no longer have a program manager?
What’s that about?
Red Hat recently announced a round of layoffs[1] and the Fedora Program Manager role was impacted.
Ben posted this blog: https://funnelfiasco.com/blog/2023/05/12/inaction-bcotton/
What's the process for selecting a new Program Manager?
-Tom
josh
[1] https://www.redhat.com/en/blog/message-red-hat-associates-today _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Wed, May 24, 2023 at 3:23 PM Tom Stellard tstellar@redhat.com wrote:
On 5/24/23 12:19, Josh Boyer wrote:
On Wed, May 24, 2023 at 2:55 PM Peter Boy pboy@uni-bremen.de wrote:
Am 24.05.2023 um 20:30 schrieb Chris Murphy lists@colorremedies.com:
I'm pretty sure we no longer have a program manager?
What’s that about?
Red Hat recently announced a round of layoffs[1] and the Fedora Program Manager role was impacted.
Ben posted this blog: https://funnelfiasco.com/blog/2023/05/12/inaction-bcotton/
What's the process for selecting a new Program Manager?
The Fedora Program Manager was a paid Red Hat position before. We do not have a process defined for selecting one from the community. There are a few people trying to spread the responsibilities around in the meantime.
josh
On Wed, May 24, 2023 at 7:23 PM Tom Stellard tstellar@redhat.com wrote:
What's the process for selecting a new Program Manager?
From the words that have been shared at: https://docs.fedoraproject.org/en-US/council/fpgm/ the position itself has been eliminated.
The important responsibilities will (presumably) need to be passed to others on the Fedora Council, who will likely need to triage some of their current work to make room.
I hope the Fedora Council members will soon share the updated roles and responsibilities of the remaining members.
On 5/24/23 12:31, Gary Buhrmaster wrote:
On Wed, May 24, 2023 at 7:23 PM Tom Stellard tstellar@redhat.com wrote:
What's the process for selecting a new Program Manager?
From the words that have been shared at: https://docs.fedoraproject.org/en-US/council/fpgm/ the position itself has been eliminated.
The important responsibilities will (presumably) need to be passed to others on the Fedora Council, who will likely need to triage some of their current work to make room.
I hope the Fedora Council members will soon share the updated roles and responsibilities of the remaining members.
I agree with this.
Maybe this has happened and I missed it, but it would nice if the Council put out a statement acknowledging the position has been eliminated and explaining what will happen next.
Going back to the original topic, though, what is the best way to raise the issue of the elections being delayed, should I file a ticket for the Council?
-Tom
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Wed, May 24, 2023 at 12:36:58PM -0700, Tom Stellard wrote:
On 5/24/23 12:31, Gary Buhrmaster wrote:
On Wed, May 24, 2023 at 7:23 PM Tom Stellard tstellar@redhat.com wrote:
What's the process for selecting a new Program Manager?
From the words that have been shared at: https://docs.fedoraproject.org/en-US/council/fpgm/ the position itself has been eliminated.
The important responsibilities will (presumably) need to be passed to others on the Fedora Council, who will likely need to triage some of their current work to make room.
I hope the Fedora Council members will soon share the updated roles and responsibilities of the remaining members.
I agree with this.
Maybe this has happened and I missed it, but it would nice if the Council put out a statement acknowledging the position has been eliminated and explaining what will happen next.
Going back to the original topic, though, what is the best way to raise the issue of the elections being delayed, should I file a ticket for the Council?
just as a note, our FPL (Fedora Project Leader) (Matthew) and FCA (Fedora community architect) (Justin) are both at Red Hat summit this week.
So yeah, likely they are aware, but busy... but I guess a council ticket would be good to make sure.
kevin
On 5/24/23 13:00, Kevin Fenzi wrote:
On Wed, May 24, 2023 at 12:36:58PM -0700, Tom Stellard wrote:
On 5/24/23 12:31, Gary Buhrmaster wrote:
On Wed, May 24, 2023 at 7:23 PM Tom Stellard tstellar@redhat.com wrote:
What's the process for selecting a new Program Manager?
From the words that have been shared at: https://docs.fedoraproject.org/en-US/council/fpgm/ the position itself has been eliminated.
The important responsibilities will (presumably) need to be passed to others on the Fedora Council, who will likely need to triage some of their current work to make room.
I hope the Fedora Council members will soon share the updated roles and responsibilities of the remaining members.
I agree with this.
Maybe this has happened and I missed it, but it would nice if the Council put out a statement acknowledging the position has been eliminated and explaining what will happen next.
Going back to the original topic, though, what is the best way to raise the issue of the elections being delayed, should I file a ticket for the Council?
just as a note, our FPL (Fedora Project Leader) (Matthew) and FCA (Fedora community architect) (Justin) are both at Red Hat summit this week.
So yeah, likely they are aware, but busy... but I guess a council ticket would be good to make sure.
I've filed a ticket here:
https://pagure.io/Fedora-Council/tickets/issue/457
-Tom
kevin
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Wed, May 24, 2023 at 6:35 PM Tom Stellard tstellar@redhat.com wrote:
I've filed a ticket here:
Thanks Kevin and Tom for getting this flagged as a Council ticket.
Hi Gary, hi all,
Thanks for filing the Fedora Council ticket and flagging this. Ben trained me on the election process and transferred ACLs to me before his final day at Red Hat. I dropped the ball on continuity. I will run the elections this round. The timing with Red Hat Summit this week, the F38 release party next week, and ongoing Flock logistics ended up spilling over.
On Wed, May 24, 2023 at 3:37 PM Tom Stellard tstellar@redhat.com wrote:
Maybe this has happened and I missed it, but it would nice if the Council put out a statement acknowledging the position has been eliminated and explaining what will happen next.
Matthew and I were working on something to share with the community and wanted to publish last week, but for several reasons, it hasn't been timely. I hope to have more in hand soon.
Il 24/05/23 21:19, Josh Boyer ha scritto:
On Wed, May 24, 2023 at 2:55 PM Peter Boy pboy@uni-bremen.de wrote:
Am 24.05.2023 um 20:30 schrieb Chris Murphy lists@colorremedies.com:
I'm pretty sure we no longer have a program manager?
What’s that about?
Red Hat recently announced a round of layoffs[1] and the Fedora Program Manager role was impacted.
Ben posted this blog: https://funnelfiasco.com/blog/2023/05/12/inaction-bcotton/
josh
[1] https://www.redhat.com/en/blog/message-red-hat-associates-today
Wait, what?? Someone at RH wakes up in the morning and decides to cut one of the key roles (or better, THE) of Fedora community and this goes completely unannounced, unnoticed and without any backup plan?
I have seen other dumb decisions by RH about Fedora in the past, but I think this is the greatest one, both for Ben's role and for their person.
Mattia
On 5/24/23 4:49 PM, Mattia Verga via devel wrote:
Wait, what?? Someone at RH wakes up in the morning and decides to cut one of the key roles (or better, THE) of Fedora community and this goes completely unannounced, unnoticed and without any backup plan?
I have seen other dumb decisions by RH about Fedora in the past, but I think this is the greatest one, both for Ben's role and for their person.
I totally agree. I am pretty upset that they chose to let bcotton go. His work was top notch and I will miss him and his contributions. Losing him as the Fedora Program Manager is going to be very impacting to the project in the short to medium term. We are already seeing things fall through the cracks. What a short-sighted decision.
Also finding out about this in a random thread is a bummer. There should have been an announcement.
To the RH powers that be that made this decision. You chuckleheads dun goofed.
Joe
Joe Doss wrote:
On 5/24/23 4:49 PM, Mattia Verga via devel wrote:
Wait, what?? Someone at RH wakes up in the morning and decides to cut one of the key roles (or better, THE) of Fedora community and this goes completely unannounced, unnoticed and without any backup plan?
I have seen other dumb decisions by RH about Fedora in the past, but I think this is the greatest one, both for Ben's role and for their person.
I totally agree. I am pretty upset that they chose to let bcotton go. His work was top notch and I will miss him and his contributions. Losing him as the Fedora Program Manager is going to be very impacting to the project in the short to medium term. We are already seeing things fall through the cracks. What a short-sighted decision.
Also finding out about this in a random thread is a bummer. There should have been an announcement.
To the RH powers that be that made this decision. You chuckleheads dun goofed.
That is the kind of braindead decisions that was to be expected after the sellout to the mega(dis)trust IBM.
The total lack of advance communication (because they want to lay off their employees as quietly as possible in order not to scare potential shareholders?) just makes it worse.
Kevin Kofler
On Thu, May 25, 2023 at 7:58 AM Kevin Kofler via devel devel@lists.fedoraproject.org wrote:
Joe Doss wrote:
On 5/24/23 4:49 PM, Mattia Verga via devel wrote:
Wait, what?? Someone at RH wakes up in the morning and decides to cut one of the key roles (or better, THE) of Fedora community and this goes completely unannounced, unnoticed and without any backup plan?
I have seen other dumb decisions by RH about Fedora in the past, but I think this is the greatest one, both for Ben's role and for their person.
I totally agree. I am pretty upset that they chose to let bcotton go. His work was top notch and I will miss him and his contributions. Losing him as the Fedora Program Manager is going to be very impacting to the project in the short to medium term. We are already seeing things fall through the cracks. What a short-sighted decision.
Also finding out about this in a random thread is a bummer. There should have been an announcement.
To the RH powers that be that made this decision. You chuckleheads dun goofed.
That is the kind of braindead decisions that was to be expected after the sellout to the mega(dis)trust IBM.
This is neither accurate nor helpful to any conversation. If you want to throw invectives at people or companies, please do it elsewhere.
josh
The total lack of advance communication (because they want to lay off their employees as quietly as possible in order not to scare potential shareholders?) just makes it worse.
Kevin Kofler
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Wed, May 24, 2023 at 9:50 PM Mattia Verga via devel devel@lists.fedoraproject.org wrote:
Wait, what?? Someone at RH wakes up in the morning and decides to cut one of the key roles (or better, THE) of Fedora community and this goes completely unannounced, unnoticed and without any backup plan?
I do understand why RedHat itself will not announce who got laid off, but the Council members should have been informed (I hope!) at the time, and should have worked on an announcement to the community, even if all they could say was "stay tuned, we are working it out".
I would like to believe this will be a learning opportunity for the Council to improve their communications for the next time something impacts their group (and the Fedora community).
On Wed, May 24, 2023 at 9:34 PM Gary Buhrmaster gary.buhrmaster@gmail.com wrote:
On Wed, May 24, 2023 at 9:50 PM Mattia Verga via devel devel@lists.fedoraproject.org wrote:
Wait, what?? Someone at RH wakes up in the morning and decides to cut one of the key roles (or better, THE) of Fedora community and this goes completely unannounced, unnoticed and without any backup plan?
I do understand why RedHat itself will not announce who got laid off, but the Council members should have been informed (I hope!) at the time, and should have worked on an announcement to the community, even if all they could say was "stay tuned, we are working it out".
The Council members were not informed in advance. They found out about the layoffs at the same time the public did, and also found out about Ben's specific role only after he informed others he was impacted.
I would like to believe this will be a learning opportunity for the Council to improve their communications for the next time something impacts their group (and the Fedora community).
I do believe they are working on something, but you're laying blame at the feet of the wrong people here. The Council was blindsided like everyone else.
josh
The elections are now scheduled to start on Monday, 29 May and end on Sunday, 11 June. Documentation and schedules are being updated.
On Thu, May 25, 2023 at 6:55 AM Josh Boyer jwboyer@fedoraproject.org wrote:
On Wed, May 24, 2023 at 9:34 PM Gary Buhrmaster gary.buhrmaster@gmail.com wrote:
I do understand why RedHat itself will not announce who got laid off, but the Council members should have been informed (I hope!) at the time, and should have worked on an announcement to the community, even if all they could say was "stay tuned, we are working it out".
The Council members were not informed in advance. They found out about the layoffs at the same time the public did, and also found out about Ben's specific role only after he informed others he was impacted.
This isn't incorrect but I do want to clarify the timeline because it is what I would have wanted to know as a community member and there are events that may appear to be conflicting in the timeline (e.g. Ben's blog and my LinkedIn recommendation for him). We did have *some* advance notice before the general public. Ben mentioned https://funnelfiasco.com/blog/2023/05/12/inaction-bcotton/ the Red Hat reductions were announced in the US on 24 April and that was when we found out. We knew Ben's last day was 12 May. That was as much advance notice that we had.
The week of 24 April was not productive. It was a shocking week for nearly everyone. But we did start transitioning Ben's work before his final day and his blog post, which is why you are seeing incredibly helpful Fedorans who are stepping up right now and picking up the slack in Ben's absence (*thank you folks!*). There are going to be gaps. Some things will fall through the cracks. But we will get through this. Calling out slippage as Fedora Council tickets is likely the most effective way for (1) problems to be identified and noticed, and (2) for Fedora leadership to take steps at resolving those problems.
On Thu, May 25, 2023 at 8:58 PM Justin W. Flory (he/him) jwf@redhat.com wrote:
The elections are now scheduled to start on Monday, 29 May and end on Sunday, 11 June. Documentation and schedules are being updated.
On Thu, May 25, 2023 at 6:55 AM Josh Boyer jwboyer@fedoraproject.org wrote:
On Wed, May 24, 2023 at 9:34 PM Gary Buhrmaster gary.buhrmaster@gmail.com wrote:
I do understand why RedHat itself will not announce who got laid off, but the Council members should have been informed (I hope!) at the time, and should have worked on an announcement to the community, even if all they could say was "stay tuned, we are working it out".
The Council members were not informed in advance. They found out about the layoffs at the same time the public did, and also found out about Ben's specific role only after he informed others he was impacted.
This isn't incorrect but I do want to clarify the timeline because it is what I would have wanted to know as a community member and there are events that may appear to be conflicting in the timeline (e.g. Ben's blog and my LinkedIn recommendation for him). We did have some advance notice before the general public. Ben mentioned the Red Hat reductions were announced in the US on 24 April and that was when we found out. We knew Ben's last day was 12 May. That was as much advance notice that we had.
The week of 24 April was not productive. It was a shocking week for nearly everyone. But we did start transitioning Ben's work before his final day and his blog post, which is why you are seeing incredibly helpful Fedorans who are stepping up right now and picking up the slack in Ben's absence (thank you folks!). There are going to be gaps. Some things will fall through the cracks. But we will get through this. Calling out slippage as Fedora Council tickets is likely the most effective way for (1) problems to be identified and noticed, and (2) for Fedora leadership to take steps at resolving those problems.
And, while I can understand that the days after April 24th may not have been comfortable, and taking advantage of access to Ben while he was still available was a good thing, I do believe some member of the Council should have started working on the note to the Community to be sent on (or about) May 15th with something of the form that RH's staff redundancies have resulted in the elimination of the position of Fedora Program Manager, and the Council is working through how the existing roles and responsibilities of the Council will be revised (downwards?), and redistributed given the reduction of staffing, and if anyone sees something getting dropped, create a ticket (properly wordsmithed by someone with actual skills in writing words, of course).
I think we all appreciate that everyone is stepping up and trying their best. Thank you!
But I will continue to believe that we(*) should not have had to find out about the changes when the elections did not happen, which was the point of my request that this be taken as a learning opportunity about better communications for the next time (which may have nothing to do with future redundancies, as people can leave, or have life emergencies, and those can impact ongoing activities).
Thank you for your consideration.
(*) I was aware of it personally because it was posted elsewhere, but clearly a lot of people seemed to have been surprised. I do not believe that should happen.
On Thu, May 25, 2023 at 5:54 PM Gary Buhrmaster gary.buhrmaster@gmail.com wrote:
On Thu, May 25, 2023 at 8:58 PM Justin W. Flory (he/him) jwf@redhat.com wrote:
The elections are now scheduled to start on Monday, 29 May and end on
Sunday, 11 June. Documentation and schedules are being updated.
On Thu, May 25, 2023 at 6:55 AM Josh Boyer jwboyer@fedoraproject.org
wrote:
On Wed, May 24, 2023 at 9:34 PM Gary Buhrmaster gary.buhrmaster@gmail.com wrote:
I do understand why RedHat itself will not announce who got laid off, but the Council members should have been informed (I hope!) at the time, and should have worked on an announcement to the community, even if all they could say was "stay tuned, we are working it out".
The Council members were not informed in advance. They found out about the layoffs at the same time the public did, and also found out about Ben's specific role only after he informed others he was impacted.
This isn't incorrect but I do want to clarify the timeline because it is
what I would have wanted to know as a community member and there are events that may appear to be conflicting in the timeline (e.g. Ben's blog and my LinkedIn recommendation for him). We did have some advance notice before the general public. Ben mentioned the Red Hat reductions were announced in the US on 24 April and that was when we found out. We knew Ben's last day was 12 May. That was as much advance notice that we had.
The week of 24 April was not productive. It was a shocking week for
nearly everyone. But we did start transitioning Ben's work before his final day and his blog post, which is why you are seeing incredibly helpful Fedorans who are stepping up right now and picking up the slack in Ben's absence (thank you folks!). There are going to be gaps. Some things will fall through the cracks. But we will get through this. Calling out slippage as Fedora Council tickets is likely the most effective way for (1) problems to be identified and noticed, and (2) for Fedora leadership to take steps at resolving those problems.
And, while I can understand that the days after April 24th may not have been comfortable, and taking advantage of access to Ben while he was still available was a good thing, I do believe some member of the Council should have started working on the note to the Community to be sent on (or about) May 15th with something of the form that RH's staff redundancies have resulted in the elimination of the position of Fedora Program Manager, and the Council is working through how the existing roles and responsibilities of the Council will be revised (downwards?), and redistributed given the reduction of staffing, and if anyone sees something getting dropped, create a ticket (properly wordsmithed by someone with actual skills in writing words, of course).
I think we all appreciate that everyone is stepping up and trying their best. Thank you!
But I will continue to believe that we(*) should not have had to find out about the changes when the elections did not happen, which was the point of my request that this be taken as a learning opportunity about better communications for the next time (which may have nothing to do with future redundancies, as people can leave, or have life emergencies, and those can impact ongoing activities).
Thank you for your consideration.
(*) I was aware of it personally because it was posted elsewhere, but clearly a lot of people seemed to have been surprised. I do not believe that should happen.
I agree that it should not have happened this way.
On Mon, May 29, 2023 at 3:28 AM Kevin Kofler via devel devel@lists.fedoraproject.org wrote:
Gary Buhrmaster wrote:
RH's staff redundancies
The position was clearly NOT redundant.
The word (and all words are made up) is used by organizations to meet certain legal requirements (talk to *your* lawyer for a better explanation of all the details and subtleties of employment law if you don't understand employment law, as it is complex (and even more complex in multi- national organizations such as IBM and RH as some countries have "interesting" requirements); my understanding is based on occasional discussions with my employment lawyer colleagues, and I have mostly decided that is not a field I wish to become an expert in).
This is just RH unilaterally killing jobs including a central Fedora position in order to increase IBM's profits.
Any particular position (in a large enough company like IBM, or RH) has about zero impact on any organization's profits. It *may* indicate priorities (which is a completely different discussion, and which you might, legitimately, ask if IBM and RH is committed, and at what level, to Fedora in the long term(*)).
Personally, I think the Fedora Program Manager (as embodied most recently in Ben) provided value to the Fedora community, as some of the work being done was something that volunteers cannot easily pick up (simply due to available time (resources)).
I fervently hope that the council members will not (in the long term) try to "make do" with fewer people (asking others to do 130%), but will either offload to the community, or drop (after consultation with the community) some of the work the Program Manager or other members of the Council did (there needs to be a prioritized list of work and reassigments). If no one is willing/able to step up, some functions will need to be terminated for the good of the work/life balance of the remaining Council members (yes, some people live to work, and work to live, but that is not something we should expect of our hatters.).
(*) Someone, and I am not sure of the process or protocol, should ask RH what they see and want Fedora to be, and how they intend to support (fund) that going forward. It is, perhaps, not a place I (or you) wish to be, but right now all we really know is that RH has decided to de-commit some resources. Perhaps they intend to add more resources in a different way. I would like to think that discussion may have happened (or at least started) at the RH summit, but as I do not not attend (no one is paying my attendance), I have no idea.
Gary Buhrmaster wrote:
Any particular position (in a large enough company like IBM, or RH) has about zero impact on any organization's profits.
Which is why they have laid off a whole bunch of people. They just happen to not be as visible as the (now former) Fedora Program Manager.
It *may* indicate priorities (which is a completely different discussion, and which you might, legitimately, ask if IBM and RH is committed, and at what level, to Fedora in the long term(*)).
It was pretty clear in IBM's acquisition announcement that they are only interested in RH as a cloud services company and do not care at all about RHEL, let alone Fedora. The word "Linux" did not show up a single time in the whole announcement!
Kevin Kofler
Dne 29. 05. 23 v 7:03 Kevin Kofler via devel napsal(a):
It*may* indicate priorities (which is a completely different discussion, and which you might, legitimately, ask if IBM and RH is committed, and at what level, to Fedora in the long term(*)).
It was pretty clear in IBM's acquisition announcement that they are only interested in RH as a cloud services company and do not care at all about RHEL, let alone Fedora. The word "Linux" did not show up a single time in the whole announcement!
Red Hat still pays lots of people working on Fedora. Most of fedora-infra people, lots of people working on tooling - including me. And many others.
I think that your statement is unfair.
Miroslav