| Summary: | Kopete Chat log migration | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] telepathy | Reporter: | George Goldberg <grundleborg> |
| Component: | kopete-migrator | Assignee: | Telepathy Bugs <kde-telepathy-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | ddomenichelli, dvratil, kde |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | 0.6-next | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | commits.kde.org/telepathy-common-internals/79e43703dac07ed3e24f9a23d2b07a711d4a530b | Version Fixed In: | 0.6.0 |
| Attachments: | Conversion script | ||
|
Description
George Goldberg
2010-07-28 11:33:00 UTC
vHanda imported gmail accounts chat log in nepomuk (see http://vhanda.in/blog/2012/01/chat-logs-in-nepomuk/ ) We should do the same using kopete log files My current log viewer pulls stuff directly from tp-logger so this won't help. Also VHanda's code is very "prototype"-y (his words). It relies on manually downloading a load of files and running the script on each file individually. It's cool demo stuff, but a long way from something actually shippable. I know, I'm looking at the far future, and I'm thinking that instead of using nepomuk for logs, we should just write some nepomuk service to import them from tp-logger... One day we might have a log viewer that imports logs from nepomuk, and we will have already all data there. There is soo much discussion to have on this topic that neither bug reports or the mailing list is a good solution. I can see 9 different possible ways to do this, each with pros and cons. I have created a wiki page here: http://community.kde.org/Real-Time_Communication_and_Collaboration/Tasks/KopeteLogs. Please add to the discussion on any of these. Created attachment 69782 [details]
Conversion script
Alin wrote this script to convert kopete logs to tp-logger xml
Closing as fixed since we now have the log importer implementation in common-internals and utilize it in Accounts KCM and LogViewer. |