![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
diff --git a/doc/developers.txt b/doc/developers.txt
index 6698616dd14d5994e5335e0fd91ae089c74adb36..cc2dee28cd52d7808a63f60663e773e1548f6a0e 100644 (file)
--- a/doc/developers.txt
+++ b/doc/developers.txt
- roundup-dev mailing list at
http://lists.sourceforge.net/mailman/listinfo/roundup-devel
-- Sourceforge's issue trackers at
- https://sourceforge.net/tracker/?group_id=31577
+- The issue tracker running at
+ http://issues.roundup-tracker.org/
-Website, wiki, issue tracker
-----------------------------
+Website, wiki
+-------------
-1. Log into <username>,roundup@shell.sourceforge.net
+1. ssh -t <username>,roundup@shell.sourceforge.net create
2. cd /home/groups/r/ro/roundup
3. follow instructions in README.txt
+Issue Tracker
+-------------
+
+The tracker resides on psf.upfronthosting.co.za. The roundup installation
+belongs to the user roundup. In ~roundup, all trackers are stored and
+the roundup code itself. roundup is started through /etc/init.d/roundup;
+other parts of the installation are started through
+/etc/init.d/{postgresql-8-1,spambayes,postfix}.
+
+The machine is operated by Upfronthosting in South Africa. The meta
+tracker is http://psf.upfronthosting.co.za/roundup/meta/
+In this tracker, Upfronthosting people are the users izak and roche.
+
+The Roundup tracker http://issues.roundup-tracker.org/ is in
+~roundup/trackers/roundup
+
+The configuration is in the "web/trunk/issues" section of Roundup's
+Subversion repository and copied manually to the live tracker.
+
+A checkout of the roundup sources is in ~roundup/src/roundup-src.
+
+
Small Changes
-------------
-Most small changes can be submitted through the `feature tracker`_, with
+Most small changes can be submitted through the issue tracker, with
patches attached that give context diffs of the affected source.
SVN Access
----------
-To get SVN access, contact richard@users.sourceforge.net.
+See http://www.roundup-tracker.org/code.html.
+For all other questions ask on the development mailinglist.
Project Rules
- 80 column width code
- 4-space indentations
-- All modules must have a CVS Id line near the top
+- All modules must have an Id line near the top
Other project rules:
where there's missing documentation) and changes to tracker configuration
must be logged in the upgrading document.
- subscribe to roundup-checkins to receive checkin notifications from the
- other developers with CVS access
+ other developers with write access to the source-code repository.
- discuss any changes with the other developers on roundup-dev. If nothing
else, this makes sure there's no rude shocks
- write unit tests for changes you make (where possible), and ensure that
Debugging Aids
--------------
-Try turning on logging of DEBUG level messages. This may be done a number
-of ways, depending on what it is you're testing:
-
-1. If you're testing the database unit tests, then set the environment
- variable ``LOGGING_LEVEL=DEBUG``. This may be done like so:
-
- LOGGING_LEVEL=DEBUG python run_tests.py
-
- This variable replaces the older HYPERDBDEBUG environment var.
-
-2. If you're testing a particular tracker, then set the logging level in
- your tracker's ``config.ini``.
-
+See `debugging.txt`_.
Internationalization Notes
--------------------------
message translators.
4. Translated Message Files are compiled into binary form (_`MO` files)
- and stored in ``locale`` directory (but not kept in the `Roundup
- CVS`_ repository, as they may be easily made from PO files).
+ and stored in ``locale`` directory (but not kept in the source code
+ repository, as they may be easily made from PO files).
See `Compiling Message Catalogs`_ section.
5. Roundup installer creates runtime locale structure on the file
This means that you need both `GNU gettext`_ tools and `PO utilities`_
to build the Message Template File yourself.
-Latest Message Template File is kept in `Roundup CVS`_ and distributed
-with `Roundup Source`_. If you wish to rebuild the template yourself,
+Latest Message Template File is kept in the source code repository
+and distributed with `Roundup Source`_.
+If you wish to rebuild the template yourself,
make sure that you have both ``xpot`` and ``xgettext`` installed and
just run ``gmake`` (or ``make``, if you are on a `GNU`_ system like
`linux`_ or `cygwin`_) in the ``locale`` directory.
http://vim.sourceforge.net/scripts/script.php?script_id=695
.. _PO utilities: http://po-utils.progiciels-bpi.ca/
.. _poEdit: http://poedit.sourceforge.net/
-.. _Roundup CVS: http://sourceforge.net/cvs/?group_id=31577
.. _Roundup Source:
.. _Roundup source distribution:
.. _Roundup binary distribution:
http://dev.zope.org/Wikis/DevSite/Projects/ZPT/TALES%20Specification%201.3
.. _vim: http://www.vim.org/
.. _ZPTInternationalizationSupport: http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ZPTInternationalizationSupport
-.. _feature tracker: http://sourceforge.net/tracker/?group_id=31577&atid=402791