Added KDE3 version of KDE Guidance utilities

git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/applications/kde-guidance@1102646 283d02a7-25f6-0310-bc7c-ecb5cbfe19da

1 files changed, 48 insertions, 0 deletions

diff --git a/README.developers b/README.developers
new file mode 100644
index 0000000..82b98da
--- /dev/null
+++ b/README.developers
@@ -0,0 +1,48 @@
+
+Intro
+~~~~~
+In this file I want to try to explain some practical things about Guidance
+the "project" and some basic (and hopefully not too heavy) policies about how
+things work organisationally.
+
+-- 11 Feb 2007, Simon Edwards <simon@simonzone.com>
+
+
+Developers
+~~~~~~~~~~
+The list of developers as of 11 Feb 2007:
+
+Simon Edwards <simon@simonzone.com>, SVN username: sedwards, IRC: sime (unregistered)
+Sebastian Kügler <sebas@kde.nl>, SVN username: sebas, IRC: sebas
+Yuriy Kozlov <yuriy.kozlov@gmail.com>, SVN username: ykozlov, IRC: yuriy
+Martin Böhm <martin.bohm@kubuntu.org>, SVN username: martinbohm, IRC: ???
+
+"Lure" on #kubuntu-devel will join this list whether he likes it or not if he keeps
+on committing stuff to powermanager. ;-)
+
+
+Subversion
+~~~~~~~~~~
+Main development occurs in KDE's subversion repository in
+/trunk/kdereview/guidance. Branches of the stable releases can be found
+in svn under /kde/branches/guidance/. 0.6 was used in the Kubuntu Dapper, 0.7
+was in Edgy.
+
+
+Python source code
+~~~~~~~~~~~~~~~~~~
+Use 4 spaces for indentation, for the simple reason that it is very common
+and mixing indentation styles is a PITA.
+
+I (Simon) use Qt/KDE style naming conventions for methods. For variable
+names I'm a bit inconsistent but it is usually lower case of lower case
+with underscores. All I ask is that variable names be descriptive and
+understandable.
+
+TIP: When dealing with translated strings, use uncide() and not str(),
+otherwise things will break on translated desktops.
+
+
+Release procedure
+~~~~~~~~~~~~~~~~~
+[TODO: explain how a release tarball is created.]