mudpy

The previous BSD-like mudpy license has been replaced with the one used by the OpenBSD project. It’s modeled after the Internet Software Consortium’s, a two-clause BSD license removing language made unnecessary by the Berne convention. This new license is functionally identical to the old one, just more terse and openly recognized.

While I was at it, I made sure to correct the copyright dates on some of the files in the current release and add a copyright statement to any files previously lacking one.

In the interest of development process transparency (and also as a list of patch requests for anyone interested in pitching in), the mudpy to do list has been added to this site. In it you’ll find a (hopefully) up-to-date, if rather disorganized, list of things that need to be tackled in both the source code and sample data.

A section for configuration documentation has been added to the site, detailing the common settings to be tweaked under the new data model (note, this will not be usable with the code in the current snapshot, but is helping me to flesh out the changes required). More to come…

The revised data model for mudpy has finally been sketched out, and I think this will be much more flexible than the previous model. Documentation for it is being maintained here, and while not really a formal specification, it at least aims to be comprehensive in its coverage of data storage both external to and cached within the mudpy engine.

To help facilitate productive discussion of mudpy concepts, a glossary has been created. Within, you will find definitions for common terms used to describe composition and operation of the mudpy engine, data, and the virtual worlds it maintains.