1st attempt at an initial import.

[qwerkisync] / qtc_packaging / debian_fremantle / README

diff --git a/qtc_packaging/debian_fremantle/README b/qtc_packaging/debian_fremantle/README
new file mode 100644 (file)
index 0000000..824cf65
--- /dev/null
+++ b/qtc_packaging/debian_fremantle/README
@@ -0,0 +1,33 @@
+The Debian Package qwerkisync
+----------------------------
+
+This package will import and export your communications data to and from files.
+
+It's alpha-quality. Understand this. That said, I use it and haven't had major
+problems with it yet.
+
+It will create backups of your communications database files each time it is
+used. These are located in the usual backups folder should you ever need to
+recover them manually. It will cycle these backups, keeping at most the last 3.
+
+Currently, it supports SMS message import/export to/from VMG files. I plan to
+add call logs, MMS, and chat log support. I also plan to add support for mutiple
+formats for each of these in time (i.e. Android-compatible formats). It also
+currently preserves SMS-transported data such as clender events and
+configuration data. these will show in the rtcom-messaging-ui as contact cards
+as that's the only attachment it expect SMSes to have. They have ot be stored
+however to ensure the export is the same as the import.
+
+The backends it currently supports are Maemo5's rtcom-eventlogger for all event
+types other than MMS and it will (hopefully!) shortly support Fmms on Maemo5 for
+MMSs.
+
+In the long-term, I plan to add MMS support to the normal rtcom-eventlogger (and
+fork Fmms to use this instead) and will add support for this format to the
+program.
+
+...in the long-long future I'd like to reimplement the rtcom-messaging-ui
+component so that's another closed-source package to tick off the freedom list,
+obviously adding support for the new events I'll be adding.
+
+ -- Jamie Thompson <maemo@jamie-thompson.co.uk>  Fri, 05 Aug 2011 11:32:52 +0100