On Fri, Dec 4, 2020 at 2:33 PM Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > > On Fri, Dec 04, 2020 at 07:53:12PM +0100, pboy@xxxxxxxxxxxxx wrote: > > 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. > > > 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. It would be interesting if we had a set of use cases Fedora Server actually solves. So far in this thread we've seen people use it, but it reads to me like they use it to get a boiled down installation of Fedora. So is Fedora Server just a convenient way to get a quick and simple Fedora installation (e.g. you're using it because it's *Fedora*), or do people actually use it for traditional server use cases. For those using it for traditional server use cases, why? What about it do you find better than something like CentOS? josh _______________________________________________ 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
