Description of problem:
With Empathy now going to be part of GNOME and plans for Fedora 10 to include Empathy by default, we really would benefit from a easy way to migrate from Pidgin. If we can provide some way to import chat logs, contacts and settings from Pidgin, that would be awesome.
I believe upstream is already working on some of this, though I'm not sure if it will be done by F10.
(In reply to comment #1)
> I believe upstream is already working on some of this, though I'm not sure if
> it will be done by F10.
That's my understanding, as well.
I can imagine there are some people who simply have used Pidgin with auto-login enabled for so long that they have forgotten their own passphrases for their various IM accounts; and I'd hate for them to have to dig manually for them, though admittedly it would not be terribly difficult since they're stored in plaintext (~/.purple/accounts.xml).
Should part of this transition be having telepathy-haze and friends installed by-default (e.g., marked as such in comps)?
While I love Empathy being advocated as a default client, I'd hate for people to simply disregard it for lack of "out of the box" protocol support. (And even though there is an explicit README in the empathy package for these, I can imagine that, unfortunately, most people simply won't read it.)
Absolutely. If the decision on migrating to Empathy as the default client has been made, change the comps file to add the additional plugins by default and make sure it is documented in detail in the release notes. I am sure, some people will still miss the details but we can do our part.
(In reply to comment #3)
> Should part of this transition be having telepathy-haze and friends installed
> by-default (e.g., marked as such in comps)?
Ugh, please don't. That really defeats some of benefits of empathy IMO.
(In reply to comment #5)
> (In reply to comment #3)
> > Should part of this transition be having telepathy-haze and friends installed
> > by-default (e.g., marked as such in comps)?
> Ugh, please don't. That really defeats some of benefits of empathy IMO.
Hmm. Would it be better to add this ("install telepathy-haze for AIM/etc support") as a release note then?
Wait. Why does it defeat the benefits?
(In reply to comment #6)
> (In reply to comment #5)
> > Ugh, please don't. That really defeats some of benefits of empathy IMO.
> Hmm. Would it be better to add this ("install telepathy-haze for AIM/etc
> support") as a release note then?
Truthfully, it would be best if empathy had a ui that lists the plugins available (and what they provide) from packagekit, and then allow the user to install them as needed. Obviously, that would need quite a bit of work to do, which probably isn't reasonable in the F10 timeframe.
As you suggested it might be best to list the various telepathy connection managers, and what they provide in the release notes (though that isn't particularly user-friendly, since I wonder how many folks actually read the release notes). But if we start manadatorily requiring connection managers to each users request for funtionality, I see us eventually having the whole tp stack being pulled in.
Truthfully, I think Empathy is still too immature, since issues like this should be resolved before considering making it the default in the disto. But that's just my opinion. ;)
Peter, I was re-reading some of the earlier comments and I think the better solution would be to list telepathy-haze as a default in comps (like empathy) as Rahul suggested, but not requiring it in the spec file. that way if the user doesn't want tp-haze, they can simply remove it.
(In reply to comment #9)
> Peter, I was re-reading some of the earlier comments and I think the better
> solution would be to list telepathy-haze as a default in comps (like empathy)
> as Rahul suggested, but not requiring it in the spec file. that way if the
> user doesn't want tp-haze, they can simply remove it.
That's definitely a better idea. Would it be better to add it as a requires for the empathy item, or as a new entry altogether? (And if a new item, in which category should it be?)
(In reply to comment #8)
> As you suggested it might be best to list the various telepathy connection
> managers, and what they provide in the release notes (though that isn't
> particularly user-friendly, since I wonder how many folks actually read the
> release notes). But if we start manadatorily requiring connection managers to
> each users request for funtionality, I see us eventually having the whole tp
> stack being pulled in.
Note also that to the best of my knowledge, telepathy-haze supports only one-to-one chat, not MUC (or its equivalent in particular protocol).
An importing pidgin account info option has been added to empathy-2.25.2. I'm guessing it doesn't import over any pidgin logs, but I could be wrong since I haven't had a chance to look at the code.
Correct, Brian. The source code (src/empathy-import-pidgin.c and friends) currently imports only the necessary login details, not conversation logs.
(Apologies for the slight tardiness of the reply. I completely forgot about this bug until the recent fedora-desktop-list discussion reminded me of it.)
This seems the best place to offer comment on the default CMs installed with Empathy, since this is still open.
The current install of Empathy as of F11, is to include telepathy-haze and all the dependancies that pulls in along with it.
Empathy should not depend on any CMs, in it's purest form. I would like to have dependancy for telepathy-haze removed, and if MSN support is required, use telepathy-butterfly.
It was noted that Debian Recommend gabble and salut and Suggest haze and butterfly.
Recommends would be helpful in Fedora, but that's another bug :)
I think to simplify the move to Empathy, along with future updates, changing the rpm package to use Butterfly would be much better.
Any progress from upstream on importing Pidgin logs? I have years of chat logs and frequently need to refer back to them. Not possible to switch to Empathy before this gets implemented.
Currently I believe they are working on allowing Empathy to read pidgin logs, but not import them. That might have changed since the last time I looked at the bug though since I haven't looked at that bug in awhile.
I have split the "Empathy should not depend on telepathy-haze" issue into Bug 555366.
Reading the above comments, it sounds like log import is the only remaining issue. However, the upstream bug seems to indicate that a patch has been applied. I don't know if that has made its way into Fedora yet or satisfies everyone's request, but it might be cleaner to track that specific issue in a new bug.
I believe pidgin logs are handled now by tp-logger(1), but since I don't use pidgin I can't verify this. If someone can verify this, we can probably close this bug.
These days the empathy / telepathy stack of software components ranges from very weakly maintained to unmaintained. So I think it is safe to consider this as WONTFIX.
On second thoughts, empathy already supports importing account settings from pidgin and can access logs from it. So CURRENTRELEASE.