&fmldevel; already implemented fundamental functions except for editing configuration files. Several people uses &fmldevel; as hobby and office mailing list system for a test. &fml8; is intended to re-implement almost all &fml4; functions but not yet enough. So, if you are interested in the use of special features, please use &fml4; stable series. See http://www.fml.org/software/fml-devel/fml/doc/ja/todo/STATUS.html for the current status of &fmldevel;. &fmldevel; is fully rewritten mailing list driver from scratch to re-implement &fml4;. The main purpose of this project is re-implementation of fml mailing list driver system with reflecting my 10 years experience on mailing list driver developement. Roughly speaking, the relation between &fml4; and &fmldevel; is similar to one between sendmail and postfix. &fmldevel; re-implements features of &fml4; functions. We redesign fml and clean up the function and variable naming convenstion. Also, We reinforce guide line to the coding style for clean source codes. For example, when you use &fml4;, you'll find that fml assumes the list of members is found in the text file on the host. &fml4; inherits the assumption from version 1.0 through 4.0. It affetcts the core part of designs. Hence, it is difficult to extend fml IO for the use of RDBMS, redundency et.al. In fact, &fml4; supports RDBMS but the code is ugly. We should need to fully rewrite fml core parts. Also, I want a lot of new features. &fmldevel; should provide tiny bug tracking system maintatined automatically. It is better to co-relate fml with cvs log. These features help the support by mail and developer mailing list. I need it, of course. Firstly, we need to discuss what we should inherit from &fml4; design and features, and discard what in &fml4;. What we should inherit into &fmldevel; from &fml4; ? easily customizable ? remove obsolete features. Anyway, we should write codes for the further discussion! You can find it at the following URL. http://www.fml.org/software/fml-devel/ ftp://ftp.fml.org/pub/fml-devel/ We implement new features at &fml8; branch. &fml4; imports it if needed. We only have to bug-fix at &fml4; branch. (further translation omited). fml-devel -----------------------------> 8.0 A | | | (interaction) | V 1.2 -> 4.0 ------------------------------> 4.0-current | | 4.0.1 4.0.2 .... (release / 4.0-stable release) fml-users@ffs.fml.org is prepared. Use it for English discussion. To subscribe it, send the mail with "subscribe YOUR NAME" in the body to fml-users-ctl@ffs.fml.org. You will receive the reply for confirmation. Please reply the confirmation and send back it to fml-users-ctl@ffs.fml.org again. For example, a subscribe mail is as follows: From: your-account@your-domain To: fml-users-ctl@ffs.fml.org subscribe Kinomoto Sakura Please send me the idea on &fmldevel; to the mail address: fml-request@fml.org or myself fukachan@fml.org directly. For the &fml4; user, the order of chapters and sections are almost same as the book "fml bible" publishded by O'reilly Japan (rewritten in Japanese). §.terms;