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
- Declan Fleming
- A. Soroka
- Benjamin Armintor
Zhiwu Xie- Neil Jefferies
- Yinlin Chen
Agenda
- Clarify objectives of this group (reference: charter)
- Establish approach for addressing initial objectives
- Validate components and APIs
- Identify any questions or concerns about Fedora 4.0 architecture in the context of the project’s goals, objectives, and use cases
- Assess core vs. modular features
- Thought exercise: what would be the technical "risks" of releasing 4.0 Production *now*?
Minutes
Notes for Aug 14 Meeting:
Group - Help figure out if Fedora 4 (as developed) is meeting user requirements
Separate out REST API from remaining Fedora Implementation
Permits other implementations (different optimizations)
Clustered Multiple Node Case (Neil)
Performance
“Things are not working the way I like it to”
“Cannot meet a specific performance requirement”
“Can it support increased ingest performance”
Process for identifying the tasks. (Chris)
Review:
What are the aspects of the need to be reviewed:
API - REST, maybe core classes
Reviewing the architecture.
Performance (lay out scenarios cross by parts of architecture)
Use Cases (Scenarios)
Functional Requirements (features, capabilities)
Non-functional Requirements (ilities - like scalability, extensibility)
Functional Architecture
Technical Architecture (products and technology)
Implementation
Trace asynchronicity (against requirement a.k.a goals)
Trace preservation-related requirements and capabilities
- Modeshape metadata and ramifications
Read or Write more important
Note - People are at different levels
Modeshape
Object persistence
Asynchronous model for persisting (more well known)
Less so for asynchronous check that functions were performed (possibly not part of repository)
Two asynchronous processes in play
Summary Actions:
Bring next week expectations and goals (not just performance but all qualities/functions) that improved upon Fedora 3, or were supported by Fedora 3 and still need to be supported by Fedora 4.
