Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Dial-in Number: (712) 775-7035
  • Participant Code: 479307#
  • International numbers: Conference Call Information
  • Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
• IRC:
  
  • Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #fcrepo on irc.freenode.net

Attendees 

• Jared Whiklo 
• Nick Ruest 
• Bethany Seeger
• Longshou Situ
• Unknown User (acoburn)
• A. Soroka
• Yinlin Chen
• Esmé Cowles
• Michael Durbin
• Kevin Ford
• Andrew Woods
  
• Peter Eichman
  

Agenda

1. LevelDB corruption issues - potential fix 4.1.1 (fcrepo-webapp-4.1.1-recovery.war)

2. Update on Versioning Spec - meeting notes

3. Fedora API GitHub repo(s)

   1. Which GitHub organization? fcrepo? duraspace?
   2. One or many repos?
   3. Are the constituent parts of the API versioned separately?
4. Time to deprecate filesystem federation?
5. Time to move fcrepo-message-consumer out of fcrepo4-exts?
6. Review of: https://github.com/fcrepo4/ontology/pull/37
7. ModeShape5 update
8. Repository configuration (e.g. repository.json): should this be standardized in any way or do different Fedora implementations use whatever configuration style/content that makes sense for the implementation?
9. Logging recommendations and style-guide
10. ...

11. Status of "in-flight" tickets

    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.

Ticket Summaries

1. 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.

2. 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.

3. 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.

Minutes

1. LevelDB corruption issues - potential fix 4.1.1 (fcrepo-webapp-4.1.1-recovery.war)

   1. Discussion of a couple mailing list issues

      1. Consensus on Andrew Woods proposed resolution of
         1. using patch
         2. exporting content
         3. upgrating through fcrepo versions up to 4.5.1

   2. Get folks off LevelDB; Make a strong statement

      1. Timing is problematic due to Modeshape 5
         
         

2. Update on Versioning Spec - meeting notes

   1. Waiting to get things into GitHub repo to proceed, and then into W3C spec format
      
      

3. Fedora API GitHub repo(s)

   1. Which GitHub organization? fcrepo? duraspace?
      1. fcrepo - https://github.com/fcrepo
   2. One or many repos?
      1. One standard with parts/chapters
   3. Are the constituent parts of the API versioned separately?
      1. Version as a unit
         
         
4. Time to deprecate filesystem federation?
   1. Came from Esmé Cowles, out the D.C. Fedora Users group meeting
   2. Use webservers that perform better
   3. Discussion about moving it from core to fcrepo4-exts, or actually deprecating it
   4. Extract federation out of core base?
      1. Yes.
      2. Move it to labs
      3. Provide community notice, how to move from labs to exts
      4. If nobody picks it up after a period of time (to be determined), move it to archives/deprecated
   5. We need to make a deprecation warning, and a release before we do that
      1. "Super-double-down-deprecation-warning-with-blink-tags"
         
         
5. Time to move fcrepo-message-consumer out of fcrepo4-exts?
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Move to labs
   3. Provide community notice, how to move from labs to exts
   4. If nobody picks it up after a period of time (to be determined), move it to archives/deprecated
      
      
6. Review of: https://github.com/fcrepo4/ontology/pull/37
   1. This pull request brought up bigger issues about where this should live, and how things are organized
   2. Move to fcrepo4-exts
      1. Combine https://github.com/fcrepo4-exts/fcrepo-indexing-ontology & https://github.com/fcrepo4-exts/fcrepo-audit-ontology into a single fcrepo-exts ontology github repo, but still published as they are
      2. Discussion on how versioning will work if they are combined in one github repo
   3. Merge the pull request
   4. Needs some cleanup after move (A. Soroka will do it!)
      
      
7. ModeShape5 update
   1. Carry to next meeting
      
      
8. Repository configuration (e.g. repository.json): should this be standardized in any way or do different Fedora implementations use whatever configuration style/content that makes sense for the implementation?
   1. Carry to next meeting
      
      
9. Logging recommendations and style-guide
   1. Carry to next meeting