|
1. Many users have access to the OSCAR account. Each member should actively minimize the activity within the OSCAR account, and document any activity. New members of the group should discuss all potential changes with the chief scientist, team leader, or project leader. 2. If you are going to change OSCAR files, do not change any current interfaces without approval from the Chief Scientist. 3. If you are adding new files to OSCAR, develop these within your own account and add them only after they have been thoroughly tested. 4. If you are developing new applications with OSCAR, develop these using a personal account and add to the file OSCAR/Applications only if they are thoroughly tested, demonstration ready, or clear enough for all to use. Titles and comments must make it clear what the application demonstrates. 5. Use the traditional headers, and naming scheme. All OSCAR objects should start with ‘RR’ to avoid name space pollution. Comment new code in a clear and succinct manner. Document origins of applied algorithms if necessary. Object Outline follows a clear rules for parsing comments into online documentation. Make sure these rules are followed. 6. New code should compile on all currently supported platforms. |