view detectors/README.txt @ 7697:c73a1177c2b2

fix: roundup-demo, interactive mode would nuke an existing tracker. Tonu Mikk demonstrated a bug in roundup-demo. When invoked without a tracker home on the command line, it would nuke an existing directory specified interactively. There is still a minor bug. If an invalid home directory is specified, roundup-demo will prompt for the template to use before reporting: Error: Refusing to nuke non-tracker directory: but this doesn't cause data loss so not worth fixing at this time.
author John Rouillard <rouilj@ieee.org>
date Wed, 08 Nov 2023 21:18:34 -0500
parents b2eb59ada444
children e738377b4ffe
line wrap: on
line source

This directory has some detector examples that you can use to get
ideas on implementing your own detectors.

These are provides on an as-is basis. When they were added, they
worked for somebody and were considered a useful example.

The roundup team will attempt to keep them up to date with major
changes as they happen, but there are no guarantees that these will
work out of the box. If you find them out of date and have patches to
make them work against newer versions of roundup, please open an issue
at:

   https://issues.roundup-tracker.org

The current inventory is:

creator_resolution.py - only allow the creator of the issue to resolve it

emailauditor.py - Rename .eml files (from email multi-part bodies) to
                  .mht so they can be downloaded/viewed in Internet Explorer.

irker.py - communicate with irkerd to allow roundtup to send announcements
           to an IRC channel.

newissuecopy.py - notify a team email address (hardcoded in the script)
		  when a new issue arrives.

newitemcopy.py - email the DISPATCHER address when new issues, users,
                 keywords etc. are created. Kind of an expanded version
		 of newissuecopy.

Roundup Issue Tracker: http://roundup-tracker.org/