Contributed patches are essential to the success of OpenDX. We don't have access to all platforms, and we certainly aren't using OpenDX in all the different ways it can be used. We try to make it as easy as possible to contribute code. However, to help us manage the process, please observe the following guidelines.
Please create the patch using the following command
diff -C3 file-old.c file.c
where file.c is the file affected. We should be able to
feed the patch directly into the "patch" program and have it update
the file or set of files. The -C3 is very important,
line numbers can change on a daily basis in some code files, so having
context is crucial to knowing where it all really goes.
Please post patches to the opendx-general mailing list, with the string "[PATCH]" prefixing your subject line. Or if you prefer e-mail the patch directly to gabra@us.ibm.com.
We are sure there's plenty of just plain dumb mistakes in the code. These, along with portability fixes, are the most timely and will receive our highest priority.
Be aware that Greg, although flexible by nature, tends to be a bit conservative about what makes it into the core of OpenDX. OpenDX has a variety of flexible APIs, and any advanced functionality is a likely candidate for a user-contributed module. Also, it is possible that the functionality you wish already exists either in another portion of OpenDX or in an existing user-contributed module. We suggest you raise the issue on the mailing list before you start adding function or re-architecting the core.