= eROPP =

is an external issue and bug tracking web site for the '''Radio Occultation Processing Package (ROPP)'''.
The system allows for browsing through the history of source code, documentation and test folders 
for various versions. Tickets for feature requests, bugs or any other issues with ROPP can be 
created and tracked. The system is based on Trac.


== Project Statistics ==

for the ROPP project (source code only) can be found [http://www.marquardt.sc/project_stats/ropp_src here].


== About Subversion ==

[http://subversion.tigris.org/ Subversion] is a version control system meant to be a replacement for CVS, 
and has most of CVS's features. Generally, Subversion's interface to a particular feature is similar to CVS's,
except where there's a compelling reason to do otherwise. The most important advantage over CVS is that 
Subversion does not only version file contents and file existence, but also directories, copies, and renames. 
Commits are also truly atomic; no part of a commit takes effect until the entire commit has succeeded. The most
visible difference to CVS is that CVS Revision numbers are per-commit, not per-file. Tags and branches are also handled somewhat differently (rather like copying things into dedicated directories).

Probably the best source about Subversion is the [http://svnbook.red-bean.com/nightly/en/index.html Subversion book]
(the link points to the current development version of the documentation; pdf and other versions of the book are 
[http://svnbook.red-bean.com/ available here].

Users without experience in version control systems like Subversion or CVS might benefit from this [http://svnbook.red-bean.com/nightly/en/svn.intro.html general introduction]; experienced CVS users will find
[http://svnbook.red-bean.com/nightly/en/svn.forcvs.html Subversion for CVS users] useful.

The subversion repository for ROPP can be accessed via the Subversion server at the URL
{{{
http://svn.marquardt.sc/svn/ropp/...
}}}
For example, checking out the actual development version of the entire source code into a subdirectory ropp_src would require
{{{
svn co http://svn.marquardt.sc/svn/ropp/ropp_src/trunk ropp_src
}}}
The commands 
{{{
svn co http://svn.marquardt.sc/svn/ropp/ropp_doc/trunk ropp_doc
svn co http://svn.marquardt.sc/svn/ropp/ropp_web/trunk ropp_web
svn co http://svn.marquardt.sc/svn/ropp/ropp_test/trunk ropp_test
}}}
will check out the documentation, web presentation, and test folder in a similar way. 

== About Trac ==

[http://trac.edgewall.com/ Trac] is a minimalistic approach to web-based management of
software projects. Its goal is to simplify effective tracking and handling of software issues,
enhancements and overall progress. All aspects of Trac have been designed with the single goal 
to help developers write software while staying out of the way and imposing as little as possible 
on a team's established process and culture.

There is some [wiki:TracGuide built-in documentation], a [http://projects.edgewall.com/trac/wiki/TracFaq FAQ], 
and a complete list of [wiki:TitleIndex local wiki pages].



== About this page ==

As all Wiki pages, this page is editable, this means that you can
modify the contents of this page simply by using your
web-browser as soon as you are logged in. Simply click on the "Edit this page" link at the bottom
of the page. WikiFormatting will give you a detailed description of
available Wiki formatting commands. The [wiki:TracGuide Trac documentation]
will also help you get started.

It is possible to configure Trac to better fit this project, especially in regard to ''components'', ''versions'' and ''milestones''. Unfortunately, this is only possible on a system administrator level; please contact me (christian AT marquardt DOT sc) about this.