Time/Place

Attendees

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

Note-taker = (star)
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

    1. Assessment plans have been moved from the email list to the wiki
  2. ...

Previous Actions

From 2014-08-20

  • Neil to define initial set of system CI tests

From 2014-09-03

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

From 2014-09-17

  • (tick) Dan to define area of assessment and establish plan for end of October resolution - Performance
  • (tick) Esme/Declan to define area of assessment and establish plan for end of October resolution - Preservation-worthiness
  • (tick) Zhiwu to define area of assessment and establish plan for end of October resolution - Clustering
  • Ben to define area of assessment and establish plan for end of October resolution - REST-API

Discussion

Assessment Plans

Performance

  • Looking for more feedback
  • Divided performance activities into categories
    • Grounded in real-world uses
  • Need to factor out generalized tests
    • Example, many of the use cases do not have quantified details
  • Need help with:
    • Mapping use cases into canonical operations
  • Concern that the permutations may be hard to scope into the timeframe
  • Need to define the nature of concurrency testing
  • Add: bulk reindexing, bulk metadata retrieval
  • Need to mention that bulk export is covered in the preservation area
  • Could be useful to have federation in the performance testing mix
  • Re-emphasize: goal to get results by end of October

Preservation worthiness

  • Defined 5 ways of exporting content
  • Need to make a statement regarding where Fedora sits in the preservation stack
  • Fixity
    • Compare federation fixity versus modeshap-native fixity
    • Checkbox: could the user write a fixity checking app? - yes
    • Checkbox: ensure that a corrupted binary is detected? - yes

 

Actions

 

  • Plan owners: to move the plans into implementation