This proposal is currently being discussed on the Thoughts on Fedora Server lifecycle thread on the server mailing list.
Purpose
We need to define "server roles" and the criteria for that "role," then look at the server applications or application stacks which exist in the project and are applicable for that role and select which one we choose as that role. ([1]) We should produce the best out of the box optimized ks/playbooks files for any given server product, reducing the steps necessary to configure/tweak/optimize/scale/secure for administrator to perform and get started. ([2])
We will pick somewhere between one and three initial roles to focus on for F21. That's achievable and allows us to direct our energies. ([3])
Requirements for First-Tier Applications/Services Supporting a Server Role
We'll declare some services to be "first-tier". In other words: here are the set of things that we (The Fedora Project) asserts are functional, useful and ready for you to play with.
We should always allow access to the greater universe of packages and services, but in order to be promoted to "first-tier", they would have to meet some set of guidelines that we lay down (i.e. "must provide an Ansible playbook to set them up", or "must be capable of scaling in the following ways", etc.) ([4])