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 
6. Ben Pennell 
7. Calvin Xu 
8. Michael Ritter 
9. Demian Katz
10. Geoff Scholl 

Agenda

1. Announcements
2. Fedora Desktop Client
   1. Why?
   2. What would it do?
      1. Auto Sync Directories
      2. Manage concurrent uploads
      3. Search
      4. Manage downloads
      5. Bulk Updates to metadata 
      6. Bulk deletes
   3. Why is this good for Fedora
      1. New use cases
      2. Raises Visibility
      3. Potentially expand organizational support to smaller institutions
3. Fedora Core + Tools Release
   1. Review what is going into these releases
      1. components to be released
         1. fcrepo-java-client
         2. fcrepo-storage-ocfl
         3. jetty-console
         4. fcrepo
         5. fcrepo-upgrade-utils
         6. fcrepo-migration-utils
         7. fcrepo-migration-validator
   2. Issues
   3. Do we want anything else to go in?
      1.   FCREPO-3699 - Getting issue details... STATUS
      2. FCREPO-3777 - Getting issue details... STATUS
4. Camel Toolbox  Release
   1. components to be released 
      1. fcrepo-camel
      2. fcrepo-camel-toolbox
   2. Issues
      Click here to expand...

      Key	Summary	T	Created	Updated	Due	Assignee	Reporter	P	Status	Resolution

      Loading...

      Refresh

5. New tickets
6. Your topic

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