Re: Discussion around app retirements and categorizations by the CPE team

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Le 2019-07-22 10:22, Miro Hrončok a écrit :

Personally, I wish we had spent less engineering time in
infrastructure on Modularity and more on the contributor UX :(

It’s not just Modularity. Modularity is just a symptom. There is something deeply broken in the Red Hat / Fedora interface.

RHEL made Red Hat fortunes. It’s what justified the billions IBM paid for it (RHEL is the only Red Hat product where Red Hat completely dominates the market, even the best other offerings, like OpenShift, are just one among many).

And Fedora is RHEL’s future.

And yet what do we see ?

Highly-visible Red Hat investments on the desktop, where the focus is on creating flatpacks to deprecate Fedora as soon as possible. If you read the marketing messages you’d think Silverblue was the only Fedora today and rpm packaging a thing of the past. Even though Silverblue is incomplete by design, since it does not want to address anything except desktop deployments.

Huge Red Hat investments, in the Java ecosystem, that fail to translate into an healthy Fedora Java ecosystem. To the point that when IBM wants its Java guys to join there is absolutely no one Fedora-side to provide an on-boarding path.

Huge Red Hat investments, in the container ecosystem. And yet we get told CPE is downsizing its activities, in part because all the new cool things happen in the container space, contributors want to work on cool things, Fedora/RHEL is absent from this space, packaging the things containerized infra need is an afterthought.

As a result of short-term delivery focus, with no work on long term packaging and maintenance, we're seeing the same explosion of bundling and forking and API incompatibilities container-side we saw Java-side before, with the same highly predictible long term outcome.

Red Hat is taking RHEL and Fedora for granted.

There is no business drive to keep Fedora strong and growing, and lots of internal incentives to work instead on the next best purported value-added thing. There is no business drive to keep code healthy and maintenable long term, and lots of incentives to invent band-aids like modularity, to contain the rot some more till it’s someone else’s problem. There is no business drive, to create solutions, that can be deployed and used by joe nobody packager. And without those, there is no potential of long-term packaging community and no Fedora (let's cut the fluff Fedora is a lot of things but at core it’s a packaging community).

Well all that happened to others before, and one day the golden goose will be gone.

And why am writing about this non-Fedora sponsor things? Because Fedora has stewardship instances, that are supposed to tell those things to the generous sponsor, and keep it informed of the real state of its sponsored project. And, they are clearly failing to pass the message.

Regards,

--
Nicolas Mailhot
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux