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.