This implies adding triggers here: 'admin/build/trigger/comment') and configuration of actions here: 'admin/settings/actions'.
It is the uniform method of dealing with triggers and actions within Drupal.
This means (among other things) that role privileges can be set via the global "administer actions" option under the "system module" section of the "admin/user/permissions" form.
It would improve the consistency (user friendlessness) of the UI.
NB: If also (besides the optional core module Triggers) the module http://drupal.org/project/token is installed and enabled, more fine-tuned actions are configurable, like sending tokenized emails.
Drupal guidelines recommend maintainers to join forces (whenever modules offer overlapping functionality): http://drupal.org/node/23789
Advantages of joining forces:
1) As development effort is focused on ONE module (a SINGLE codebase), solving issues happen faster and (functionality, security and performance wise) better.
2) No incompatibilities can arise between similar enabled modules.
3) Less effort is needed from the maintainer and the rest of the module community (incl. submitting and processing issues and feature requests).
PS: If this module already supports this, then please consider this issue as a bug within the documentation and/ or project webpage, since then the information on it is unclear.
Comments
Comment #1
not_Dries_Buytaert commentedComment #2
deekayen commentedfixed in 6.x-2.x