Originally Posted by RevdKathy

Err no. I understood the first part of that (I think) but then you lost me.

The problem is I speak a range of 'elite' languages - medical, mental health, church (in several variants) theology (again several variants) and sci-fi. But I don't speak OSS. So there's lots of terms being used I simply don't understand. It feels like I'm working in a foreign language which I never got beyond 'o' level.

What exactly do you mean by "Breaking design guidelines for user interface would be considered a bug as there is an expected behaviour being deviated from."

My best guess you mean is that it isn't doing what I expect because I expect to understand it (at which point we're going in circles).

The problem is reproduceable in that I have a mild panic every time I look at the Bugzilla page.

As for brainstorm... I cam start a thread in the brainstorm forum, but if you want me to do more than that... well, I'm back to the same problem.

Originally Posted by Fargus

Sorry Kathy - got so used to you posting solutions on forum and contributing at a high level I forgot you're not up on the lingo yet: my short coming!

I was trying to say that if there is a definate behaviour that should be working but doesn't work as expected then it is a potential bug. For a bug report it is important that you explain how the problem can be reproduced so clear list of actions that allow someone else to get the same issue. As software is complex the other programs and settings you have might affect things too (hence the automated tools that Microsoft use).

The bit about design guidelines for the user interface: there is a guide for how Nokia expect the interface to work. This covers things such as screen layouts, actions on certain keypresses etcetera. This helps make applications look and feel the same to end users. If an application deviates from this way of doing things then whilst it might work properly it doesn't follow the standards so might be confusing. This is an issue with compliance and technically still a bug.

If an application simply doesn't do something you would like to have it do (such as make the tea) then this is a request to extend the functionality so should go via Brainstorm.

Apologies if this still makes no sense. Quite happy to chat interactively if it helps any: sometimes hard to do this without interaction and confirmation.

Originally Posted by RevdKathy

Six months down the line here there's a huge risk that all those people who jumped in with enthusiasm in the autum will be telling their friends to avoid anything maemo as it's 'buggy as all hell'.

Originally Posted by luca

Six months down the line there will be a new device, bugs filed for the previous one will be marked as fixed in the new device and you'll lose interest in reporting bugs.

Originally Posted by GeneralAntilles

Yeah, see, now this really isn't helpful at all. Please take your trolling somewhere else, thanks.

Originally Posted by Fargus

The bit about design guidelines for the user interface: there is a guide for how Nokia expect the interface to work. This covers things such as screen layouts, actions on certain keypresses etcetera. This helps make applications look and feel the same to end users. If an application deviates from this way of doing things then whilst it might work properly it doesn't follow the standards so might be confusing. This is an issue with compliance and technically still a bug.

Originally Posted by BrentDC

The thing is, "consumers" don't report bugs, so why design a system for them to do it?

We don't want 95% of users to report bugs. Most of them are woefully under-qualified to do so

Originally Posted by krisse

Ha ha ha...

Ohh... the comedy of it all...

Maybe I should start crying now.

It's phrases like this that make me think Maemo is doomed if it's going to be shaped by a community like this.