All you have to do to join the OJP is to contribute in some way to its development. To submit material to the project, follow the instructions below. If you want to contribute in a different way (i.e.: keeping the readme up to date, etc), please e-mail one of the people on the Contact List.

We are looking mostly for new code features, but are not limited to that. We are usually looking for generic, flexible, and adaptable features that anyone can work into their own code. Features that are drastically unique or special probably do not belong here, because we believe in keeping individuality and uniqueness among mods.

We also accept patches. If you see something in our code that has a problem, you can submit a patch for it. A patch would usually be replacement code or files.

However, we are not looking for maps or player models (although we might be able to use some very skilled modeler help) at the moment.

Before you consider submitting, take note that we won't let you desubmit or remove your works from the project. Allowing people to do so would cause too many problems for the project. While your work will remain your work, submitting stuff to OJP means that you give us the rights to use your work as part of the project forever.

In addition, your work won't necessarily be turned on or even in every compiled version of OJP. Some features will be disabled by default to allow people to just fire up and play OJP without confusion.

That being said, if you have something to submit, just contact one of the OJP moderators or administrators.

DO NOT E-MAIL STAFF MEMBERS WITH FEATURES WITHOUT ASKING FIRST! Just contact one of us, tell us a summary of your patch or feature, and if we think it fits the project, we'll accept it.

If you think you would like to actively participate in developing OJP, we can give you write access to the CVS repository, so that you may work on it yourself. This doesn't have to be a commitment, but if you would like to just submit features or patches separately, go ahead.

Submission Material Guidelines:

• Document your work as much as possible. Be sure to add mentions of your work to the readme and other project documents.
• Make your work as clean and tight as possible.
• Follow the coding guidelines. Try to keep your code as separated from other code as is reasonable. Label every coding change that is separate from base JA with appropriate coding tags. If you're creating a new feature, you'll get to determine what the tag name will be. Try to pick something that is simple and easy to search for.
• NEVER DELETE FILES OR DIRECTORIES FROM THE CVS REPOSITORY! If it is necessary, the moderators will handle it, just contact them.