I apologize for stumbling over the legalize in the license: (MPL 1.1) http://www.aolserver.com/license/
Would someone sum up the legality of a party, not AOL, creating, distributing, and selling, a proprietary AOLserver module? I have been asked to help develop a piece of network glue, and gosh, it would appear to really benefit from being made from AOLserver, plus a variety of C or Tcl modules. I certainly want to support AOLserver. I would plan on contributing changes to AOLserver itself back to AOLserver, while encapsulating the new network glue in its own module. I don't know who the end client is, and so I don't know if they intend to sell the software, or just services based on their own internal application. I do know they would want to own the module that implements the core piece of their service, and I suspect they really don't want to own anything but that. It is conceivable they would be happy to link to or mirror the AOLserver distribution while selling the nsglue module. Is this behavior A) encouraged B) tolerated C) illegal D) ?? If A) or B) is there a guide to practical working with the MPL in spirit as well as in letter? Thank you, Jerry Asher ======================================================== Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161 Tel: (510) 549-2980 Berkeley, CA 94709 Fax: (877) 311-8688
