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

1. Danny Bernstein
2. Andrew Woods
3. Jared Whiklo  
4. Ben Pennell 
5. Peter Eichman  
6. Bethany Seeger
7. Aaron Birkland

Agenda

1. Announcements

   1. Barriers to Migration Survey

      1. Key take aways
         1. Fedora 3 File System Layout is popular
         2. People like Fedora's linked data support
         3. API is popular with users
         4. Lack of staff time and good migration tooling present biggest barriers for migration
   2. 2019-05 Fedora Camp Atlanta
   3. Fedora 6 Sprint Doodle
2. Fedora 5.1.0  Release
   1. 5.1.0 Open (is triage complete for inclusion in 5.1.0?):
      1. 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. 5.1.0 Closed
      1. 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.

   3. 5.1.0 Open (need to re-evaluate for inclusion in 5.1.0):
      1. 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.

3. Import Export
4. Fedora 6.0.0 Sprint planning 
   1. High-level roadmap 
   2. Tactics
      1. Development Roadmap
      2. Pilot Program
      3. Contracting
5. <Your agenda item 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

Actions

• Peter Eichman  is planning to work on documenting UMD's fixity check system on the  Fedora in Production: Case Studies wiki page.
• Jared Whiklo to fix Java 11 javadoc errors in a new ticket, link to fcrepo-2958
• Danny Bernstein to rename 5.x-maintenance to 5.0.x-maintenance