Server Technical Specification: Agenda and First Draft

[Stephen Gallagher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've created a wiki page[1] for the Technical Specification that we
are working on. I've copied much of the structure from the Workstation
tech spec, as it was well organized.

There are quite a few sections in it that I have tagged as UNAPPROVED.
I believe we need to make these the agenda for the Tech Spec Working
Session today. What we will do is quickly go through each of them.
We'll mark any that are uncontested as "Approved" and then go back and
discuss any that need discussion.

[1] https://fedoraproject.org/wiki/Server/Technical_Specification
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlMQkbIACgkQeiVVYja6o6PG+wCeNSl8khjCant8UYUGkTNW+67J
> UaEAnjBKT+3yIwC+527f7I5grKKQNmCE
> =czbY
> -----END PGP SIGNATURE-----

[Colin Walters]

On Fri, Feb 28, 2014 at 8:40 AM, Stephen Gallagher 
 wrote:
> [1] https://fedoraproject.org/wiki/Server/Technical_Specification

Minor, but I think we should remove the sentence "systemd-nspawn will 
be used to manage containerization capabilities.", for two reasons:

1) systemd-nspawn is for "building, testing, debugging, and profiling", 
i.e. not production.
2) It doesn't make a lot of sense to group virt with containers at this 
level

Merge Display Manager and Graphics?  BTW, we will need eventually to 
figure out how "workstation on a server" is configured.  I mentioned 
this elsewhere but basically for the case where you need to run some 
(potentially legacy) GUI app from your server.  We can't necessarily do 
X forwarding since we have to consider Windows clients. Think 
system-config-lvm or whatever.