
On 4/14/2010 at 10:14, James Ogley <riggwelter@opensuse.org> wrote: I had a message a couple of days ago from Ryan Paul, lead developer on Gwibber. He was apologising basically for the state of the Couch-based Gwibber and telling me that he's dropping it as soon as that version (to which, I think, Ubuntu are committed for their next release) is out the door.
He's already started working on Gwibber 3.0 which uses SQLite as a backend (and so, doesn't add any new esoteric requirements).
I've done a local build and what I have to say is that, although Ryan says it's a couple of weeks (only a couple of weeks!) off being ready for public consumption, it's already more stable and usable than the Couch version.
I'm inclined to commit it to home:Riggwelter:GNOME for a bit more testing. Given that it's already ahead of the Couch version, I'm also inclined to propose it for 11.3 which would mean we could drop the whole Couch stack too as I don't think anything else uses it (hence all the pain in getting it sorted for Gwibber).
RFC before I commit.
no objections at all from my side! Let's get rid of gwibber 2.29.x ! This is a beast that will cause much more trouble than we would like to have. Event hough I got it to start once in a while, I still have too many cases when it does not start (mostly desktop-couchdb related issues... couchdb as system service seems to run fine now and it also passes all of it's internal tests). A schema-less database sounds good in theory, but too often I read 'document type conflicts' and desktop-couch dies. GO FOR IT! Dominique -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org