%myvars; ]> by Joel Aufrecht Get commit access to the repository. Core developers already have this. We should have a process where anybody can register a package name and (possibly after a delay or security audit) get commit rights to a subdir of the same name. Make sure your package is ready to contribute. myfirstpackage.info should have all the basic tags auto-generated by the APM, plus vendor and maturity. Maturity should be: <maturity> <platform id="openacs-core" version="5.0"> <level descr="New Submission">0</level> </platform> </maturity> with the appropriate core version number. has automated tests - at a minimum, every API function should be covered by a smoke test. Has documentation. An install guide, if there are any special installation requirements (such as additional software); a user guide; an administrator guide. Get a clean copy of your package - no ~ files or .# files or CVS files. Assuming you have been developing in a local cvs repository and your local version 1.0.0 is the one you want to contribute, the easy way to do this is: cd /tmp cvs -d /cvsroot openacs-4/packages/myfirstpackage export -r 1-0-0 Import it to the openacs.org cvs tree cd openacs-4/packages/myfirstpackage cvs -d :pserver:you@openacs.org:/cvsroot import -m "initial upload" openacs-4/contrib/packages/myfirstpackage your_vendor_tag myfirstpackage-1-0-0 Tag the imported package for compatibility with core: cvs tag openacs-5-0-compat Wait for someone to set up nightly rebuild of the Automatic Repository Generator, less than 24 hours after which point your package will be put in the OpenACS.org repository and become available to everybody via "Install from Repository"