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 

• Andy Wagner
• Benjamin Armintor
• Jared Whiklo 
• Longshou Situ 
• Esmé Cowles 
• David Wilcox 
• Katherine Lynch
• Andrew Woods
• Nick Ruest
• A. Soroka
• Mark Jordan
• Unknown User (acoburn)

Agenda

1. Review of fcrepo4-labs and fcrepo4-exts for shifting

   1. fcrepo-kernel-filesystem - remove?

   2. fcrepo-karaf - promote to exts?

   3. fcrepo-message-consumer - archive?

   4. fcrepo4-packer-aws-grinder - archive?

   5. fcrepo-aws-puppet - archive?

   6. fcrepo-test-grinder - archive?

2. Fedora 4.6.0 release plan?
   
   1. Support influx of Sufia7 users' use of JDBC over LevelDB ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. )

   2. Support ModeShape 5.1 – ready to test now ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. )

   3. Support WebAC alignment with Hydra community

   4. Common logging practice in fcrepo-http exception mappers? ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. )

3. Source code license header, see: http://apache.org/licenses/LICENSE-2.0.html#apply
4. DGI's announcement of an attempt at an alternative Fedora 3 implementation
5. Import/export of Bags
6. Use of Maven BOMs in the fcrepo4 codebase... embrace or abort? And generally, how are dependencies managed?
7. Commons RDF in fcrepo-kernel-api
8. ...
9. Status of "in-flight" tickets
10. Click here to expand...

    

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.

   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