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 
• Kevin S. Clarke
• Bethany Seeger
• Yinlin Chen 
• Doron Shalvi 
• Benjamin Armintor 
• Andrew Woods
• James R. Griffin III

Agenda

1. Fixing bugs as they come up on the mailing list...

   1. Andrew Woods advocates ownership, implying need for SG to create space for employees to do this work
   2. FCREPO-1980 being investigated by Unknown User (acoburn)
2. 4.5.1 RC-2 testing status
   1. Release Testing Procedures - Template for future release.

3. Fedora Specification

   1. Messaging SPI <- close to done, need to tighten RDF serializations
   2. Atomic Batch Operations
   3. CRUD <- needs to include elements of RESTful HTTP API
   4. Resource Versioning <- not currently aligned with reference F4 impl, since that is just a copy/exposure of JCR which cannot be imported into specs
   5. Binary Fixity Checking <- needs help
   6. Authorization <- needs help

4. Should we remove old release candidates from github? https://github.com/fcrepo4/fcrepo4/releases

5. Looking for a Fedora techie to attend Archivematicamp

6. With scripts as a starting point, TCKs in Ruby?

   1. Should Unable to locate Jira server for this macro. It may be due to Application Link configuration. be closed?
   2. Should Yinlin Chen continue working on https://github.com/yinlinchen/fcrepo4-release-tests ?
7. A complementary service to fcrepo-serialization?
8. ...

9. 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