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/88068382811
  
  • Meeting ID: 880 6838 2811
  • 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 

1. Danny Bernstein 
2. David Wilcox  
3. Arran Griffith 
4. Jared Whiklo
5. Peter Winckles   (out)
6. Ben Pennell 
7. Calvin Xu 
8. Michael Ritter  
9. Demian Katz
10. Geoff Scholl 

Agenda

1. Announcements
   1. David Wilcox's Bon Voyage: Friday 10/22 1pm Eastern time 
2. Post Sprint Update
3. Issue Drilldown: 
   1. FCREPO-3739 - Getting issue details... STATUS
   2. FCREPO-3746 - Getting issue details... STATUS
4. Tickets available to be worked before 6.1.0 release:
   
   1.   FCREPO-3699 - Getting issue details... STATUS
5. Fedora Analytics
   1. expand metrics and potentially automate setup of grafana dashboard
      1. bytes ingested over time
      2. pull together prometheus and database info using a charting front end tool kit with prometheus datasource integration such as chartjs (https://github.com/chartjs/awesome)
         
         
   2. Information we can easily display using search index:
      1. resources CRUD in the last n number of days
      2. recently added (by time frame)
      3. current size of the repository
      4. pie chart of bytes stored by mimetype
      5. pie chart of count stored by mimetype
      6. bar chart of resource count by size in bytes
      7. bytes ingested by user
      8. files ingested by user
      9. ?
6. Ticket needing merging:
   1. https://github.com/fcrepo-exts/migration-utils/pull/174
7. Demo Video scheduling
8. ?

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