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 

• Benjamin Armintor
• Jared Whiklo 
• Longshou Situ 
• Esmé Cowles
• Andrew Woods
• Nick Ruest 
• A. Soroka 
• Mark Jordan
• Unknown User (acoburn)
• Bethany Seeger
• Yinlin Chen
• David Wilcox

Agenda

1. Use of Maven BOMs in the fcrepo4 codebase... embrace or abort? And generally, how are dependencies managed?
2. Commons RDF in fcrepo-kernel-api
3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
4. Deprecate fcrepo-transform in favor of a Camel-based solution?
5. Fedora 4.6.0 release plan?
   

   1. Based on ModeShape4 - although Esmé Cowles has some successful, preliminary backup/restore results

   2. DelegateHeaderPrincipalProvider - Benjamin Armintor approach updates?  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

   3. Support WebAC alignment with Hydra community - has this been verified?

   4. Extracting File System Connector - Blocker?  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

6. Move fcrepo-event-ontology into fcrepo4/ontology?
7. Source code license header - Done, pending new release of fcrepo-build-tools
8. Import/export of Bags
9. Ready for Performance/Scale summary page/message
10. ...

11. Status of "in-flight" tickets

    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