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)
- Dial-in Number: (712) 775-7035
- Participant Code: 479307#
- International numbers: Conference Call Information
- Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
- IRC:
- Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #fcrepo on irc.freenode.net
Attendees
Agenda
Discuss the current use and implementation of IdentifierConverters
- Consider the use of Akka for aync operations
- 4.5.1 Release Planning - when is code freeze?
Bugs are beginning to pile up
- Fedora Specification updates
- Messaging SPI
- Atomic Batch Operations - name? BatchOps? Bag-o'-Ops? OpSack? AtomicOp?
- CRUD
- Resource Versioning
- Binary Fixity Checking
- Authorization
- ...
Status of "in-flight" tickets
Ticket Summaries
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Minutes
- IdentifierConverters:
- The actual implementation, how we provide that service.
- Now it is based on a Guava concept, and what we want is not exactly what it is providing. We should get rid of that and implement exactly what we want.
- It will be a challenge because it is all throughout the code, and the longer it goes, the worse it gets
- The recent move to Java8 (iterators to streams), provides a lot of opportunity to cleanup and make the code base smaller
- What are the convertors? Just a mapping from one world to another world
- Example: Reference to fedora objects (info:fedora/ then the path)
- If you change the hostname, you don't need to change everything
- How to implement? Have an interface that has two function; to, and from
- Guava problem? Syntax vs Semantics -- it's not clear how the "sameness" gets represented
- How to move forward? A. Soroka will pull together some basic contracts, http implementation, and API class.
- Unknown User (acoburn) will open a ticket:
- It will be a large change!
- Akka:
- What is it? JVM implementation of the actor model; Highly concurrent, possibly distributed operations
- Other option is thread pools (sharing states and resources between threads is ugly)
- It's a big step, programming model is different and unfamiliar
- Where does it make sense? Things that are async, background jobs
fixity checking, modify an object (JMS events)
- Before we really kick the tires on Akka, we should identify a couple other use cases
- Should be easier to move forward on this than working on IdentifierConverters
- 4.5.1 Release planning
- Do we want merged, and in 4.5.1
- Squash and merge https://github.com/fcrepo4/fcrepo4/pull/1007
- - A. Soroka will take care of this before March 25, 2016
- When is code freeze? After we take care of the above; so March 25, 2016
- Feelings
- Specification updates
- Please read them all, and provide feedback!
- Messaging SPI
- Specifying data that comes out but not the format
- We should support all sorts of messaging protocols
- We don't specify a serialization
- We specify a serialization, or a mandatory serialization
- Use rdf - specify the semantics, not syntax
- fcrepo java client
- Unknown User (acoburn) says it is ready, and should be released!
- Nick Ruest and Unknown User (acoburn) will figure out how to release it next week
- Java8 Stream API
- How to become more familiar with it?
- There places in the code that need some refactoring, and could be a good place to get some experience
- Unknown User (acoburn) can point out some good places
- Unknown User (acoburn) and A. Soroka would be good resources to help
- rbacl is a good place to start (all the for loops!)
- fedora/modeshape impl (that could thrown into Akka too)
- How to become more familiar with it?
