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 
• Unknown User (acoburn)
• David Wilcox
• Doron Shalvi
• Kevin S. Clarke

Agenda

1. Bugs are beginning to pile up 

   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. Fedora Specification updates
   
   1. Messaging SPI
   2. Atomic Batch Operations - name? BatchOps? Bag-o'-Ops? OpSack? AtomicOp?
   3. CRUD
   4. Resource Versioning
   5. Binary Fixity Checking
   6. Authorization
3. ...

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

Review of current Bugs:

Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Assigned to Diego Pino Navarro, but he may be busy at present.

Unable to locate Jira server for this macro. It may be due to Application Link configuration. - We should confirm that the error condition described in this ticket actually exists. A. Soroka will add a comment to this ticket.

Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Server Errors should include the correct Content-Type (at present, this should be text/plain). As a follow-on, should error responses be RDF? and should Fedora support conneg for errors?

Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Now assigned to Unknown User (acoburn).

Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Missing headers. Some parts of this can be merged with FCREPO-1887. A. Soroka will add comments to the ticket.

Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Stack trace – this condition should result in a 409 Conflict error.

Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Is this a limitation of Modeshape or an error with Fedora? or is this a function of a default Hydra repository layout? It was decided that the ticket will be closed as "Won't Fix"

Unable to locate Jira server for this macro. It may be due to Application Link configuration. - No activity since November. A. Soroka will ask Nianli Ma for a status update

Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - No activity since November. A. Soroka will ping Esmé Cowles

Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Unknown User (acoburn) will work this ticket using the touch() method to update jcr:lastModified on referenced nodes, asynchronously (A new ticket will be created to remove the Properties header from emitted Events: Unable to locate Jira server for this macro. It may be due to Application Link configuration. )

Unable to locate Jira server for this macro. It may be due to Application Link configuration. - This seems more like a Modeshape issue than a Fedora issue. It could be closed and reopened with the modeshape project

Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Copied from a github issue. A. Soroka will ping Esmé Cowles about whether the tombstone mechanism would work here

Unable to locate Jira server for this macro. It may be due to Application Link configuration. - This will be addressed by the maintainer of the OAI project

Unable to locate Jira server for this macro. It may be due to Application Link configuration. - this is a low priority and will be closed for now

Unable to locate Jira server for this macro. It may be due to Application Link configuration. - This is expected behavior for SPARQL and not a bug. Unknown User (daniel-dgi) should use an OPTIONAL block for possibly missing properties.