Jerry Peek <[EMAIL PROTECTED]> writes: > For the long term: I've never written architecture documentation > before. How difficult would it be to write one and add to it as time > goes on? Would a wiki or some sort of collaborative online setup let > us all rough out the outlines of good specs? I don't know.
Josh Bressers <[EMAIL PROTECTED]> writes: > If there is interest, I think it would be worth starting a cleanup branch > in CVS, or an nmh-cleanup sub project (possibly not hosted on savannah). While these are well-intentioned, my fear is that people do not have the time to commit to these sorts of things. We might get a nice architecture, but then run out of steam on the implementation. We might get a really nice cleaned-up branch, but then run out of steam leaving the branch orphaned. I think the most pragmatic approach is to work on the trunk in small bits checking your work with unit tests as I said before. Then if people run out of steam, at least we have some working code. -- Bill Wohler <[EMAIL PROTECTED]> http://www.newt.com/wohler/ GnuPG ID:610BD9AD Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian! If you're passed on the right, you're in the wrong lane. _______________________________________________ Nmh-workers mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/nmh-workers
