* Created "old" branch and moved stuff

[gosa.git] / gosa-core / README

diff --git a/gosa-core/README b/gosa-core/README
deleted file mode 100644 (file)
index 15bd73e..0000000
--- a/gosa-core/README
+++ /dev/null
@@ -1,48 +0,0 @@
-GOsa 2.6 README
-===============
-
-* Information
-
-GOsa is a LDAP administration frontend for user administration. It
-is NO GENERIC frontend to dictionary servers. Informations are stored
-in the way the underlying conecpts suppose them to be stored (i.e.
-people accounts are stored in "ou=people" subtrees, etc.) This can
-be configured marginally.
-
-Complete setups applying Kerberos, AFS, LDAP, Mail, Proxy and Fax setups
-are not trivial at all. You should be familiar with these components and
-with your UNIX installation, of cause. This file is (and will not be)
-an introduction to any of these components. See INSTALL for a quick
-overview about what to do, to get the things up and running. A complete
-GOsa infrastructure howto is work in progress and not released yet.
-
-
-* Translations
-
-GOsa is not available in your native language? Just take the message.po
-file out of the locales/core directory and put your translations into the
-msgstr fields. You may look at the de/LC_MESSAGES for the way how it
-works.
-
-If you're ready with that, create a directory for your language using
-the ISO shortcuts (i.e. es for spain) with a subdirectory LC_MESSAGES.
-Make sure your apache has locale support or, in case of debian,
-that the specific locale will be generated (via dpkg-reconfigure locales).
-
-You may want your translations to be included in the main GOsa repository,
-then just send the .po file to me.
-
-Run update-gosa after you've added translations in order to let GOsa
-compile and re-sync the translations.
-
-
-* NOTES
-
-Be sure that 'gosaUserTemplates' are not able to log into your server,
-since they may have no password set. Example configs can be found in
-the contrib directory.
-
-Have fun!
-
----
-Cajus Pollmeier <pollmeier@gonicus.de>