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 

• A. Soroka
• Jared Whiklo 
• Danny Bernstein 
• Esmé Cowles
• Marcus Barnes
• Michael Durbin
• Bethany Seeger
• David Wilcox
• Frank Smutniak
• Unknown User (acoburn)
• Jonathan Green
• Joe Harrington
• Andrew Woods
• Longshou Situ
• Aisha - Duke
• Benjamin Armintor
  
  

Agenda

1. 4.7.0 release candidate - testing and migration
   
   1. Backup/Restore issues
2. 4.6.1 release - patch for concurrent resource creation
3. Semantic versioning, API Specifications and releases post-4.7.0
4. new fcrepo-vocabulary repository?
5. API Specification - Taking it to the streets
6. Move Yinlin's tests into fcrepo4-labs

7. Status of "in-flight" tickets

Ticket Summaries

1. Please squash a bug!

2. Tickets resolved this week:

3. Tickets created this week:

Minutes

Status of release testing:

1. The process seems to be going well.
   1. ActiveFedora issue does not seem to be a blocker.  Ideally Drew can provide feedback before we turn the crank.
   • Danny Bernstein will rerun steps that seemed to be broken.
2. Release schedule: Halloween? Let's plan for early-ish on Monday after talking to Drew and Stephano.

• • Jared Whiklo is concerned that we haven't  the data migration enough - will touch base with Drew
  • Andrew Woods will circle up with Stefano and the gang about migration
  • Andrew Woods will check with Stefano that all is well with   Michael Durbin's 4.6.1 patch  before dropping the monkey.
    
    

Semantic versioning, API Specifications and releases post-4.7.0

The community wants semantic versioning.  

But the community wants no more than one major release per year,  minor releases as necessary.

There are two factors that require a major release:

1. breaking changes to the API
2. required backend data migration

Ideally we would finish the API work before the next major release (5.x). 

Should we strive for this?   Yes:  there is a consensus on the call.

Do we think that we'll need more near term releases with breaking changes at the REST API level before we get to 5.x? 

Is 6-8 months enough time to solidify the REST API and align the implementation with it? 

• A robust test suite should be part of that milestone.

new fcrepo-vocabulary repository

• reduces potential for misspellings
• uses RDF commons  - a level of abstraction above Jena.
• in labs right now
• should wait to merge into core until after the next version (0.3) of RDF commons comes out.
• increases reusability
• Unknown User (acoburn)  :  would like to keep the included ontologies to what is being used in the code.

API Specification - Taking it to the streets

A. Soroka has institutional support to move the process forward.  He is working to get the API (starting with the core) to the point where we can put it out to the wider community for feedback.

Perhaps we need a document that shows the delta between  the reference implementation and the API  today.  We could use this to track our progress towards 5.x.  Non-Adam's could help on this.

Aisha: Maybe consider looking at https://apiblueprint.org/..

Move Yinlin's tests into fcrepo4-labs

• Andrew Woods will move those in.

Moving FCREPO-2105 forward

• Unknown User (acoburn)  will work on wrapping Guava-based converter implementations with new Java 8 functions
• Danny Bernstein will then  revisit each converter in order to  factor out Guava and implement performance related improvements where applicable.