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 

• Unknown User (acoburn)
• Bethany Seeger
• Nick Ruest
• Yinlin Chen
• Esmé Cowles
• Andrew Woods
• James R. Griffin III
• Jared Whiklo
• Andy Wagner
• A. Soroka
  
  

Agenda

1. Updates from the last two weeks?

2. Tickets aligned with roadmap themes

   1. API Specification 

      Click here to expand...

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

   2. Service: CRUD 

      Click here to expand...

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

   3. Service: Versioning 

      Click here to expand...

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

   4. Service: Transactions 

      Click here to expand...

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

   5. Service: Fixity 

      Click here to expand...

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

   6. Service: Authorization 

      Click here to expand...

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

   7. SPI Specification 

      Click here to expand...

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

   8. Runtime configurability 

      Click here to expand...

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

   9. Performance / Scale 

      Click here to expand...

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

3. FCREPO-1777 - Vagrant Integration Testing

4. Status of "in-flight" tickets

   Click here to expand...

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

5. ...

Ticket Summaries

1. Please squash a bug!

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   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

1. Updates from last two weeks

   1. Last week was in-flight tickets
      1. FCREPO-1777
      2. Methodologies around packaging (came up during work on FCREPO-1823)
      3. Outstanding pull requests on fcrepo4-client
      4. Messaging around getting folks to focus on the new fcrepo4-java-client as opposed to fcrepo4-client
      5. A ticket will be created to survey the landscape of LDP clients ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. )
      6. Discussion around upgrading to Jena 3.0 (rdf 1.0 vs 1.1)
         1. Breaks about a dozen tests because of how literal behaviour changes
         2. Should we wait?
      7. January release
         1. empowering folks to cut releases for individual modules
         2. policy? consensus on a call?
2. Tickets aligned with roadmap themes
   1. These are the central themes we are focusing on, and our development should be prioritized on tickets touching on these.
      1. May need to discuss our coupling with JCR semantics and dependencies, especially as it relates to reimplementation of modules.
      2. How do we effectively get to a REST API?
      3. How do we support alternate implementations?