Message Boards

That's because it's SECRKT!

There is a repository (what project doesn't have one these days), you just gotta have two things:

1. Trust
2. Access

And no don't ask me, because I don't have either.

Could an index of files be given, with headers only, for those of us interested in the development, and compatability with other cocurrent projects.  I'm in early planning stages of a progressive bleading edge port, that doesn't plan to take the fast route OdaMex is taking, but a much slower route that will result in a code base usable for backports of features to all major GPL Doom versions.

Also, if you could post some of the resources you have been given for your project it may help other projects coordinate.  Remember, you are on the leading edge of development, and nice diplomacy will really help.

BTW I truely do understand the source issue, despite it being frustrating.

Could an index of files be given, with headers only, for those of us interested in the development, and compatability with other cocurrent projects. 

I don't see how this will help.  When the source is ready it will be available to everyone.  Given your rather ambitious project, it seems that you've got some work to do before it would even be necessary.  It doesn't seem to make much sense though, given that there's nothing purposely unique that make odamex special from other ports.  It uses the same CTF standard as the other two, it is boom compatible, all of which is available in boom/prboom.  There really is not much at this point that distinguishes an odamex-compatible wad from anything else.

Also, if you could post some of the resources you have been given for your project it may help other projects coordinate.  Remember, you are on the leading edge of development, and nice diplomacy will really help.

This request seems vague.  Chocolate doom, prboom and maybe even eternity studies and code extraction are the only "resources" we've utilized.  Odamex uses SDL for graphics, input, audio (_mixer).  The network code is heavily reworked from csdoom .62. 

The last bit of the previous quote almost sounds a bit threatening.  If you understand our situtation then you'll see why such a request is not possible or useful.

Good, now we can actually see the progress. Thanks.

Notice when bug 50 was posted.  It's been there for some time. :P

I will add however that the linked-to lists in the last comment for that bug are already out of date.  The list is much smaller than even the newest one on that page.

So, anywhere we can watch the progress? Any updates?

You can watch that bug, watch the changelog, and hang out in the IRC channel.