[MUD-Dev] openmud or pdmud or devmud

James Wilson jwilson at rochester.rr.com
Sun Oct 25 08:38:02 CET 1998


seems like the first thing people need to agree on is what name to use. ;) I
like OpenMud myself. PDMud sounds like there'll be a lot of sex there. DevMud
is kind of stodgy. There's always the Python option, i.e. go with something 
that just sounds good.

but maybe before that, it should be determined who is involved and what the
roles are. There's been a lot of design thrash lately, which can be good, 
but I recall numerous similar threads (not on this list) where people had lots
of grand ideas but no code ever got written. The Perfect is the enemy of the
Good, cf. the Hurd project. Anyways, I guess there are two things that I think
need to get resolved.

1. Who's in charge? Is it 'the consensus of mud-dev at kanga.nu'? Is it 'Bibi and
Bill and Yasser, but definitely NOT Muammar'? Is it 'Linus Torvalds alone'? I'd
like to believe that something good would happen without such a fascist
structure, but I'm a little bit cynical. Someone (maybe multiple someones) need
to decide on big things like What License To Use, and have their decisions
accepted. (I would imagine that different modules could be distributed under
different licenses. However, the core should probably be licensed as a unit.)

2. Who's going to do what? When? A number of fundamental design issues need to
be resolved fairly quickly if any further work is to be done. It's fun to argue 
about grand design schemes, but at the end of the day one has to make some
difficult choices and stick with them. Whatever design is arrived at needs to be
documented thoroughly so people know how to proceed. I don't want to be the
cause of needless bureaucracy, but we need to formalize things so everybody
understands one another.

I'm itching to implement something (as are, I think, many others who have
leapt up and shouted 'YES!'). I don't want it to fall apart in a month or two,
though, which is why I'm being so fussy and corporate.

James




More information about the mud-dev-archive mailing list