Time/Place

• Time: 12:00pm Eastern Daylight Time US (UTC-4)
• Place: Google-hangout, https://plus.google.com/hangouts/_/event/c1glu6soq43r1rr6ou17qtobug8

Attendees

• Andrew Woods 
• Esme Cowles *
• Chris Beer *
• Daniel Davis * x2
• Declan Fleming
• A. Soroka
• Benjamin Armintor *
• Zhiwu Xie
• Neil Jefferies

Note-taker = 
Previous note-taker = *

Agenda

• Thought exercise: "What would be the technical "risks" of releasing 4.0 Production *now*"?
  • Or another way, "Where do we want to put next sprint's dev energy"?

1. Review of previous actions

2. Plan for wrapping up working group by end of Oct
3. Revisit discussion: "Preservation-worthiness"

Previous Actions

From 2014-08-20

• Neil to define initial set of system CI tests

From 2014-09-03

• Dan to create matrix of performance test payloads (probably here)

From 2014-09-10

• Esme to describe (and send to TWG list) position of F4 in the preservation stack/environment to seed next week's discussion

Discussion

• Chris
  • Give timeframe, may not need to assess all items
  • REST-API has seen movement due to its concrete objectives
• Esme
  • Performance testing and evaluation needs a lot of prep work
  • Could be helpful to use sprint to set up testing framework
  • In general, performance is not the greatest concern because the UCSD repository is ready-heavy
    • Read performance is supported by web-caching
• General question regarding how f4 scales with performance demands
• Zhiwu
  • clustering performance?
• Chris
  • We must change our change the wording of our areas of assessment requirements to "must"
• Esme
  • Each topic needs an owner
  • Need a plan for getting to Oct
• Dan
  • This group needs to bless the test scenarios