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 
• Yinlin Chen 
• Aaron Birkland 
• A. Soroka 
• Andrew Woods
• Unknown User (acoburn)
• Bethany Seeger
• David Wilcox
• ...

Agenda

1. Vulnerability: Java object serialization

   1. http://fishbowl.pastiche.org/2015/11/09/java_serialization_bug/ 
   2. http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/

2. Modeshape5: https://developer.jboss.org/message/945504

   1. Plan
      • standard API
      • multiple impls
        • f4 over mode w/level-db
        • f4 over mode w/jdbc
        • f4 over casandra
   2. Considerations
      • minimize migrations
      • simplify migrations
3. IDCC F4 workshop in Amsterdam – Fedora committer volunteers?
4. Nov/Dec/Jan plans
   1. consider upcoming travel

5. ...

Ticket Summaries

1. Please squash a bug!

   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. 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. Java Serialization Vulnerability - (link to email thread) Andrew Woods, Benjamin Armintor, Unknown User (acoburn) have all looked into this and concluded that this does not affect fedora4.

2. Modeshape5 - modeshape community is moving away from infinispan because in cluster configuration they are unable to maintain consistency. modeshape is now focused on "scaling up" rather than "scaling out". Perhaps infinispan will return later.
   1. Fedora currently relies on infinispan and has been advertising the clustering capabilities of modeshape/infinispan.