> > > I'm comfortable saying that most Fedora users are not installing the > distro > just to support one specific application, as one might with RHEL or > CentOS, > but to benefit from the Four Foundations of Fedora, in this case the most > important ones being Freedom, Features and First. >
Exactly ... this is what I believe, too. I think that Fedora users put Fedora on their desktops and laptops to be creative in many ways of creativity. Some make make music, some enhance pictures, some model in Blender, cut videos, write documents. The majority, I dare to say, is not interested in having several Inkscape versions, they want the newest yet stable enough and they are satisfied with that. > It'd be great to have a working modular system, but since we don't seem to > have that, it's not a good idea to force the broken implementation on > users. > We need to consider what is best for Fedora's users, not what is best for > Red > Hat, at least in my opinion. > Fedora modules must be ready to work in all possible combinations and streams, if we really mean it seriously. For example, I as a user, want to install the newest version of Gimp, because I need the newest features, but since the newest Scanner Application stopped supporting my device, I need the penultimate one. I also play windows games with wine and I set the current version of wine to suit my needs, so I want to stick with this version as long as possible and maybe even beyond, and I also want an NFS share for my TV to consume, but because I am paranoid, I want to go 2 versions behind the latest. To make a long story short, I will need lots of different stream working in harmony and I will want to upgrade my PC without any problems. Until we can provide this, we should keep modularity as opt-in technology preview. > > I see no reason that dropping certain parts of Modularity from actual > releases > of Fedora will harm the relationship with Red Hat, as Stephen suggests. > Such > tests can, and probably should, be done in Rawhide, until they're actually > ready for users. > > So far, the best approach seems to be to remove default modules, and > require a > non-modular version for fedora releases and branched. (In addition to > whatever > packagers would package as modules. To clarify, I am not attempting to > suggest > nothing should be done with Modularity except in Rawhide.) > This seems to me the easiest way to solve current problems. > > We're not saying this to discourage you, at least that is not my goal. My > goal > is to ensure the best result for the end user. > > -- > John M. Harris, Jr. > Splentity > > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@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 > -- Lukáš Růžička FEDORA QE, RHCE Red Hat <https://www.redhat.com> Purkyňova 115 612 45 Brno - Královo Pole lruzi...@redhat.com TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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
