>>>>> "CK" == Christopher Knight <email@example.com> writes:
CK> I was offering with open arms majordomo.com to be used to help in any
CK> way that it can to promote the forward momentum of the majordomo
Well, projects like this work with ideas as the fuel; you folks probably
have more experience than any of us developers in the running of 'large'
installations, with many lists and lists with many users. Generally when I
ask "now, what's best for large sites" on majordomo-workers, I don't get
much response so I have to make a few good guesses. Your site's input
would be great.
I guess all I'm asking for anyone to do is participate. Nobody has to hack
code, but often I just need more ideas than I can come up with. (And I
need someone to correct the dumb ideas that I do come up with.) Join
majordomo-workers. Fetch the current snapshot
(ftp.hpc.uh.edu:/pub/majordomo) and read the TASKS list. Read the TODO
list and tell me what isn't there, and which of the items that are there
are stupid. If you're brave, test the code. (Just don't expect to be able
to do anything real with it yet.)
CK> If shot down, I respectfully withdraw my offer.
I will never turn down genuine offers for help, as long as it doesn't
encumber the project in some legal way. But the TASKS file is the closest
I'm going to come to telling someone what to do. I'm just not very good at