Sorry for being a bit late with chimming in again, was travelling then knocked out with
acute food poisoning.
Anyway, the second non-heading sentence of the document says 'We want to create a
stable, integrated, polished and user friendly system that can appeal to a wide general
audience, but with a special focus on providing a platform for development of server side
and client applications.' This is in the Mission statement. So I still fail to see how
we are not covering this aspect of things.
Would it help people if we boldface that line?
----- Original Message -----
From: "Bill Nottingham" <notting(a)redhat.com>
To: "Discussions about development for the Fedora desktop"
Sent: Tuesday, December 10, 2013 8:45:16 PM
Subject: Re: Workstation PRD approval
Josh Boyer (jwboyer(a)fedoraproject.org) said:
However, "general desktop _usage_" is certainly within
Developers, sysadmins, students, grandma, all use a desktop. They
read email. They use a web browser. The basics of using your
computer are implicit as Christian says, but Matthew contends leaving
them out reads as if there will be no focus given to them.
I would argue the target users are additive to general desktop usage.
So instead, perhaps the PRD could incorporate somewhere that we wish
to produce a Workstation that is high quality and usable for daily
computing but with focus improvements in the developer areas. This
could perhaps be done very simply as a line addition or slight
rewording in the mission statement.
This seems like a worthwhile effort to clarify. If I look at the latest
draft of the PRD, it does:
- Developer type A
- Developer type B
- Developer type C
- Developer type D
- Other users
Plans, Policies and Work:
- Robust upgrades (not developer specific at all)
- Quality releases (not developer specific at all)
- Better upgrade/rollback control (not developer specific at all)
- 3rd party software (not developer specific at all)
- Fedora ecosystem integration (not developer specific at all)
- Standardize/unify Linux desktop space (only relevant for platform
developers, which is not a developer type called out above)
- Develop app guidelines (only relevant for a subset of developers that
isn't a specifc one of A/B/C/D above)
- Container-based app install (only relevant for a subset...)
- Encapsulated dev environments (developer specific)
So I would agree there's a bit of a disconnect in the document between what
is said to be targeted and what is planned to be done.
desktop mailing list