< Server
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
We will use a set of personas to describe our target users and their respective needs. This document will list the personas in their simplified forms, with detailed explanations of each one available on their respective wiki pages.
- System Administrator "Macgyver"
- Administrator with limited hardware and personnel resources to work with
- Needs to be able to do "a lot with a little"
- DevOps Engineer/Administrator
- Focus is on time-to-deploy and time-to-recover as opposed to uptime
- Value is achieved by delivering the latest capabilities fastest
- Needs to be able to deliver quickly to PaaS, SaaS and bare-metal servers
- Traditional Application Developer
- Needs a platform with API and ABI stability guarantees
- Focus will be on minimizing risk when making changes
- Cannot tolerate rapid changes in core functionality
- Junior Enterprise System Administrator
- Simplify automation to manage repetitive tasks
- Needs intuitive mechanisms to effect common changes
- Decision Maker
- Makes purchasing decisions and directs technology choices
- Interacts with upstream FOSS communities to identify potential value
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.