Fedora Server PRD Draft and call for participation

Joerg Stephan johe.stephan at ymail.com
Fri Jan 10 20:44:31 UTC 2014

Hash: SHA1

Hi Stephen,

i guess i am late :-) so maybe caused by that, while reading through
the document there are some basic questions in my mind, so sorry that
i start with some clearification question:

(you EQUAL all contributors so far)

When you speak about "Server Roles" you mean the service which is
provided by the server? Like DNS, so you mean that we need an
easy/remote/api way of installing a service on an server? Like you
could do it with puppet or spacewalk or maybe WebYAST in SUSE?

Were is the "base"? I mean the basic server, the naked installation
like a minimal server. For me, as an administrator i like really tiny
iso`s which provide a basic installation so that i can ran into the
loud and noisy server room an install the system within some seconds
and do the rest via ssh (or something else).

Than (currently last), i am missing "security". Now a days i guess
security plays a big role. So maybe we should tell a bit about
security features we need in this set. Like pre configured firewalls,
maybe installation sets which open there port on firewall side. Or
maybe an preferrred backup solution, easy to install maybe api
triggered like we got it in zabbix to bound client and server.

So far & Cheers


Am 10.01.2014 21:05, schrieb Stephen Gallagher:
> The first deliverable that the Fedora Server Working Group was
> tasked with was the production of a Product Requirements Document.
> This document is intended to provide a high-level view of the goals
> and primary deliverables of the Fedora Server distribution. A great
> deal of discussion has gone on during the weekly Working Group
> meetings as well as on the mailing list.
> At this time, the deadline for the delivery of the PRD is rapidly 
> approaching. Originally it was due to be delivered for ratification
> on Monday, January 13th, but at the FESCo meeting on Wednesday, it
> was agreed to delay this deadline by a single week. The primary
> reason for this delay was so that the Fedora Cloud and Fedora
> Server groups could have some last discussions about overlap and
> respective areas of responsibility.
> This past Tuesday, we had an all-day PRD hackfest in IRC and have
> come up with a fairly strong draft[1]. It is not yet complete
> (notably, there remains a FIXME under "Misc. Concerns" and some
> ambiguity around the Use Cases), but I believe that it is close
> enough to its final form (as envisioned by those people that have
> contributed to it), that we should expose this document to the
> wider world and ask for input before submitting it to the Fedora
> Engineering Steering Committee and Fedora Advisory Board a week
> from Monday.
> Please read through the PRD draft and provide feedback of any sort.
> If you see that we have missed or misrepresented any of our
> statements, we would very much like to hear this soon.
> [1] 
> https://fedoraproject.org/w/index.php?title=Server/Product_Requirements_Document_Draft
> server mailing list server at lists.fedoraproject.org 
> https://admin.fedoraproject.org/mailman/listinfo/server
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/


More information about the server mailing list