Just out of curiosity... why have so few people forked RunUO?
Maybe the view point of Ryan and his dev team is simply that it's stable and does what is expected. That could be a valid argument and one that I could respect. But the beauty of GPL(2?) is that, if that's the stance that RunUO is taking, and we disagree with it, we are fully empowered to create our own solution forked from RunUO code and distribute it as an entirely different, and arguably "better" project.
Over the years there have been a few mildly popular RunUO derivatives, but none, that I'm aware of (and I admit I've been out of the loop), that really just aimed to
improve the RunUO codebase; not fundamentally change it. If an OSS project won't accept our patches, and we truly believe them for the better good,
fork it. There's nothing wrong in doing that. That's what OSS is all about... enabling advancement by enabling competition.
I say, if there's a need, fix the RunUO project structure. Better separation of concerns and pluggability (dare I say IoC?). Set up a proper VS2010+ solution for debugging by default. Slap up a github project/page, lay out a project plan, and start upgrading things. Ideally, both projects should benefit.
Side Note: I do say github for a reason... it's about to get some serious Windows/Visual Studio love this year, now that they've hired Phil Haack (see:
http://haacked.com/) and it's super-fabulous for collaboration.