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 
• Nick Ruest 
• Bethany Seeger 
• Longshou Situ 
• Unknown User (acoburn)
• Yinlin Chen
• Esmé Cowles
• Michael Durbin
• Kevin Ford
• Peter Eichman
  
• Bill Branan
• David Wilcox
• Katherine Lynch
• Michael Gibney
• Andy Wagner
• Andrew Woods

Agenda

1. ModeShape5 update

   1.  Need assistance enabling PostgreSQL in Modeshape5 branch (MySQL works)

   2.  Need assistance testing/enabling clustering, which is available with Modeshape5
      1. A.Woods - clustering in AWS with objects and binaries in MySQL works
   3.  Previously identified issue with ModeShape5 and Federation not picking up new files is resolved
   4. Ready for community testing – focus on piloting migration via /fcr:backup and /fcr:restore
   5. Production Fedora release of ModeShape5 is pending ModeShape release 5.1.0 to include bugfix – although testing can start now!
2. An RdfSource that is not a NonRdfSourceDescription currently describes itself. Should that be reflected in the Java API?
3. Open Repositories Tech Meeting agenda planning
4. Message serialization format (see proposal)
5. Filesystem Federation Use Case & deprecation from core
   1. UPenn Use Case and additional info
6. Multi-tenancy - needs from Hydra-in-a-box
7. Migrating and Round-tripping content... tooling needed
8. Use of Maven BOMs in the fcrepo4 codebase... embrace or abort? And generally, how are dependencies managed?
9. Commons RDF in fcrepo-kernel-api
   
10. Logging recommendations and style-guide
11. ...
12. Status of "in-flight" tickets
13. 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