My biased list of Diablo bugs that bother me most:
1. Media Player not refreshing (3970).
2. MicroB certificate problems (349, 3792). It would be nice to use my N810 to access some of my secure company web sites.

A short update on the summit meeting was posted here. Hopefully we will have a repository and be able to start testing soon :-)

In the meantime, I would like to discuss the scope of the community updates project a bit.

In my mind, the updates should be rock-solid. It MUST be safe to tell a non-technical end-user to enable our repository, and when they do that they should get a better Diablo as a result and absolutely no nasty surprises. That means no experimental stuff (that includes things like the forthcoming TI GPU drivers, at least until they're well tested and found good enough), nothing that breaks compatibility with existing apps etc. Tested bug fixes and enhancements belong here, but new/experimental stuff should probably go to Mer.

I'm hopeful that by the time we've cleared the existing backlog this will encourage more contributors to submit patches so the project may continue for a while, but in the long run, Mer is the future and there's little point duplicating effort.

I agree.


We don't have a clear roadmap for Maemo, so the future is uncertain. Plenty of people are satisfied with stylus-based Diablo UI, now and in the future. It's only the HW that will need updating eventually.

My appreciation for all who discussed this & are involved. From my perspective, ANY maintenance to Diablo is better than nothing. It doesn't have to be visionary (although I appreciate that that stuff is cool). Each bug that was FiF represents a roadblock to Diablo usability (forcing users to stop using certain features or develop tortured workarounds). Each one that the community fixes is giving users back their tablets! From my perspective, little bug fixes is big stuff.

A small update: we now have a "community-diablo" bugzilla keyword for bugs with patches of interest to the community SSU project. I've marked all the ones I could find, but feel free to update any I might have missed.

If you're talking about the "Keywords" field on the bug page (example), when I change it I get this message:

"You tried to change the Keywords field from crash to crash, community-diablo , but only the assignee or reporter of the bug, or a sufficiently empowered user may change that field."

"I've got the power"... not! So it looks like only some people can do this.

Oops, I didn't realize that... Plan b: post bug numbers to this thread and I'll have a look at them.

Unfortunately that's just a binary attachment for a closed component, so we probably can't re-distribute it.

Pardon my ignorance, but what's SSU? What happens now that Fremantle is out? Is there a FAQ I can read?

check here:
http://wiki.maemo.org/SSU