[maemo-community] Fw: Proposal: MeeGo User Experience Framework working group
From: Randall Arnold texrat at ovi.comDate: Thu Mar 4 16:19:05 EET 2010
- Previous message: Fw: Proposal: MeeGo User Experience Framework working group
- Next message: Fw: Proposal: MeeGo User Experience Framework working group
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
----- Original message ----- > Randall, > > I am thinking along the line of something like a sort of "expert" > system, a web ui, that offers bug/problem domains to the user to > choose from. Then according to the problem domains a set of question > are presented for the user to answer with minimum free text. And so on > and forth. We could even have something like this on the device, as a > complementary test-case or use-case to validate against a fix when it > is out. > > What do you think? > > Sivan That is right on target with what I propose, especially the on-device aspect. Now you have me thinking my presentation comes up short... ; ) Randy > > On Thu, Mar 4, 2010 at 3:52 PM, Randall Arnold <texrat at ovi.com> wrote: > > > > ----- Original message ----- > > > Hi, > > > > > > ext Randall Arnold wrote: > > > > Thanks Attila! I just uploaded a more recent update to the PDF > > > > (http://maemo-daemons.org/MeeGo_User_Experience_Framework.pdf) > > > > based on helpful feedback so far. > > > > > > Some comments on the bug reporting thing. > > > > > > We already have Crash reporter which collects crashes. > > > > > > > > > Creating automated bug reports from crashes isn't useful because: > > > > > > * Users don't write detailed enough use-case descriptions > > > to the crash uploads. It's slightly too inconvenient to > > > do that with the device. > > > > > > * Bugs are related to use-cases, not crashes. Without a reproducible > > > use-case, bugs are usually worthless as you cannot even verify > > > potential fixes to them i.e. tell when the issue is fixed. > > > > > > > > > Telling for which _already existing_ bug crash is related to is > > > useful though and Crash reporter already supports that for (internal) > > > bugs. Due to screen size constraints bug number is given as a keyword > > > in note field instead of there being a separate field for it though. > > > There are going to be some updates to Crash reporter soon so that user > > > can select which bugs to upload (so that unrelated core dumps can be > > > uploaded separately or ignored). > > > > > > > > > Crash reporting isn't currently targeted for normal users > > > for few reasons: > > > > > > * Crash dumps are large and can contain private information > > > (like passwords). Hopefully in Harmattan we can can use > > > minidumps that contain only enough information for backtraces, > > > not all the process data. > > > > > > * Installing syslog means that user's rootfs can run out of space > > > if the log file grows too large (syslog is run as root). Syslog > > > can also contain private information (user names etc). > > > > > > * Crash dumps in heavily loaded device will make the situation > > > worse (whole crashing process needs to be swapped in for core > > > dump etc). > > > > > > > > > - Eero > > > > Thanks for the information Eero. However, I'm looking to overcome the issues > > you cite rather than just accept them as inescapable. > > > > Randy > > > > -------------------------------------------------------------- > > Ovi Mail: Free email account from Nokia > > http://mail.ovi.com > > > > _______________________________________________ > > maemo-developers mailing list > > maemo-developers at maemo.org > > https://lists.maemo.org/mailman/listinfo/maemo-developers > > > > -------------------------------------------------------------- Ovi Mail: Free email account from Nokia http://mail.ovi.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.maemo.org/pipermail/maemo-community/attachments/20100304/aaaad802/attachment.htm>
- Previous message: Fw: Proposal: MeeGo User Experience Framework working group
- Next message: Fw: Proposal: MeeGo User Experience Framework working group
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]