LCA Software Development Needs
- Jake: versioning (software & web content, etc.)
- Stephen: Central repository of analysis codes/scripts, etc. Constantly hunting around. Not necessarily public. Better documentation.
- Alexei: Preservation via version control.
- El Houndogo: Verioning and code centralization is key, us and "external" developers (LCA Alum). Documentation (expletive). Therefore, we need to write some docs. Maybe we should talk about bugs at meetings.
- Los Drunken Boys: Keggeratorttt.
- James: Version control: $ENZO_ROOT/amr_src/version.def, $ENZO_ROOT/VERSION (same file). Start using this wiki, share crazy finds. Coding guidelines, standards. Repository for tools/scripts.
- Dan: Subversion help guides, especially for merging. Easy way to adding documentation, especially for new functionality. Version control over test files/input files. Help with Robert's I/O (maybe some documentation).
- Rick: Version control policy, absolute web power. Divide up the responsibility.
- John: Automated emails of commits (can we do for branches?). Codes area looks crowded.
Download in other formats:
