[opensuse-gnome] Gwibber
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. -- James Ogley (riggwelter) openSUSE Member GNOME Team and Planet SUSE e: riggwelter@opensuse.org w: http://opensuse.org/GNOME t: @riggwelter w: http://www.planetsuse.org openSUSE: Get It, Discover It, Create It at http://www.opensuse.org -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Wed, 2010-04-14 at 09:14 +0100, James Ogley 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.
Personally I'm all for getting it into 11.3, even if it means all the hard work by yourself, DimStar et al was for not much. I'll install it now and let you know if I hit any issues. Thanks for your perseverance! Regards, Andy -- Andrew Wafaa, openSUSE Member: FunkyPenguin. PGP: 0x3A36312F openSUSE: Get It, Discover It, Create It at http://www.opensuse.org
RFC before I commit. Personally I'm all for getting it into 11.3
Gentlemen, start your engines... ogley@linux-ad02:~/Documents/buildservice/home:Riggwelter:GNOME/gwibber> osc commit Note that there are issues with replying & retweeting that Ryan intends to fix tomorrow. home:Riggwelter:GNOME -- James Ogley (riggwelter) openSUSE Member GNOME Team and Planet SUSE e: riggwelter@opensuse.org w: http://opensuse.org/GNOME t: @riggwelter w: http://www.planetsuse.org openSUSE: Get It, Discover It, Create It at http://www.opensuse.org -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
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
On Wednesday 14 April 2010 11:15:43 Dominique Leuenberger wrote:
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).
Ok, so should we cancel the submit requests for erlang and couchdb and remove them again from Factory? Yeah, sorry for the work to push the stack in but from what I hear, it looks like the sqlite push is the best way. Thanks Dominique! Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Wed, Apr 14, 2010 at 9:14 AM, 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.
That's great news; it never made sense to me that Gwibber would need to use a document store, or that you would want to sync anything besides your preferences, so Couch always seemed like a bizarre dependency for it. But I wonder how this will work. The Couch-based Gwibber is part of the new LTS release for Ubuntu, which means it will be supported for quite some time. I wonder if there will be pressure on Ryan to stick with Couch, if for no other reason than to make sure that the 2.30 release stays maintained for LTS reasons.
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).
I believe the Couch stack also stands in the way of having Ubuntu One desktop client packages. I'm not advocating that we invest a lot of time adding support for a competitor's proprietary sync solution, but certainly there are users that want it, so it's worth considering before dropping the whole Couch stack. Sandy -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On 4/14/2010 at 16:20, Sandy Armstrong <sanfordarmstrong@gmail.com> wrote: I believe the Couch stack also stands in the way of having Ubuntu One desktop client packages. I'm not advocating that we invest a lot of time adding support for a competitor's proprietary sync solution, but certainly there are users that want it, so it's worth considering before dropping the whole Couch stack.
I would not say we should just go ahead and drop the couch stack, but at least not having gwibber as the only consumer of it. Not having such a visible app require the stack gives us also more time in actually fixing that stack (couchdb itself is fine, desktop-couch is a mess, like so many python services I've seen (/rant) ) Dominique -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Wednesday 14 April 2010 16:25:34 Dominique Leuenberger wrote:
On 4/14/2010 at 16:20, Sandy Armstrong <sanfordarmstrong@gmail.com> wrote:
I believe the Couch stack also stands in the way of having Ubuntu One desktop client packages. I'm not advocating that we invest a lot of time adding support for a competitor's proprietary sync solution, but certainly there are users that want it, so it's worth considering before dropping the whole Couch stack.
I would not say we should just go ahead and drop the couch stack, but at least not having gwibber as the only consumer of it. Not having such a visible app require the stack gives us also more time in actually fixing that stack (couchdb itself is fine, desktop-couch is a mess, like so many python services I've seen (/rant) )
Ah, I should read everything before answering ;) So, ignore my previous email where I asked whether we should drop again the couchdb stack.... Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Wed, 2010-04-14 at 09:14 +0100, James Ogley 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.
How will that work with the "Feature and version freeze for the complete distribution"[1] that was set to April 9th? Cheers, Magnus [1] http://www.suse.de/~coolo/opensuse_11.3/ -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Wed, 2010-04-14 at 09:14 +0100, James Ogley 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.
How will that work with the "Feature and version freeze for the complete distribution" that was set to April 9th. Cheers, Magnus
-- James Ogley (riggwelter) openSUSE Member GNOME Team and Planet SUSE e: riggwelter@opensuse.org w: http://opensuse.org/GNOME t: @riggwelter w: http://www.planetsuse.org openSUSE: Get It, Discover It, Create It at http://www.opensuse.org
-- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On 4/15/2010 at 1:12, Magnus Boman <captain.magnus@gmail.com> wrote: On Wed, 2010-04-14 at 09:14 +0100, James Ogley 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.
How will that work with the "Feature and version freeze for the complete distribution" that was set to April 9th.
Well, let's all nicely look at Coolo. Gwibber situation can't get worse with the update which does not bring new dependencies to the Distribution (based on SQLIte) as compared to the current gwibber (2.29.9x.. tested up to .95) which in fact does not work reliable at all. @Coolo: I think I would like to take this opportunity for a defined exception from the version freeze to get gwibber 3.0 in. In case this is denied, I would probably have to opt to drop gwibber completely at this time (Which I assume is not what we would really like to do, as we do have an alternative option). Status of gwibber 2.29.95 at this time is: - CouchDB as a system service runs (it passes all it's internal tests. There were issues with the linking of libmozjs.so). But the service itself is not used by gwibber (only the couchdb binaries are. It launches a user session version of the db) - python-desktopcouch: The dbus service sometimes can start up correctly. Best chances are after executing rm -rf ~/.cache/desktop-couch/ ~/.local/share/desktop-couch/ ~/.config/desktop-couch/ But I did not test here neither the just released desktopcouch 0.6.4 - Some of the errors with starting python-desktopcouch actually seem to be errors in python-couchdb, like I see for example http://code.google.com/p/couchdb-python/issues/detail?id=121 very often). That's why I would like to get the exception to move to the new gwibber: with this high complexity of things that can break, chances that gwibber ever get's fully to work are low (the bugtracker at lp shows also very mixed feelings about the success). Dominique -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Thursday 15 April 2010 09:03:35 Dominique Leuenberger wrote:
[...] Well, let's all nicely look at Coolo. Gwibber situation can't get worse with the update which does not bring new dependencies to the Distribution (based on SQLIte) as compared to the current gwibber (2.29.9x.. tested up to .95) which in fact does not work reliable at all.
For leaf packages - and gwibber is a leaf package - Coolo in general grants this. I support the request and suggest you submit asap to openSUSE:Factory so that Coolo can review the changes, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
I support the request and suggest you submit asap to openSUSE:Factory so that Coolo can review the changes,
request id 37976 will put it in GNOME:Apps - can someone accept it and then push it to oS:F please? -- James Ogley (riggwelter) openSUSE Member GNOME Team and Planet SUSE e: riggwelter@opensuse.org w: http://opensuse.org/GNOME t: @riggwelter w: http://www.planetsuse.org openSUSE: Get It, Discover It, Create It at http://www.opensuse.org -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On 04/15/2010 at 11:03 AM, James Ogley <riggwelter@opensuse.org> wrote: I support the request and suggest you submit asap to openSUSE:Factory so that Coolo can review the changes,
request id 37976 will put it in GNOME:Apps - can someone accept it and then push it to oS:F please?
Gwibber 2.31.1 has been pushed (and already accepted!) in openSUSE:Factory. Happy testing all! BRyen mentioned yesterday that he had to re-create his accounts, which seemed to be to only pitfall so far. Looking forward for mor test results (it can't be as bad as 2.29.x was :) ) James, thank you very much for your efforts on this and picking it up. Dominique -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
participants (6)
-
Andreas Jaeger -
Andrew Wafaa -
Dominique Leuenberger -
James Ogley -
Magnus Boman -
Sandy Armstrong