From Fedora Project Wiki
< Server
mNo edit summary |
mNo edit summary |
||
| Line 18: | Line 18: | ||
= Delivery Mechanism = | = Delivery Mechanism = | ||
See [[Server/Proposals/Server_Lifecycle | Server Lifecycle Proposal]] for draft work that includes this topic. | |||
= Proposed Server Roles = | = Proposed Server Roles = | ||
| Line 24: | Line 26: | ||
= Requirements for First-Tier Applications/Services Supporting a Server Role = | = Requirements for First-Tier Applications/Services Supporting a Server Role = | ||
See [[Server/Proposals/Server_Roles | Server Roles Proposal]] for draft work that includes this topic. | |||
Revision as of 05:23, 8 November 2013
Our primary deliverable for January should be the definition of how we're going to prepare the platform and the requirements for an application stack to be promoted to first-tier inclusion. (Agreed 5 Nov 2013)
Mission Statement
Fedora Server is a common base platform with 'featured application stacks' built on top of it. We commit to produce, test, and distribute these application stacks.
Personas
See Personas (target users) for Fedora Server for draft work.
Use Cases
See Use Cases for Fedora Server for draft work.
Product Lifecycle
See Server Lifecycle Proposal for draft work.
Delivery Mechanism
See Server Lifecycle Proposal for draft work that includes this topic.
Proposed Server Roles
See Server Roles Proposal for draft work.
Requirements for First-Tier Applications/Services Supporting a Server Role
See Server Roles Proposal for draft work that includes this topic.