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/396037251
- Meeting ID: 396 037 251
- 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

Announcements
June 1-5 Sprint
1. Post suite wrap-up
2. Reflections
3. Next Demo
4. Fedora 6 Feature Tracking
5. Fedora Test Suite Results
Renaming of 'master' branch?
Defining Fedora ID limits
Search
1. escapes within condition params
Open questions:
1. JMS: Remove Fedora-related JMS messaging headers? 2018-04-26 - Fedora Tech Meeting
  1. ACTION: Jared to investigate potential impact on Camel tooling - updates?
  2. Ralf Claussnitzer Message headers are useful for filtering (Camel and Nifi) → No need to parse message JSON body.
Community-raised bug: Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Your Topic Here

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.

In Review

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.

Please squash a bug!

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.

Tickets resolved this week:

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.

Tickets created this week:

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.

Announcements
June 1-5 sprint
1. accomplished quite a bit
2. 1 pending ticket
3. not a ticket, but progress made on documenting fedora-ocfl structure and header file structure
  1. Fedora Header Files
  2. Fedora OCFL Object Structure
4. reflections
  1. lots of PRs on Friday => fedoraful weekend
  2. contingencies come up
  3. fairly smooth
5. next demo
  1. search? Danny & David will work on it.
  2. database work?
6. mark features that should be done
7. test suite - someone run it after each spring & track results over time
  1. performance tests - run existing jmeter tests and/or modify them. Add to next sprint.
renaming of master branch
1. sooner or later it'll change
2. how to handle with existing PRs? can retarget all PRs in GitHub.
fedora id limits
1. OCFL persistence - archival group parts, because of mapping logical paths to content paths
  1. translate between logical path and content path?
2. limitations based on how to persist fedora-specific data (eg. reserving .fcrepo, ...)
3. DB - eg. varchar in mysql limit - could be avoided
4. discuss later

Andrew Woods to reply to leaders side-loading thread with proposal
Danny Bernstein to ensure that a JIRA exists for scenario of transaction does not succeed completely, but rollback does succeed (see: 2020-06-11 - Fedora Tech Meeting)
Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-06-11 - Fedora Tech Meeting)
Who: Clarify in documentation that multiple simultaneous writes to OCFL are not supported
Jared Whiklo to investigate impact of removing JMS Headers on camel tooling.