Outline a process to review, improve, endorse, and implement SECOORA DM changes

This is a first cut / strawman - additions to this page? Login and make improvements or email Jesse Cleary for editing access.

Objectives

• Get new code and software tested, improved, endorsed and into production
• Small group for each specific review, but larger tacit review
• Help balance/distribute dev efforts around the organization
• Keep hub activities more tightly sync'd
• Contribute to general awareness of all SECOORA dev efforts
• Distribute technical knowledge via peer exchange
• Get development work into an internally visible location (trac/SVN) to pub DMCC efforts within SECOORA
• General
  • light and quick
  • public, build consensus
  • supportive/positive
  • time requirement for individuals participating in the DMCC

Process Outline

1. New code is developed / software is considered
   • document and publicize pieces while underway
2. DMCC is notified when a review is desired by the author(s)
   • might just be a stumbling block and not a full version review?
   • Needs companion documentation - simple wiki page + code in SVN
3. Reviewer(s) are volunteered
   • Pending expertise and availability
   • Reviewer role is part of SECOORA participation
4. Reviewer(s) has some time period to review
   • I think this should be short (1-2 weeks?)
5. Reviewer(s) develop a short written response
   • highlight issues and concerns
   • publicize to DMCC
6. Review call to discuss with author
   • develop action items to improve
   • publicize to DMCC
7. Author works on improvements
   • Ready after decisions/actions on improvements list?
8. Out to DMCC to endorse
   • author(s) and reviewer(s) informally discuss with DMCC
   • non-reviewer DMCC comments heard
9. DMCC discusses how to implement