david wrote:
A big advantage of nmh's code stability is that it provides
a natural place to stop. Should we consider starting with a
clean slate? An extensible architecture and modern language
would make enhancements and maintenance much easier. And
safer, e.g., nmh still uses mktemp because replacement is
just too painful.
Of course, it won't be easy to reach consensus on what
should and should not be in it, what language, whether or
not to use middleware, etc. But going through that process
should give the gsoc student "more exposure to real-world
software development scenarios."
it would also pretty much guarantee the gsoc student about 10
summers worth of work. :-)
i know there have been a couple of fuse attempts at imap
integration -- i don't recall how far they've gotten. if it
weren't for possibly already having been done, i'd think that
would be an almost ideal summer-of-code project, since it would
be a somewhat stand-alone project, and something with pretty
well-understood requirements. and there wouldn't be a lot
of code archaeology needed to implement it, unlike some other
possible projects.
paul
=---------------------
paul fox, pgf(_at_)foxharp(_dot_)boston(_dot_)ma(_dot_)us (arlington, ma,
where it's 41.2 degrees)
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
http://lists.nongnu.org/mailman/listinfo/nmh-workers