On Mon, Mar 7, 2016 at 9:03 PM, Stephen Gallagher <sgallagh(a)redhat.com> wrote:
> On Mar 7, 2016, at 8:37 PM, Matthew Miller <mattdm(a)fedoraproject.org> wrote:
>
> On Tue, Mar 08, 2016 at 01:30:39AM +0000, Peter Robinson wrote:
>>> Ideally, we'd have roles to cover just about _anything_ anyone wanted,
>>> and so the process would be start with Fedora Server _instead_ of
>>> Minimal, and then install your role, instead of packages, but maybe
>>> that's too far out.
>> Also at the moment server is all that is built for Secondary arches
>> and so with a DVD installer it is the only way they can get a minimal.
>
> There's been some talk recently of having a re-chartered Base WG maintain a
> functional minimal install (as well as the container base image). That
> seems like it might serve some of the Secondary arches better (although
> for others, actual Server seems appropriate too). And, I guess that's
> still separate from whether Server should _also_ present a minimal
> environment of its own — that's a question of audience and use cases, I
> guess.
>
>
I'm of the opinion that Server Edition should realistically be as minimal as we are
willing to support. That's not the same thing as the build-your-own-OS case of the
minimal environment today.
It is unclear whether you are saying the "Base WG maintain a
functional minimal install" is a bad idea, or if you are simply saying
the current Server image is as small as you want to go for Server. The
we is also unclear. We as in Fedora or we as in Server?
Sorry, I'm not trying to be difficult. I simply don't understand
exactly what your point of view here is.
If Server Edition isn't small enough for some use cases, then we
should identify those specifically and decide if it's worth adjusting the contents of
the Server Edition to handle that case or if it belongs as part of another (perhaps new)
Edition.
The often spoke of Base WG minimal image is thought of as the bare
bones minimal image that everything else is built on top of. This
ties directly into modularity in that the "image/container" is a
functional check of the minimal modules. Hopefully it becomes more
clear after the meeting tomorrow.
josh