We are open to your contributions! If you have an idea, a new piece of documentation, or a patch, we want to hear about it! Below you'll find an overview of the people involved and advice on how you can contribute.
Here are a couple of guidelines that we think will benefit not only your OpenACS project but the OpenACS community at large:
You might look into better version control systems to ensure that your local customizations are preserved (for example, see using OpenACS with Gnu Arch)
Please check the discussion forums (use the search) and see if your idea has been discussed before. Feel free to contribute any additional information. Bugs and feature requests should be submitted to the OpenACS Bug Tracker.
If you want your idea to be adopted, it is up to you to get support for it! The OpenACS community tends to rally fairly quickly around popular/useful ideas, so this shouldn't be too difficult.
If you want to submit code you are encouraged to checkout the sources from CVS and keep them up-to-date. Patches can be submitted in the OpenACS Bug Tracker. If you need cvs commit rights you should contact the OpenACS Core Team. Once you have commit rights you should read our CVS guidelines and instructions. You should also check the projects page to see which projects are already underway that you can join.
If you want to help with documentation, either by informing us of a mistake, or adding documentation for areas that don't currently exist, see the FAQ entry on helping out with documentation, or contact Rocael Hernández with your input.
You can mention OpenACS in any way you want. If you'd like to be more "officially" associated with the OpenACS project when you speak (at a conference, at a university group, etc...), please email any one of the gatekeepers and explain what you want to talk about, what your role in the OpenACS community has been to date (in case that isn't clear already), etc...