The detectors directory of 1.4.8 contains:
creator_resolution.py  emailauditor.py  newissuecopy.py

In 1.4.9 the directory does not exist.

In the svn repository I found:

------------------------------------------------------------------------
r4221 | stefan | 2009-06-17 03:45:25 +0200 (Wed, 17 Jun 2009) | 1 line

Remove obsolete detectors.
------------------------------------------------------------------------

But this isn't mentioned in the changelog or release notes,
and I still have to look at the current docs what I should use instead
of newissuecopy.py

doc/customizing.txt still contains the section
"Additional Detectors Ready For Use"
talking about the three deleted detectors.

On IRC stefan said that he removed the detectors directory because it is
not used by the tracker templates.
He said there is no reason for the Roundup project to ship them, they
can easily be written by end-users.

Personally I think newissuecopy.py is very precious, even if it is
simple enough that advanced end-users would be able to write it on their
own.
Just changing one email address simply is more convenient than that.

Personally, I think that a batch of sample code is really nice to have
to get started. I also think that shipping three small files should not
hurt anyone.

In any case, the change wasn't fully executed, as setup.py still
mentions the detectors subdirectory.

adding stefan to nosy

FWIW: I also agree that shipping essential buildings blocks is a good 
idea. The only potential issues I see is that the documentation might
not match the shipped script anymore, but I propose to solve this by 
generating the documentation out of the script, so that this is only 
one source.

I would like the sample detectors back too ;)

I also agree that `newissuecopy.py' is important.  After reading the
config comments:

  # The 'dispatcher' is a role that can get notified
  # of new items to the database.

It seems to me that DISPATCHER_EMAIL should be notified of all new
items, not just bounced messages as is currently hardcoded into
Mailer.bounce_message.

I've attached a tweaked version of `newissuecopy.py' that implements
this for all items.  I thing that a number of email-generating methods
from IssueClass should actually be Item methods, so they can also be
used on non-Issue nodes.  This would remove a lot of the duplicated
code from my `newitemcopy.py'

* W. Trevor King <issues@roundup-tracker.org> [20120515 18:54]:
> I also agree that `newissuecopy.py' is important.  After reading the
> config comments:
> 
>   # The 'dispatcher' is a role that can get notified
>   # of new items to the database.
> 
> It seems to me that DISPATCHER_EMAIL should be notified of all new
> items, not just bounced messages as is currently hardcoded into
> Mailer.bounce_message.
> 
> I've attached a tweaked version of `newissuecopy.py' that implements
> this for all items.  I thing that a number of email-generating methods
> from IssueClass should actually be Item methods, so they can also be
> used on non-Issue nodes.  This would remove a lot of the duplicated
> code from my `newitemcopy.py'

We nearly always use newissuecopy.py to inform some users or a
public mailing list about new issues (or in one case new merge
entries), but not about everything.

DISPATCHER_EMAIL is the supervisor who wants to be notified about
everything, so this is something different.

First step should be to revive the removed detectors. But yes,
providing more flexibility with less code duplication would be nice,
as would be the possibility to set the newissuecopy recipients in
config.ini (without preventing configuration in newissuecopy.py
itself of course).

Regards,
Thomas

I went ahead and restored the detectors in changeset 6b32e9dac625
(directly after 1.4.20), but I can't change the status of this issue.

Trevor, can you open a new issue with your improvement please? 
(As this issue is quite specific about restoring the old situation. I believe you are
changing some of the conditions how this is used and I haven't fully thought it 
through.)

On Wed, Aug 01, 2012 at 06:55:54PM +0000, Bernhard Reiter wrote:
> Trevor, can you open a new issue with your improvement please? 

Split off as issue2550767.