@@ -10,25 +10,57 @@ from Ka-Ping Yee in the Software Carpentry "Track" design competition.
1010
1111*simple to use*
1212 - accessible through the web, email, command-line or Python programs
13+ - may be used to track bugs, features, user feedback, sales opportunities,
14+ ...
15+ - keeps a full history of changes to issues
1316
1417*simple to install*
1518 - installation takes about 10 minutes for a basic installation
19+ - two "template" schemas included in the distribution for you to base your
20+ tracker on
1621
1722*web interface*
1823 - fully editable interfaces for indexing and display of items
1924 - differentiates between anonymous, known and admin users
2025 - may be set up to require login, and may also only allow admin users
2126 to register new users
27+ - may be run through CGI as a normal cgi script, as a stand-alone
28+ web server, or through Zope
29+ - searching may be performed using many constraints, including a full-text
30+ search of messages attached to issues
31+ - file attachments (added through the web or email) are served up with the
32+ correct content-type and filename
33+ - email change messages generated by roundup appear to be sent by the
34+ person who made the change, but responses will go back through the nosy
35+ list by default (see `e-mail interface`_)
2236
23- *e-mail interface*
37+ *_` e-mail interface` *
2438 - may be set up using sendmail-like delivery alias, POP polling or mailbox
2539 polling
2640 - issues have their own mini mailing list (nosy list)
41+ - may auto-register users who send in mail and aren't known to roundup
2742 - nosy list configuration controls how people are added and when messages
2843 are sent to the list
2944 - auto-filing of "unformatted" messages into a particular class
45+ - e-mail attachments are handled sanely, being attached to the issue they're
46+ intended for, and forwarded on to the nosy list
47+ - sane handling of content-type and content-encoding of messages (text/plain
48+ preferred in all situations)
49+ - email packages that display threading will show issue messages correctly
50+ threaded
51+ - users may send in messages from multiple addresses and be associated
52+ with the same roundup username
3053
3154*command-line*
3255 - may be used to interactively manage roundup databases
3356 - may be scripted using standard shell scripting
57+ - roundup's API may also be used by other Python programs - a sample is
58+ provided that runs once a day and emails people their assigned issues
59+
60+ *highly configurable*
61+ - web interface HTML is fully editable
62+ - database schema is also fully editable
63+ - customised automatic auditors and reactors may be written that perform
64+ actions before and after changes are made to entries in the database
65+ - samples are provided for all types of configuration changes
3466
0 commit comments