Agenda and notes from the 8/22 meeting

o    Need to be more open and transparent about the process the Intel team is following - don't surprise the community.

o    Need to be more open (within the Security team) about the work items coming out of the Intel security review

o    Static analysis results and how to handle?

o    Banned C function usage and how to handle?

o    Intel has internal milestones for this work.

o    Ken to set a Security team call.  Action needed to set the priority of the Security work in the community. 

o    Ildiko can help with setting calls.  Please reach out to her.

o    Follow up to the Security discussion - would like to see defects coming out of large efforts e.g. static analysis shouldn't be tracked on a bug by bug basis but as part of larged stories - don't want to see one bug per static analysis issue for instance.  For example, we should define one story for static analysis issues for stx-fault and let the team decide how/if to break that work up into tasks.

o    Can use the Importance field in LP to assign priorities to bugs.  Should agree on how to set priorities.

o    weekly meetings for sub-teams - schedule on wiki with Ildiko

o    Sub-teams should define priorities for the teams and tag stories for the right release.

o    In OpenStack the teams determine release content and the Release team handles process and mechanics.  In StarlingX we've been leaning toward the Release team determining content.  We should probably start leaning more toward a collaborative model.

o    Release team can put a proposal together for review