From 24cb02ec7fd88c67096eefd886276f56de2f8bdf Mon Sep 17 00:00:00 2001
From: Benoit Mortier <benoit.mortier@opensides.be>
Date: Mon, 26 Mar 2018 17:57:28 +0200
Subject: [PATCH] :books: fix(readme): contrib/doc/README.ldap-migration should
 be merged to README.md

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>
---
 README.md                          | 19 ++++++++++++++++-
 contrib/docs/README.ldap-migration | 34 ------------------------------
 2 files changed, 18 insertions(+), 35 deletions(-)
 delete mode 100644 contrib/docs/README.ldap-migration

diff --git a/README.md b/README.md
index a02bb22f3..720b1c777 100644
--- a/README.md
+++ b/README.md
@@ -41,7 +41,24 @@ This question can be solved by creating:
 
 ## Installation and upgrade of FusionDirectory
 
-The installation and upgrade information is available on [fusiondirectory-install]
+The installation and upgrade information is available on [Install FusionDirectory][fusiondirectory-install]
+
+## Migration to FusionDirectory
+
+To migrate an existing LDAP tree, you've to do all steps [Install FusionDirectory][fusiondirectory-install],
+plus some modifications:
+
+* FusionDirectory only shows users that have the objectClass inetOrgPerson
+
+* FusionDirectory only recognizes subtrees (or departments in FusionDirectory's view of things) that have the objectClass gosaDepartment.
+  You can hide subtrees from FusionDirectory by not putting this objectClass inside.
+
+The FusionDirectory setup may be used to do these migrations, but it is not meant
+to work in every possible circumstance. Please be carefull when using it on
+productive system.
+
+That should be all. Entries should be visible in FusionDirectory now.
+Be aware that if your naming policy of user cn's differs from the way FusionDirectory handles it, the entries get rewritten to a FusionDirectory style dn.
 
 ## Get help
 
diff --git a/contrib/docs/README.ldap-migration b/contrib/docs/README.ldap-migration
deleted file mode 100644
index 801177188..000000000
--- a/contrib/docs/README.ldap-migration
+++ /dev/null
@@ -1,34 +0,0 @@
-LDAP TREE MIGRATION
-===================
-
-To migrate an existing LDAP tree, you've to do all steps from above,
-plus some modifications:
-
-- FusionDirectory only shows users that have the objectClass inetOrgPerson
-
-- FusionDirectory only recognizes subtrees (or departments in FusionDirectory's
-  view of things) that have the objectClass gosaDepartment. You can hide subtrees
-  from FusionDirectory by not putting this objectClass inside.
-
-The FusionDirectory setup may be used to do these migrations, but it is not meant
-to work in every possible circumstance. Please be carefull when using it on
-productive system.
-
-That should be all. Entries should be visible in FusionDirectory now. Be aware that if
-your naming policy of user cn's differs from the way FusionDirectory handles it, the
-entries get rewritten to a FusionDirectory style dn.
-
-Have fun!
-
----
-* Further information
-
-To improve this piece of software, please report all kind of errors using the bug tracker
-on https://gitlab.fusiondirectory.org/
-
-Documentation: http://documentation.fusiondirectory.org/
-Mailinglist:   http://lists.fusiondirectory.org/
-Irc:           #fusiondirectory on freenode
-
----
-The FusionDirectory project <contact@fusiondirectory.org>
-- 
GitLab