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)
• U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
• International toll free:  http://www.readytalk.com/intl 
  
  • Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial-in number
  • Once on the call, enter participant code 2257295
• 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 

• A. Soroka 
• David Wilcox 
• James R. Griffin III
• Andrew Woods
• Unknown User (acoburn)
• Yinlin Chen  
• Unknown User (daniel-dgi)
• Unknown User (escowles@ucsd.edu) 
• Nick Ruest
• Bethany Seeger
• Kevin S. Clarke

Agenda

1. 4.3.0 Release is out

   1. Process reflections and improvements
   2. Release candidates?
2. 4.4.0 focus
   1. Move projects into fcrepo-exts (see: F4 GitHub Organizations)
   2. Decouple those projects from the fcrepo4 pom.xml parent
   3. Plan on all extras projects starting independent versioning with 4.4.0
      1. Therefore, 4.4.0 will represent a common ground zero
   4. OSGi - demonstrate runtime configurability of F4?
   5. Servlet-API version? 3.01 -> 3.1.0

3. ...

4. Current Priorities

   Click here to expand...

   1. Performance
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Single subject
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   3. fcr:metadata as a container
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   4. Point-like objects
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   5. Camel RDF serializer
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   6. Migration-utils
      • Wait for Mike
   7. Bugs
      • 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.

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

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