Immanetize (talk | contribs) m (→General =) |
(→Workstation: - copied from Workstation PRD for now) |
||
Line 4: | Line 4: | ||
=== Workstation === | === Workstation === | ||
(cut n paste from [https://fedoraproject.org/wiki/Workstation/Workstation_PRD]) | |||
==== Target Audience ==== | |||
'''General:''' | |||
Programming Environment: web languages and tools, open source databases, IDE, Compilers, debug tools, performance monitoring | |||
Desktop apps should be sufficient to make this system the user's only computer. | |||
'''Case 1: Student''' | |||
Engineering/CS student who needs a personal system for software classwork and personal projects. Software class work may require particular tool chain versions. Tries out new versions of open source applications when released. Uses computer to play games. | |||
Ability to play 3D games from commercial publishers distributing games for Linux. | |||
Multiple developer environments i.e. school standard for class work, latest tools for personal use. | |||
'''Case 2: Independent Developer''' | |||
Personal development system for an independent software developer doing contract work or developing apps for a new opportunity. | |||
Desktop Apps: Up to date desktop with email client, browser, productivity suite, messaging, and a complete set of desktop apps and utilities. | |||
Desktop apps should be sufficient to make this system the developer's only computer. | |||
Generally a single development environment with the latest web development tools. | |||
Easy to configure Virtual Machines for testing software. | |||
'''Case 3: Small Company Developer''' | |||
Software developer working on an individual project or coordinated small team. DevOps. | |||
Generally a single development environment with the latest web development tools. Easy to configure Virtual Machines for testing software. | |||
Testing in local VMs and on dedicated testing systems. | |||
'''Case 4: Developer in a Large Organization''' | |||
Software developer working on a large, coordinated project in a large organization. | |||
Support for enterprise login. | |||
Multiple developer environments i.e. current project and maintenance work on older projects. | |||
Testing typically on a target system in a testing lab. | |||
'''Other users''' | |||
While the developer workstation is the main target of this system and what we try to design this for, we do of course also welcome other users to the Fedora Workstation. In fact, many of the changes and improvements we expect to implement for developers will be equally beneficial to other user segments. For instance our plans around multi-screen handling and improved terminal functionality should also be highly beneficial to a system administrator. Or the work we are doing to provide a high performance graphics workstation would be useful to people who want a Linux gaming PC. Or a student who just wants a system with a productivity suite to write papers will of course get benefit from the fact that we do ship a good productivity suite. We will welcome feedback and requests from all our users and try to accommodate it, as long as it doesn't negatively impact our developer target group and we have people available who have the time and ability to work on the requests. | |||
=== Server === | === Server === |
Revision as of 14:49, 26 February 2015
This page is about personas; use cases and user stories to target documentation on.
General
Workstation
(cut n paste from [1])
Target Audience
General:
Programming Environment: web languages and tools, open source databases, IDE, Compilers, debug tools, performance monitoring
Desktop apps should be sufficient to make this system the user's only computer.
Case 1: Student
Engineering/CS student who needs a personal system for software classwork and personal projects. Software class work may require particular tool chain versions. Tries out new versions of open source applications when released. Uses computer to play games. Ability to play 3D games from commercial publishers distributing games for Linux. Multiple developer environments i.e. school standard for class work, latest tools for personal use.
Case 2: Independent Developer
Personal development system for an independent software developer doing contract work or developing apps for a new opportunity.
Desktop Apps: Up to date desktop with email client, browser, productivity suite, messaging, and a complete set of desktop apps and utilities. Desktop apps should be sufficient to make this system the developer's only computer.
Generally a single development environment with the latest web development tools.
Easy to configure Virtual Machines for testing software.
Case 3: Small Company Developer
Software developer working on an individual project or coordinated small team. DevOps.
Generally a single development environment with the latest web development tools. Easy to configure Virtual Machines for testing software.
Testing in local VMs and on dedicated testing systems.
Case 4: Developer in a Large Organization
Software developer working on a large, coordinated project in a large organization.
Support for enterprise login. Multiple developer environments i.e. current project and maintenance work on older projects. Testing typically on a target system in a testing lab.
Other users
While the developer workstation is the main target of this system and what we try to design this for, we do of course also welcome other users to the Fedora Workstation. In fact, many of the changes and improvements we expect to implement for developers will be equally beneficial to other user segments. For instance our plans around multi-screen handling and improved terminal functionality should also be highly beneficial to a system administrator. Or the work we are doing to provide a high performance graphics workstation would be useful to people who want a Linux gaming PC. Or a student who just wants a system with a productivity suite to write papers will of course get benefit from the fact that we do ship a good productivity suite. We will welcome feedback and requests from all our users and try to accommodate it, as long as it doesn't negatively impact our developer target group and we have people available who have the time and ability to work on the requests.