UOX3.org

Actually, It is difficult to know what features the developpers really wants to make. So it is a problem for contributors.

Many people would like to help developpers for UOX3. So, they can not know what to do, because developpers do not tell what they want.

Sometime, it is difficult to know what is a feature, what is a bug, where is the bug, what developpers really wants at end.

What should UOX3 be? An OSI clone? A custom server? How this skill should work? Why they do not make this feature? It is not implemented yet or it will be it never?

There is only one reason to these problems: the developers do not have clearly draws up a list of things to be made.

There is only one solution: to write a TODO list.

In a TODO list, developpers and contributors write:
- Base idea of the software (global rules)
- Features implemented.
- Features wanted.
- Features in development.
- Know bugs to fix.
- Know bugs in fixing.
With a priority level for what is important (mainly bug fixing), what is not, what is easy or difficult to do...

So contributors would have a clear list of missing features to code, what to expect and if they like the project.

http://sourceforge.net/docman/?group_id=113893

Perhaps not entirely what you are requesting, but about as close as it gets, currently.

Aside from that, I'd rather spend the limited time I have fixing things than writing about things I'd like to do in the future (and may or may not ever do). That being the case, if someone wants to know what to do, all they need do is ask, otherwise they can suggest what they'd like to do, and I can give input on where I see that in relation to the larger UOX3 scheme.

Contributions of any kind are more than welcome, however. And even those that may not be pre-packaged in the "official" release would certainly still have a presence in other ways (IE Xuri's cache of custom JS Scripts).

I think I can do 'Cross-platform / compiler support' and 'Const Correctness throughout the code'. How do I contribute the code? I also would do unit test to squash some bugs.

Will you consider monotone? Never use it myself, but distributed version control system is much easier and efficient to share and merge work than centralized cvs, No more diff. Monotone is one of very few which support windows platform.

Right now you could send your code to either myself or giwo for inclusion on the cvs - but giwo could probably cook up some cvs write access for you if the need is great =)