getting images together for 1.0

[Aaron J. Seigo]

On Wednesday, August 31, 2011 14:38:09 Thomas Pfeiffer wrote:
>  On Tue, 30 Aug 2011 18:11:23 +0200, Aaron J. Seigo wrote:
> > On Tuesday, August 30, 2011 15:07:06 Marco Martin wrote:
> >> a very important thing for 1.0 is the final demo image since the
> >> project
> >> mostly will be judged from the finished, ready to run system.
> > 
> > yes; and in that vein i think we need to shift from thinking "demo"
> > to
> > thinking "product". we can include a set of demo configurations that
> > people
> > doing demos can put on their tablet. but the defaults ought to be for
> > actual
> > usage for our users .
> 
>  I'd say that 1.0 should be a "Minimum Viable Product"
>  (http://en.wikipedia.org/wiki/Minimum_viable_product) rather than a
>  demo, which means:

+1

>  It should have what's needed to be of actual value to the user. No

even that's a bit broad for the first release (we don't have a way to add new 
widgets or applications easily, ala an 'app store', for instance)

>  Making things shiny is nice, but it won't help if the user can't make
>  actual use of the product.

agreed; thing is, we're at the point where the product is useful, but it now 
is bad need of being made tidy, consistent, performant, beautiful .. iow 
"shiny"

>  That's what makes the difference between a tech demo and a product.

all of our use cases, with the exception of recommendations, currently work. 
the primary use cases are:

* launch an application
* find an application
* switch between applications
* switch to the home screen
* close an application
* switch between activities
* create an activity
* configure an activity
* delete an activity
* add items to an activity with the + button
* add items to an activity with SLC
* add items to an activity via the recommendations panel (this one is still a 
WIP)

supporting use cases are:

* connect to a network
* monitor status of the device (battery, bluetooth, time, etc)
* put the device to sleep
* see notifications as they occur

as such, all of our use cases (save one) work in the strictest sense of the 
word. while each use case needs testing (and that is welcome), where we are at 
with development is "making the components that enable the use cases as good 
as they can be". that means things like:

* fixing functional bugs
* visual continuity and detail
* ensuring touch usability
* improving performance

the process of defining use cases and making sure we meet them is something we 
will start again for Plasma Active Two. right now we're at a different point 
in the development cycle, as i can do everything (save one thing) that we have 
defined as must haves for the first release.

> > perhaps we should focus on our own issues first and go after the
> > deeper
> > integration problems across the OS once we've run out of things to
> > clean up in
> > our own code.
> 
>  I don't know how important the Meego platform is for us, but if it is

it's important, but not in the sense that it needs to be ready as a finished 
product right now. that we have packages for it and that things run is the 
critical goal for this stage.

making a conman backend for the network UI is not a task we have the resources 
for right now, though that would change almost immediately as soon as we would 
get our first meego based device project.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/active/attachments/20110831/de3d2a69/attachment.sig>