...

• 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
      Alpha 2 release starts later today
      1. finished design, hopefully ready Friday
      1. Today is the last meeting of the year
      2. Reminder: Fedora-related proposals for Code4Lib in March
   2. Tickets to discuss?
   3. Some of new tickets: 
      1. 1. low hanging:

            Jira
            server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3582

             
         2. low hanging:

            Jira
            server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3583

         3. Jira
            server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3561

         4. Documentation tickets
   4. 1. (deadline: Dec 21st)
         1. contact David for info, need to present the proposal in 10-15min presentation
      2. 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
   5. 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 
   6. 120 tickets in the Prioritized list of issues.
      Beta
      1. Review Criteria for Beta
      2. Prioritized list of issues. (everything in red is slated for beta
      3. 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
      1. Beta release sprint in Q1 of 2021?
         1. Pilot updates
         2. 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
         3. Pilot updates
         4. What else can we be doing with GitHub Actions?<Your topic here>

         
         

         Tickets

         1. In Review

            Expand
            Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

            
            

         2. Please squash a bug!

            Expand
            Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

            
            

         3. Tickets resolved this week:

            Expand
            Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

            
            

         4. Tickets created this week:

            Expand
            Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

            
            

         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