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 

• Jared Whiklo 
• Bethany Seeger 
• Longshou Situ 
• Unknown User (acoburn) 
• Yinlin Chen 
• Esmé Cowles
• Michael Durbin
• Kevin Ford
• Bill Branan
• David Wilcox
• Katherine Lynch
• Michael Gibney
• Andy Wagner
• Andrew Woods
• Doron Shalvi

Agenda

1. Filesystem Federation Use Case & deprecation from core
   1. UPenn Use Case and additional info
2. Multi-tenancy - needs from Hydra-in-a-box
3. Fedora 4.6.0 immediately after Open Repositories?
   1. Support influx of Sufia7 users' use of JDBC over LevelDB ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. )

4. ModeShape5 towards "master" branch

   1. How do we want to move the community onto ModeShape5?

   2. Immediate need for robust migration tooling ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. )

   3. Production Fedora release of ModeShape5 is pending ModeShape release 5.1.0 to include bugfix – although testing can start now!
5. Open Repositories Tech Meeting agenda planning
   1. Preparation for All: review API Specifications
6. Use of Maven BOMs in the fcrepo4 codebase... embrace or abort? And generally, how are dependencies managed?
7. Commons RDF in fcrepo-kernel-api
   
8. Logging recommendations and style-guide
9. ...
10. Status of "in-flight" tickets
11. Click here to expand...

    key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Ticket Summaries

1. Please squash a bug!

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

2. Tickets resolved this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

3. Tickets created this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Minutes