To get your code checked into OpenCA.org's CVS repository you'll need to understand our code development cycle, coding practices, and checkin requirements. You probably also want to have a reasonable understanding about the project's organization.

At the moment there are no written rules about conding techniques and requirements, we will provide those as soon as possible to help developers to contribute to each projects. However single projects can decide different coding rules as required by the project nature.

Getting involved in a project on OpenCA.org is as easy as subscribing the support mailing list(s). Starting from there you will be part of the community and you can submit your ideas and code there.

Remember, however, that patches and enhancements should be discussed among all the people participating to the project, therefore describe your ideas before writing many lines of code that might be rejected by the core team of the project.