From 4665ed6dfec8e549d47ae1b3234c0ba4d884ecc1 Mon Sep 17 00:00:00 2001
From: Gerhard Gonter <ggonter@gmail.com>
Date: Tue, 29 Dec 2015 10:17:09 +0100
Subject: [PATCH] wrong format

---
 README.textile | 38 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)
 create mode 100644 README.textile

diff --git a/README.textile b/README.textile
new file mode 100644
index 0000000..65ad425
--- /dev/null
+++ b/README.textile
@@ -0,0 +1,38 @@
+Perl script to sync individual projects to another Redmine instance.
+
+h2. Status
+
+My current goal is to synchronize one isolated project, which only
+has Wiki pages and attachments, from one Redmine instance to another.
+In the end, this project shall only be used on the destination instance.
+This is more complicated than initially assumed, but still leaves out
+the rather hairy problem of migrating issues or even issue numbers and
+whatever embedded in Wiki text.
+
+* Right now, migrating stuff that are related to users work.
+* Wiki migration seems to work now too.
+* Migrating attachments (using rsync'ed backup files) now work too.
+* Migrating watchers works.
+
+The next step: Maybe I should reconsider the core synchronization code,
+but this will have to wait until the migration job at hand is completed.
+
+h2. Notes
+
+h3. Perl
+
+Why Perl?  I'm not fluent enough in Ruby to even consider it as the
+tool of choice for this problem.  The script directly talks with
+the MySQL databases of the Redmine instances, it basically ignores
+the API.
+
+h3. To be improved
+
+The project's entry in 'wikis' whould be added to syncs by hand
+since Redmine creates the Wiki but the script currently doesn't
+check for that, it only looks at the syncs table.
+
+Also, the pre-configured trackers and roles need to be considered.
+
+h2. TODOs
+
-- 
GitLab