Mercurial > p > roundup > code
diff doc/developers.txt @ 4254:8d3582271a99
Minor update of doc/developers.txt...
...to point to the new resources on www.roundup-tracker.org:
- pointed to the new tracker
- removed references to CVS
- removed "macros": _Roundup CVS, _feature tracker
- hinted at http://www.roundup-tracker.org/code.html and the mailinglist
instead of duplicating information
| author | Bernhard Reiter <Bernhard.Reiter@intevation.de> |
|---|---|
| date | Thu, 17 Sep 2009 09:54:49 +0000 |
| parents | f5d7562bed95 |
| children | aab5dba70839 |
line wrap: on
line diff
--- a/doc/developers.txt Mon Sep 14 20:34:50 2009 +0000 +++ b/doc/developers.txt Thu Sep 17 09:54:49 2009 +0000 @@ -19,8 +19,8 @@ - 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 ---------------------------- @@ -33,14 +33,15 @@ 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 @@ -51,7 +52,7 @@ - 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: @@ -59,7 +60,7 @@ 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 @@ -109,8 +110,8 @@ 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 @@ -311,8 +312,9 @@ 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. @@ -416,7 +418,6 @@ 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: @@ -429,5 +430,4 @@ 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
