This is how I'm handling requests for new Majordomo features these
days, FYI. If there's a feature you'd like to see added to Majordomo,
please read this (especially if you intend to add it yourself!).
-Brent
--------
[ This is a form letter, sent to anybody who asks me for Yet Another
Majordomo Feature. Don't feel like I'm picking on you. -Brent]
Thanks for your suggestion for new Majordomo features.
If I like your idea, I may implement it myself. I seldom have time
to do that sort of work, though, and Majordomo already has most of the
features that _I_ use, so don't hold your breath...
The best way to get a new feature into Majordomo is to add it yourself
and then send me context diffs for possible inclusion with a future
release.
The rules are simple:
0) Start with the latest Majordomo release. If it's been a while since
the latest release, contact me; I might send you a copy of the current
working but unreleased code for you to modify, to ease integration.
1) Anything you add (other than bug fixes to existing code) should be
configurable.
2) If it is something site-wide (for instance, what mailer to use), it
should be controlled through variables in the .cf file, and should
default to the old, unmodified behavior if these variables aren't
specified.
3) If it is something list-specific (for instance, whether a given
list is open or closed), it should be controlled with a
"<list>.<flag>" file (such as the existing "<list>.closed" or
"<list>.passwd" files), again defaulting to the old, unmodified
behavior of the flag file doesn't exist.
Again, I appreciate your interest in Majordomo!
-Brent
--
Brent Chapman Great Circle Associates
Brent@GreatCircle.COM 1057 West Dana Street
+1 415 962 0841 Mountain View, CA 94041
|
|
