<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Roundup Features &mdash; Roundup v1.4 documentation</title>
<link rel="stylesheet" href="_static/style.css" type="text/css" />
<link rel="stylesheet" href="_static/pygments.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: '#',
VERSION: '1.4',
COLLAPSE_MODINDEX: false,
FILE_SUFFIX: '.html'
};
</script>
<script type="text/javascript" src="_static/jquery.js"></script>
<script type="text/javascript" src="_static/doctools.js"></script>
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
<link rel="top" title="Roundup v1.4 documentation" href="index.html" />
<link rel="next" title="Installing Roundup" href="installation.html" />
<link rel="prev" title="Roundup: an Issue-Tracking System for Knowledge Workers" href="index.html" />
</head>
<body>
<div class="header"><h1>Roundup</h1>
<div id="searchbox" style="display: none">
<form class="search" action="search.html" method="get">
<input type="text" name="q" size="18" />
<input type="submit" value="Search" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
<div class="navigation">
<div class="menu">
<h4>Previous topic</h4>
<p class="topless"><a href="index.html"
title="previous chapter">Roundup: an Issue-Tracking System for Knowledge Workers</a></p>
<h4>Next topic</h4>
<p class="topless"><a href="installation.html"
title="next chapter">Installing Roundup</a></p>
<h3>This Page</h3>
<ul class="this-page-menu">
<li><a href="_sources/features.txt"
rel="nofollow">Show Source</a></li>
</ul>
<div id="searchbox" style="display: none">
<h3>Quick search</h3>
<form class="search" action="search.html" method="get">
<input type="text" name="q" size="18" />
<input type="submit" value="Go" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
<p style="font-size: 90%">Enter search terms or a module, class or function name.</p>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
</div>
<div class="content">
<div class="related related-top">
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
accesskey="I">index</a></li>
<li class="right" >
<a href="installation.html" title="Installing Roundup"
accesskey="N">next</a></li>
<li class="right" >
<a href="index.html" title="Roundup: an Issue-Tracking System for Knowledge Workers"
accesskey="P">previous</a></li>
<li><a href="index.html">Roundup v1.4 documentation</a></li>
</ul>
</div>
<div class="section" id="roundup-features">
<h1>Roundup Features</h1>
<p>Roundup is a simple-to-use and -install issue-tracking system with
web, e-mail and command-line interfaces. It is based on the winning design
from Ka-Ping Yee in the Software Carpentry “Track” design competition.</p>
<dl class="docutils">
<dt><em>simple to install</em></dt>
<dd><ul class="first last simple">
<li>installation (including web interface) takes about 30 minutes</li>
<li>instant-gratification <tt class="docutils literal"><span class="pre">python</span> <span class="pre">demo.py</span></tt> :)</li>
<li>two templates included in the distribution for you to base your tracker on</li>
<li>play with the demo, customise it and then use <em>it</em> as the template for
your production tracker</li>
<li>requires <em>no</em> additional support software - python (2.3+ but not 3+) is
enough to get you going</li>
<li>easy to set up higher-performance storage backends like <a class="reference external" href="http://www.hwaci.com/sw/sqlite/">sqlite</a>,
<a class="reference external" href="http://sourceforge.net/projects/mysql-python">mysql</a> and <a class="reference external" href="http://initd.org/software/initd/psycopg">postgresql</a></li>
</ul>
</dd>
<dt><em>simple to use</em></dt>
<dd><ul class="first last simple">
<li>accessible through the web, email, command-line or Python programs</li>
<li>may be used to track bugs, features, user feedback, sales opportunities,
milestones, ...</li>
<li>automatically keeps a full history of changes to issues with
configurable verbosity and easy access to information about who created
or last modified <em>any</em> item in the database</li>
<li>issues have their own mini mailing list (nosy list)</li>
<li>users may sign themselves up, there may be automatic signup for
incoming email and users may handle their own password reset requests</li>
</ul>
</dd>
<dt><em>highly configurable</em></dt>
<dd><ul class="first last simple">
<li>web interface HTML is fully editable</li>
<li>database schema is also fully editable (only the “user” class is required)
with a full set of data types (including dates and many-to-many relations)
across all storages available</li>
<li>customised automatic auditors and reactors may be written that perform
actions before and after changes are made to entries in the database,
or may veto the creation or modification of items in the database</li>
<li>samples are provided for all manner of configuration changes and
customisations</li>
</ul>
</dd>
<dt><em>fast, scalable</em></dt>
<dd><ul class="first last simple">
<li>with the sqlite, mysql and postgresql backends, roundup is
also fast and scalable, easily handling thousands of issues and users
with decent response times</li>
<li>database indexes are automatically added for those backends that
support them (sqlite, mysql and postgresql)</li>
<li>indexed text searching giving fast responses to searches across all
messages and indexed string properties</li>
<li>support for the Xapian full-text indexing engine for large trackers</li>
</ul>
</dd>
<dt><em>documented</em></dt>
<dd><ul class="first last simple">
<li>documentation exists for installation, upgrading, maintenance, users and
customisation</li>
</ul>
</dd>
<dt><em>web interface</em></dt>
<dd><ul class="first last simple">
<li>fully editable interfaces for listing and display of items</li>
<li>extendable to include wizards, parent/meta bug displays, ...</li>
<li>differentiates between anonymous, known and admin users</li>
<li>may be set up to require login, and may also only allow admin users
to register new users</li>
<li>authentication of user registration and user-driven password resetting
using email and one time keys</li>
<li>may be run using WSGI or through CGI as a normal cgi script, as a
stand-alone web server, under mod_python or through Zope</li>
<li>searching may be performed using many constraints, including a full-text
search of messages attached to issues</li>
<li>file attachments (added through the web or email) are served up with the
correct content-type and filename</li>
<li>email change messages generated by roundup appear to be sent by the
person who made the change, but responses will go back through the nosy
list by default</li>
<li>flexible access control built around Permissions and Roles with assigned
Permissions</li>
<li>generates valid HTML4 or XHTML</li>
<li>detects concurrent user changes</li>
<li>saving and editing of user-defined queries which may optionally be
shared with other users</li>
</ul>
</dd>
<dt><em>e-mail interface</em></dt>
<dd><ul class="first last simple">
<li>may be set up using sendmail-like delivery alias, POP polling or mailbox
polling</li>
<li>may auto-register users who send in mail and aren’t known to roundup</li>
<li>nosy list configuration controls how people are added and when messages
are sent to the list</li>
<li>auto-filing of “unformatted” messages into a particular class</li>
<li>e-mail attachments are handled sanely, being attached to the issue they’re
intended for, and forwarded on to the nosy list</li>
<li>sane handling of content-type and content-encoding of messages (text/plain
preferred in all situations)</li>
<li>email packages that display threading will show issue messages correctly
threaded</li>
<li>users may send in messages from multiple addresses and be associated
with the same roundup username</li>
<li>built-in security features like TLS and APOP</li>
</ul>
</dd>
<dt><em>command-line</em></dt>
<dd><ul class="first last simple">
<li>may be used to interactively manage roundup databases</li>
<li>may be scripted using standard shell scripting</li>
<li>roundup’s API may also be used by other Python programs - a sample is
provided that runs once a day and emails people their assigned issues</li>
<li>a variety of sample shell scripts are provided (weekly reports, issue
generation, ...)</li>
</ul>
</dd>
<dt><em>xmlrpc interface</em></dt>
<dd><ul class="first last simple">
<li>simple remote tracker interface with basic HTTP authentication</li>
<li>provides same access to tracker as roundup-admin, but based on
XMLRPC calls</li>
</ul>
</dd>
</dl>
</div>
<div class="related related-bottom">
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
accesskey="I">index</a></li>
<li class="right" >
<a href="installation.html" title="Installing Roundup"
accesskey="N">next</a></li>
<li class="right" >
<a href="index.html" title="Roundup: an Issue-Tracking System for Knowledge Workers"
accesskey="P">previous</a></li>
<li><a href="index.html">Roundup v1.4 documentation</a></li>
</ul>
</div>
</div>
<div class="footer">
© Copyright 2009, Richard Jones.
<p class="source"><a href="_sources/features.txt" rel="nofollow">source</a></p>
</div>
</body>
</html>
