@@ -19,8 +19,8 @@ All development is coordinated through two resources:
1919
2020- roundup-dev mailing list at
2121 http://lists.sourceforge.net/mailman/listinfo/roundup-devel
22- - Sourceforge's issue trackers at
23- https ://sourceforge.net/ tracker/?group_id=31577
22+ - The issue tracker running at
23+ http ://issues.roundup- tracker.org/
2424
2525Website, wiki, issue tracker
2626----------------------------
@@ -33,14 +33,15 @@ Website, wiki, issue tracker
3333Small Changes
3434-------------
3535
36- Most small changes can be submitted through the `feature tracker`_ , with
36+ Most small changes can be submitted through the issue tracker, with
3737patches attached that give context diffs of the affected source.
3838
3939
4040SVN Access
4141----------
4242
43- To get SVN access, contact
[email protected] .
43+ See http://www.roundup-tracker.org/code.html.
44+ For all other questions ask on the development mailinglist.
4445
4546
4647Project Rules
@@ -51,15 +52,15 @@ relaxed sometimes). In short:
5152
5253- 80 column width code
5354- 4-space indentations
54- - All modules must have a CVS Id line near the top
55+ - All modules must have an Id line near the top
5556
5657Other project rules:
5758
5859- New functionality must be documented, even briefly (so at least we know
5960 where there's missing documentation) and changes to tracker configuration
6061 must be logged in the upgrading document.
6162- subscribe to roundup-checkins to receive checkin notifications from the
62- other developers with CVS access
63+ other developers with write access to the source-code repository.
6364- discuss any changes with the other developers on roundup-dev. If nothing
6465 else, this makes sure there's no rude shocks
6566- write unit tests for changes you make (where possible), and ensure that
@@ -109,8 +110,8 @@ How stuff works:
109110 message translators.
110111
1111124. Translated Message Files are compiled into binary form (_`MO` files)
112- and stored in ``locale`` directory (but not kept in the `Roundup
113- CVS`_ repository, as they may be easily made from PO files).
113+ and stored in ``locale`` directory (but not kept in the source code
114+ repository, as they may be easily made from PO files).
114115 See `Compiling Message Catalogs`_ section.
115116
1161175. Roundup installer creates runtime locale structure on the file
@@ -311,8 +312,9 @@ Roundup overcomes these limitations by using both of these utilities.
311312This means that you need both `GNU gettext`_ tools and `PO utilities`_
312313to build the Message Template File yourself.
313314
314- Latest Message Template File is kept in `Roundup CVS`_ and distributed
315- with `Roundup Source`_. If you wish to rebuild the template yourself,
315+ Latest Message Template File is kept in the source code repository
316+ and distributed with `Roundup Source`_.
317+ If you wish to rebuild the template yourself,
316318make sure that you have both ``xpot`` and ``xgettext`` installed and
317319just run ``gmake`` (or ``make``, if you are on a `GNU`_ system like
318320`linux`_ or `cygwin`_) in the ``locale`` directory.
@@ -416,7 +418,6 @@ At run time, Roundup automatically compiles message catalogs whenever
416418 http://vim.sourceforge.net/scripts/script.php?script_id=695
417419.. _PO utilities: http://po-utils.progiciels-bpi.ca/
418420.. _poEdit: http://poedit.sourceforge.net/
419- .. _Roundup CVS: http://sourceforge.net/cvs/?group_id=31577
420421.. _Roundup Source:
421422.. _Roundup source distribution:
422423.. _Roundup binary distribution:
@@ -429,5 +430,4 @@ At run time, Roundup automatically compiles message catalogs whenever
429430 http://dev.zope.org/Wikis/DevSite/Projects/ZPT/TALES%20Specification%201.3
430431.. _vim: http://www.vim.org/
431432.. _ZPTInternationalizationSupport: http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ZPTInternationalizationSupport
432- .. _feature tracker: http://sourceforge.net/tracker/?group_id=31577&atid=402791
433433
0 commit comments