ACMQC - Open Source - Submit Code

Rules Governing Code Submittal

Please include your name, the name(s) of the author(s), the programming language used, and the target platform for the code, in the e-mail, so that the code will be put on this website in the appropriate section with your name and the name(s) of the author(s) credited.
No malicious or viral code is permitted. We enforce zero tolerance.
Nothing stolen. If code was borrowed, credit must be given to the original coder. If you did not modify the code, and you are not the original author, you should not submit the code.
Please document your code, provide a brief description, use proper indentation, and include lots of informative comments. vague comments = vague code
Use consistent indentation. If you use spaces, always use spaces. Don't mix spaces and tabs, since it doesn't look the same in different editors or on different machines.
It's recommended that you put multiple files in an archive file; tarballs (*.tar.gz) are preferred, but zips (*.zip) will be accepted. Make sure that the directory structure necessary for the files to work properly is preserved in the archive.
It's recommended that you indicate, in the code, what license the code is being released under. The GNU General Public License is preferred, but code governed by other open source licenses will be accepted.

If you agree to these regulations, click here to submit your code.

Rules Governing Project Submittal

Please include your name, the name of the project, the programming language used, the license under which it will be released, a brief description of the project, and the current status of the project. The different status ratings are Planning, Pre-Alpha, Alpha, Beta, and Maintenance. Planning status indicates that the project is still being conceptualized, and has no code. Pre-Alpha status indicates that the project has code but is not yet at Alpha status. Alpha status indicates that the project is still being designed and implemented, but has sufficient code to test the program with all or most of its basic features. Beta status indicates that the project is otherwise fully ready for the end-user, having finished implementing all of the functionality desired in the final program, but still requires, or is currently undergoing, extensive testing. Maintenance status indicates that the project is ready to be used by the world and contains no known bugs; extensive testing having been finished by this stage, only minor bug fixes will need to be made.

By the time a project reaches Pre-Alpha status, a Project Specification should be submitted. The Specification should contain details on the purpose of the program, why it is needed or desired, what the requirements of the final program are, and any information on similar programs which have already been developed; additional details on the design and implementation should also be included if possible. As the project is developed, the Specification will most likely require additions and/or modifications to keep it up to date with the changes in the project; if possible, to make our jobs easier, submit only the changes that need to be made rather than a completely new copy of the Specification. The "look-and-feel" of this site will be applied to the Specification and so submitting only the changes that need to be made significantly reduces the amount of work involved. If you insist on making our jobs more difficult, you'll just have to wait longer for your updates to appear on the site. Also, when writing the Specification, try to use clear and proper English; it makes it alot easier for others to understand.

If you agree to these regulations, click here to submit your project.