Subject: [sacm] Proposed Timeline for the SACM Hackathon Team

From: "Waltermire, David A. (Fed)" <[email-masked]>
Date: Tue, 25 Apr 2017 17:09:49 +0000

Adam and I met on Friday to discuss a schedule for the SACM Hackathon team. The following are the milestones we came up with. Any bashing of the overall schedule?

April 28, 2017 - Identify goals based on the Vulnerability Assessment Scenario. The working group will identify a set of achievable goals and stretch goals that will establish priorities for what we build during the Hackathon.  These goals will be based on the vulnerability assessment scenario. [1]

May 5, 2017 - Identify existing code modules for SACM components; identify gaps that need to be implemented. The working group will identify existing software that can be used to assemble SACM components and any gaps that need to be filled. [2]

May 19, 2017 - Identify providers of existing code modules, and developers of new code modules. The working group will identify volunteers to provide existing code modules and developers to work on new modules, enhancements to existing modules, and any glue code that is need to form a solution.

Week of May 29, 2017 - Host a conference call to Plan deployment. The working group will figure out what the operational environment will look like to use for integration testing during the Hackathon. Specific individuals will be identified for deploying and configuring specific code modules.

June 30, 2017 - Complete development of code modules identified for enhancement, to fill gaps, or as glue code.

Week of June 26, 2017 - Host a full day conference call to facilitate integration of components and to identify interoperability defects, and other functional issues. The participants will conduct an integration and interoperability exercise to test the deployment. Any issues will be identified to be addressed before the Hackathon. This dry run will help to identify potential problems that can be addressed prior to Prague.

July 14, 2017 - Complete updates to address issues prior to Hackathon.

July, 15 and 16, 2017 - Hackathon - Conduct  integration and interoperability testing of code modules. Resolve any defects that come up.

[1] https://trac.ietf.org/trac/sacm/wiki/SacmVulnerabilityAssessmentScenario
[2] https://mailarchive.ietf.org/arch/msg/sacm/w_kL2vzDBPk0NN9N1WQcpb3Qwfw

Regards,
David Waltermire