Mercurial > p > roundup > code
comparison doc/features.txt @ 740:2d50d6a17617
more marketing ;)
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Thu, 23 May 2002 02:26:48 +0000 |
| parents | c612747b1126 |
| children | b48a19a88b65 |
comparison
equal
deleted
inserted
replaced
| 739:c612747b1126 | 740:2d50d6a17617 |
|---|---|
| 8 from Ka-Ping Yee in the Software Carpentry "Track" design competition. | 8 from Ka-Ping Yee in the Software Carpentry "Track" design competition. |
| 9 | 9 |
| 10 | 10 |
| 11 *simple to use* | 11 *simple to use* |
| 12 - accessible through the web, email, command-line or Python programs | 12 - 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 | |
| 13 | 16 |
| 14 *simple to install* | 17 *simple to install* |
| 15 - installation takes about 10 minutes for a basic installation | 18 - 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 | |
| 16 | 21 |
| 17 *web interface* | 22 *web interface* |
| 18 - fully editable interfaces for indexing and display of items | 23 - fully editable interfaces for indexing and display of items |
| 19 - differentiates between anonymous, known and admin users | 24 - differentiates between anonymous, known and admin users |
| 20 - may be set up to require login, and may also only allow admin users | 25 - may be set up to require login, and may also only allow admin users |
| 21 to register new users | 26 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`_) | |
| 22 | 36 |
| 23 *e-mail interface* | 37 *_`e-mail interface`* |
| 24 - may be set up using sendmail-like delivery alias, POP polling or mailbox | 38 - may be set up using sendmail-like delivery alias, POP polling or mailbox |
| 25 polling | 39 polling |
| 26 - issues have their own mini mailing list (nosy list) | 40 - issues have their own mini mailing list (nosy list) |
| 41 - may auto-register users who send in mail and aren't known to roundup | |
| 27 - nosy list configuration controls how people are added and when messages | 42 - nosy list configuration controls how people are added and when messages |
| 28 are sent to the list | 43 are sent to the list |
| 29 - auto-filing of "unformatted" messages into a particular class | 44 - 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 | |
| 30 | 53 |
| 31 *command-line* | 54 *command-line* |
| 32 - may be used to interactively manage roundup databases | 55 - may be used to interactively manage roundup databases |
| 33 - may be scripted using standard shell scripting | 56 - 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 | |
| 34 | 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 | |
| 66 |