Hmmm, why don't we treat this as a software project and:
1) Do requirements gathering
a) ask our customers (users) what they need
b) ask parters what they need (mh-e, exmh)
2) Come up with work estimates
3) Figure out when we want to release
4) Schedule what will fit
a) review it with customers and partners
b) refine it
5) Do the work
6) Document it
7) Test
8) Release
9) Lather, rinse, repeat
Or has getting paid to do software damaged my mind?
Thanks.
Jeff
--
Jeffrey C. Honig <[EMAIL PROTECTED]>
http://www.honig.net/jch
GnuPG ID:14E29E13 <http://www.honig.net/jch/key.shtml>
_______________________________________________
Nmh-workers mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/nmh-workers
