Time/Place

This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Audio/Video Conference Link:   https://lyrasis.zoom.us/j/88068382811
  
  • Meeting ID: 880 6838 2811
  • Find your local number: https://lyrasis.zoom.us/u/ad6Xb7q3ia

  • Join fedora-project.slack.com on the "tech" channel

  • Self-register at: http://slack.fcrepo.org/

Attendees 

1. Danny Bernstein 
2. David Wilcox  
3. Jared Whiklo
4. Peter Winckles  
5. Ben Pennell
6. Calvin Xu 
7. Michael Ritter  
8. Demian Katz
9. Geoff Scholl 
10. Jon Roby 

Agenda

1. Announcements
2. Feedback Session Debrief
3. Camel Toolbox Sprint October 4-8 Planning
4. Current Work / New Issues/Bugs
   1. Camel toolbox status
      1. Fixity PR
         1. FCREPO-3760 - Getting issue details... STATUS
      2. Audit Triplestore PR
         1. FCREPO-3761 - Getting issue details... STATUS
      3. Andy's work
         1. FCREPO-3770 - Getting issue details... STATUS
      4. Villanova work
         1. FCREPO-3753 - Getting issue details... STATUS
            1. https://github.com/fcrepo-exts/fcrepo-camel-toolbox/pull/166
   2. FCREPO-3773 - Getting issue details... STATUS
      1. https://github.com/fcrepo/fcrepo/pull/1941
   3. FCREPO-3771 - Getting issue details... STATUS
      1. https://github.com/fcrepo/fcrepo-storage-ocfl/pull/44
         1. https://github.com/fcrepo/fcrepo/pull/1942
         2. https://github.com/fcrepo-exts/fcrepo-upgrade-utils/pull/47
5. Upgrading RDF ontology versions
6. Tickets available to be worked before 6.1.0 release:
   1. FCREPO-3767 - Getting issue details... STATUS
   2. FCREPO-3739 - Getting issue details... STATUS
   3. FCREPO-3700 - Getting issue details... STATUS
   4.   FCREPO-3699 - Getting issue details... STATUS
7. Your topic here

Tickets

1. In Review

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

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

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

Notes