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://duraspace.zoom.us/my/fedora
  

  • Dial-in:
    +1 408 638 0968
    +1 646 876 9923
    +1 669 900 6833
    Meeting ID:
    812 835 3771

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

Attendee

• Danny Bernstein
• Jared Whiklo
• Peter Eichman 
• Carrick Rogers 
• Kevin Ford  
• Michael Durbin
• David Wilcox
• Joshua Westgard
• Doron Shalvi
• Aaron Birkland
• Andrew Woods
• Ben Pennell
• James Silas Creel
• Bethany Seeger

Agenda

1. Housekeeping: 
   1. Sprint Dates:  https://doodle.com/poll/2vgw3huvr8dugeuq:  
      
      1. Sept 10-24
      2. Oct 1-14 
   2. Leader for next week's call
2. OR Impressions discussion
   1. Did OR change your thinking about future directions for Fedora?
      
      1. New features
      2. Future integrations
      3. ? 
   2. Other discussion questions here: 
3. Getting to 5.0
   1. In progress tickets
      
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

   2. Remaining external content (low-hanging: ie volunteers?) issues:

      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. 5.x Documentation Effort matrix
   4. Compatibility Test Kit
4. Possible New Feature (Set): Signposting
   
   1. Does it belong in the Fedora Layer? API-X? Other?
   2. If so, should the spec be modified to include it? 
5. Ecosystem tools progress report
   
   1. Outstanding PRs
6. Review Spec committee's direction on Fedora API Specification github issue (one-step fixity check)
   
   1. Also what about dangling question about storing checksums as a server managed triple? 
   2. Fedora API Specification "Candidate Recommendation #2" in the process of being released
   3. Fixity check encouraged as a sidecar specification
7. <Add your agenda item here>

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

Actions

• Write JIRA ticket regarding calculating the SHA1 checksums Carrick Rogers ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. )
• Consider Extending Doodle Poll to later date, it closes this Friday (Danny Bernstein)
• Send an email to fedora-tech seeing if anyone is using the java client (people are and importexport tool uses it)
• Send email to community seeing who is interested in reviving OAI