Time/Place
This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
- International toll free: http://www.readytalk.com/intl
- Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial-in number
- Once on the call, enter participant code 2257295
- IRC:
- Join the #duraspace-ff chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #duraspace-ff on irc.freenode.net
Attendees
Agenda
- Release status: 3.8.0
- Java client API
- LDP library?
- Proposed client interaction model?
- Unit testing and mocking?
- Connection client configuration?
- Top priorities in view of releasing 4.0
- Acceptance testing feedback
- Load testing approach
- ...
Minutes
- some concern about none of the java LDP libraries being suitable
- Andrew Woods suggested we should build such that we can later include LDP library
Fedora 3.8.0
- Scott Prater created a test plan (copied 3.7.2 test plan)
- wants to know if it's really 3.8.0? (yes)
- what issues should we link to in the test plan for testing? (could Benjamin Armintor link issues to test plan)
- Scott Prater, Michael Durbin will continue code review. Can Benjamin Armintor schedule time? (yes, though he's busy)
- Andrew Woods noted that this may be the best opportunity to get fedora 3 stuff done given the availability of Fedora 3 veterans.
Fedora 4 Java Client Library
- Andrew Woods has concerns about FedoraRepository class growing without bounds in the future, could this be broken up
- Unknown User (escowles@ucsd.edu) suggested some could be moved out, and other new features would hang off of other classes (locking and versioning would be on objects).
- Andrew Woods is looking towards how easy it would be to mock out responses in unit tests using well-established and recommended objects.
- Unknown User (escowles@ucsd.edu) thought to use the same model as the indexer, where second constructors exist where you pass in an HttpClient and you could provide a mock or custom client in special cases.
- Andrew Woods suggested that we might want something to encapsualte the HttpClient... is it the FedoraRepository or some other object (perhaps which would be replaced by an LDP client).
- Andrew Woods praised the parameter providing methods in fedora 3's client, polled audience about people's experiences.
- Michael Durbin liked the approach
- Scott Prater started using it recently and was happy
- Unknown User (escowles@ucsd.edu) will look into the Fedora 3 client model and see if he can apply it locally.