On Wed, Nov 27, 2013 at 1:13 PM, Matthew Miller
On Mon, Nov 25, 2013 at 01:59:06PM +0100, Christian Fredrik Kalager
> Feel free to let me know if I forgot to include some important feedback
> or if further clarifications are needed.
My thread about adding a sysadmin use case got somewhat derailed in the
details of multiple monitors and terminal handling, but I still would
*really* like to see
Case: Systems Administrator
Systems Administrator supporting Fedora or downstream distributions on
servers. Uses a web browser, and ssh with many terminal windows. May use
This is a _very_ important constituency for Fedora in general and Fedora
desktop in specific, and the needs aren't subsumed by the other cases.
Please don't leave this group out.
So here's the problem. We currently have:
then people want to add:
SysAdmin (which is explicitly mentioned in Other Users already)
General desktop user
If you group all of those together, they could be summed up as:
"Someone who (1) is voluntarily switching to Linux, (2) is familiar
with computers, but is not necessarily a hacker or developer, (3) is
likely to collaborate in some fashion when something's wrong with
Fedora, and (4) wants to use Fedora for general productivity, either
using desktop applications or a Web browser."
which, not surprisingly, is exactly what today's Fedora target
audience is. The same target audience definition that lead to
creating the 3 product approach because it wasn't suitable to today's
There needs to be focus. Where that focus is can surely be up for
debate, but I'd rather not just drive Workstation into irrelevance by
not learning from our past mistakes. We can't focus on everything or
we'll wind up gaining nothing.
I would suggest that instead of just saying "Role XXXX is important,
add it!" people should look at the existing user definitions in the
drafts and rework them as a set. Adding more and more is not going to
help us create a product.