&fml8; project called as fml-devel also is refactoring of &fml4; mailing list driver. See http://www.fml.org/software/fml8/ for more details on the furure plan, design and implementation of fml-current. simple implementation of configuration files and menu. perl module (> perl 5.00504 ) support more integrated CUI (makefml) and GUI. Separation easy upgrade use CPAN modules as could as possible. 3rd party directory abstracted IO layer file (implemented) /etc/group (implemented) NIS (implemented) SQL (MySQL implemetned) LDAP IPv4/IPv6 ready (implemented) status entry detail done. license perl conformance underway. image &fml4; to &fml8; is similar to sendmail to postfix. support configuration converter. done. wrapper (separation layer). separation layer for upgrade/downgrade, debug. adapter use CPAN modules as could as possible. prepare adapter layer in using CPAM module. new single configuration file format. rule of variable naming convension use_XXX, XXX_TYPet ... prohibit NOT_USE style. function name convension use X11 style for main:: space. use method style for method. not use Lisp like style (-p). use Perl Cookbook style ? e.g. "MemberP() -> IsMember()" done. queue manager re-delivery by itself tools not use BSD make. Not be an architect nor developer. Not too abstractive and not too object oriented. Be between them. Feedback in one month to manage project and code review. days in one month content the first 4 - 5 days manage project. apply at least 20 % of the project to this stage. 2 - 3 weeks coding. the last week code review, document review at the last of the month release a snapshot. alpha-0, alpha-1, alpha-2, ...