On Wed, Oct 29, 2003 at 07:26:29AM -0500, ke...@bt... wrote:
> Now that I know I'm not alone here, I figure I'd ask a question that
> some of us are no doubt wondering. It was recently announced that Kip
> would be taking the reigns of 3065 as Head Wizard and performing some
> code merging between the two codebases. I'm curious to know what kind
> of improvements this will bring over the base 3030 dist. Along with
> that, when are we likely to start seeing these changes in?
> I'm a bit curious about this (as I'm sure others are too) and from
> what I've seen, 3065 had some very stable, cleanly running code (from
> the player side of things). It's good to see some swapping around
> going on, now if you could get Deej to do that... :)
Well, I'm not sure howmuch of the actual code will make it into the OS tree.
It may look clean from the player perspective, but this is more to do with
the surrounding supporting softcode than the actual hardcode. But the idea
is to replace the 3065 binary with one compiled from the opensource tree,
with some different configuration settings, and have it change very little
for the people playing 3065.
I've made a large diff between 3065 source and the MUX source it was based
on (more or less) and am currently working that through to find the actual
changes that need incorporating. It'll take me a while to finish it, but
it'll be merged eventually.
As for 3029, well, you have more influence there than me. Fingon already
agreed to a re-release of the original MUX source under the 3030MUX license,
provided he doesn't have to do anything, so the 'big reason' why 3029's
source is closed would be removed, but it's not a high priority to me. I
plan on adding some of the cool features from 3029 into the OS tree in a
different manner, and I don't at all like how AT2 is implemented there, so I
don't care much for 3029's source at the moment :)
--
Thomas Wouters <th...@xs...>
Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
|
