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 

• Danny Bernstein
• Andrew Woods
• David Wilcox 
• Jared Whiklo 
• Peter Winckles 
• Ben Cail 
• Calvin Xu
• Daniel Lamb
• Ben Pennell
• Thomas Bernhart

Agenda

1. Announcements
   1. fcrepo-migration-validator Sprint underway
      1. finished design, hopefully ready Friday
   2. Today is the last meeting of the year
   3. Reminder: Fedora-related proposals for Code4Lib in March (deadline: Dec 21st)
      1. contact David for info, need to present the proposal in 10-15min presentation
   4. Leaders meeting update
      1. discussed beta requisite 
      2. discussion around data-gathering provision from fedora installations (eg. institution emails, name, etc using fedora) 
      3. autoversioning vs on-demand object versioning
         
         1. Danny Bernstein will create a Jira ticket per object versioning
         2. immutable heads PR issue: Andrew suggest more documentation needed at different level such as wiki and README
2. Alpha 2 release starts at 1pm eastern
   
   1. final release of 2020, congratulation to everyone for their hard work and dedication 
   2. user reported testing 10x speed faster than MariaDB and MySQL on fedora6, planning looking into on bring MariaDB and MySQL up to speed 
3. 120 tickets in the Prioritized list of issues.
   1. everything in red is slated for beta
   2. Do we need to prioritize the blue tickets (ie for 6.0.0 or post-6.0.0)
      1. do the prioritization of blue ticket after Beta
4. Beta release sprint in Q1 of 2021?
   1. either early January or mid-late February depend on team's availability, propose two week sprint and followed by another sprint focused on documentation
   2. Consensus on weeks of Feb 8 and Feb 15th
5. Pilot updates
6. What else can we be doing with GitHub Actions?

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

• Danny Bernstein will create a Jira ticket per object versioning
• Andrew Woods  will Andrew create documentation needed at different level such as wiki and README for the immutable head PR issue 
• Prioritization of blue tickets after Beta release