Re: The future of Fedora Server (was Re: Fedora 34 Change: Make Fedora CoreOS a Fedora Edition (System-Wide Change))
> Am 04.12.2020 um 20:33 schrieb Matthew Miller : > >> ... >> Just in case it is indeed considered useful and desirable I could >> contribute various Fedora Server related/specific documentations and >> how-to's, e.g. an annotated step-by-step guide to setup a basic server >> which can get extended for various purposes, how to set up a Postgres >> server on top of a basic server, an infrastructure for vm’s and containers >> (including scripts and ansible templates), troubleshooting guides, and >> other topics like that (mostly practical but always together with >> preliminary strategic considerations). Just let me know. > > > Absolutely! A functioning Working Group needs people interested in and doing > these kinds of things too, not just package maintenance. So if you're > interested, you'd absolutely be welcome in a re-constituted Fedora Server > WG. Well, where should we discuss further proceedings? Is it this generic devel list, is it ser...@lists.fedoraproject.org? Another one? First of all we need content, of course, but we also need some planning beforehand. - How to set things in motion, - where we want which documentation be published (under Releases, Quick Doc, dedicated area in https://docs.fedoraproject.org/en-US/docs/, or wiki entries at https://fedoraproject.org/wiki/Fedora_Project_Wiki?rd=Fedora_Project_Wiki/en), - where can drafts be discussed before publication, - contact with the Doc project to name but a few. > -- > Matthew Miller > > Fedora Project Leader ___ 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
Re: The future of Fedora Server (was Re: Fedora 34 Change: Make Fedora CoreOS a Fedora Edition (System-Wide Change))
> Am 04.12.2020 um 23:16 schrieb Japheth Cleaver : > > On 12/4/2020 12:35 PM, Stephen John Smoogen wrote: >> >> ... >> >> For the people who were using it as servers, it was split between getting >> ready for the next RHEL/CentOS they would be deploying, they needed packages >> which were not in EPEL, or things like python/nodejs/etc was new enough for >> what they needed to run but wasn't in EL8. >> > It would be interesting to consider how Fedora Server use cases change over > time during an EL release cycle. > > For many server use cases where the box is NOT ephemeral, when CentOS and > Fedora are similar, it's likely that CentOS is going to be a > better-engineered and tested option. But as time goes on and the next EL > release isn't either isn't announced or isn't stable enough to rely on, > Fedora Server probably sees more use as a quasi-stable release base.. This > fills a real need when your users are absolutely clamoring for things that > aren't likely to be backported into the stable EL release and you don't > want to have to send them into Ubuntu/Debian land (or have them grab an > un-administered container off the shelf). Fedora has advantages not only when RHELx / CentOSx is matured, but in some cases already at release time, when some important components are already „behind“, e.g. postfix / dovecot with CentOS 8 regarding SNI and submission (which are quite important features in a containerised world). And with the current rapid development, even small version differences can be important. > In fact, Fedora Server as a "not EL, but better than nothing as a temporarily > stable platform" during these later periods could be a useful niche to fill. > Bonus points for some of those extended support duration/stable discussions > from a few years ago. I see advantages sui generis in Fedora Server over CentOS, not "just" an interim solution or workaround until the next CentOS version is released. You get (almost) all the positive features that make CentOS /RHEL stand out (well thought-out architecture and workflows, security, systematic tools, etc.) and additionally - more up-to-date application software, which often enables a better response to current developments and changing requirements - easier administration due to a greater variety of available packages - shorter release jumps, which are therefore less disruptive - easier (quasi rolling) updates (dnf update), which save a lot of time - Freedom from strict RH feature management (example BTRFS, XEN some years ago) - greater backwards hardware compatibility (e.g. exclusion of drivers in el 8, which make some older hardware unusable or only very difficult to use) The list can easily be extended. -- Dr. Peter Boy p...@boy-digital.de p...@uni-bremen.de ___ 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
Re: The future of Fedora Server (was Re: Fedora 34 Change: Make Fedora CoreOS a Fedora Edition (System-Wide Change))
> Am 04.12.2020 um 20:33 schrieb Matthew Miller : > > On Fri, Dec 04, 2020 at 07:53:12PM +0100, p...@uni-bremen.de wrote: >> Just in case it is indeed considered useful and desirable I could >> contribute various Fedora Server related/specific documentations and >> how-to's, e.g. an annotated step-by-step guide to setup a basic server >> which can get extended for various purposes, how to set up a Postgres >> server on top of a basic server, an infrastructure for vm’s and containers >> (including scripts and ansible templates), troubleshooting guides, and >> other topics like that (mostly practical but always together with >> preliminary strategic considerations). Just let me know. > > > Absolutely! A functioning Working Group needs people interested in and doing > these kinds of things too, not just package maintenance. So if you're > interested, you'd absolutely be welcome in a re-constituted Fedora Server > WG. OK, I would like to participate and contribute to the documentary side. ___ 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
Re: The future of Fedora Server (was Re: Fedora 34 Change: Make Fedora CoreOS a Fedora Edition (System-Wide Change))
> Am 04.12.2020 um 19:08 schrieb Matthew Miller : > > It's not a matter of making changes for change's own sake, but I would hope > that we'd have some level of innovation and experimentation in Fedora > Server. There are also just normal things like marketing materials, > promotion, blog posts, docs, etc., that can use ongoing work. > I’m not a maintainer but I use Fedora Server for a lot of our university research institutions infrastructure (and I’m a dormant member of Fedora docs). Just in case it is indeed considered useful and desirable I could contribute various Fedora Server related/specific documentations and how-to's, e.g. an annotated step-by-step guide to setup a basic server which can get extended for various purposes, how to set up a Postgres server on top of a basic server, an infrastructure for vm’s and containers (including scripts and ansible templates), troubleshooting guides, and other topics like that (mostly practical but always together with preliminary strategic considerations). Just let me know. ___ 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
Re: Should the default editor be changed from vi to nano on upgrades to Fedora 33+
> Am 04.12.2020 um 09:40 schrieb Till Maas : > > Hi, > > On Thu, Dec 03, 2020 at 08:30:45PM +0100, Miro Hrončok wrote: > >> Changing the default on upgrades is good because the Fedora 33+ experience >> is similar regardless whether the system is freshly installed or upgraded. > > … already familiar with vi or changed their editor. Therefore it seems to > be more disturbing to change this default during upgrade. > > Thanks > Till I strongly agree! ___ 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
Re: Future of Fedora Server Edition [was: Re: Fedora 34 Change: Make Fedora CoreOS a Fedora Edition (System-Wide Change)]
> Am 03.12.2020 um 20:35 schrieb Alexander Bokovoy : > > On to, 03 joulu 2020, Matthew Miller wrote: >> On Thu, Dec 03, 2020 at 10:53:39AM -0800, Kevin Fenzi wrote: >>> I suppose we could look into this, but it seems kind of complementary to >>> me: >>> Server: a install dvd, pxe/netboot >>> Cloud: a runnable image >>> Are folks wanting to drop the dvd and netinstall? >>> Or just market the Cloud image more to server admins that want a ready >>> to run image? >> >> Mostly the latter. I don't even really care if they end up keeping the >> distinct os-release and etc. > > I do care about being able to deploy from DVD or pxe/netboot. For home > environments cloud images are not everything you need, especially for > home infrastructure. FreeIPA on Fedora is one of practical home > infrastructure deployment targets. Hot only home environments! At least very many companies of all sizes have local server infrastructure and many cannot or do not want to rely on the cloud alone. I very much hope that the Fedora project does not fall for hype. ___ 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
Re: systemd v247-rc2 (app.slice, oomd, udev rule changes, light deps)
Hi, is there hope that this selinux update will make system-container usable in Fedora again? ( see e.g. https://bugzilla.redhat.com/show_bug.cgi?id=1900869 https://bugzilla.redhat.com/show_bug.cgi?id=1900888 ) > Am 12.11.2020 um 15:15 schrieb Zbigniew Jędrzejewski-Szmek > : > > Hi, > > we're getting ready to push systemd 247-rc2 to rawhide. This is > currently blocked by selinux (see below), but I wanted to give a heads-up. > There's a number of changes which are interesting for Fedora: > > > ... > > Zbyszek > ___ > 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 ___ 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
