To make contributions to the omniORB source, you should subscribe to the omniORB-dev mailing list, and post your patches there. See http://omniorb.sourceforge.net/list.html . DO NOT submit patches to the SourceForge patch manager. Nobody reads it!
Your contribution is much more likely to find its way into the omniORB distribution if you follow these simple procedures.
Post to omniORB-dev to say you intend to work on a feature before you start working on it. That way, you don't risk duplicating someone else's work, and we can all see how what you propose fits in with the rest of the plans.
Make sure your code follows the CodingConventions.
- If possible, try to test on more than one platform, at least Windows and one Unix.
If you change core ORB functions, test against the complete omniORB and ORBacus test suites, available from http://cost.omg.org/
- Post patches against the latest CVS contents on the branch you are working on, not the most recent full release.
- Post patches in unified or context diff format.
If you are given write access to the CVS repository, you MUST NOT commit changes to the main omniORB / omniORBpy modules without prior consent from the module maintainer (Duncan Grisby).