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
• Aaron Birkland 
• Stefano Cossu 
  
• Unknown User (daniel-dgi)
  
• Andrew Woods
• Yinlin Chen
• Jared Whiklo
• Doron Shalvi
• Unknown User (acoburn)

Agenda

1. Service provider idea? https://groups.google.com/d/msg/fedora-tech/UovyLGZeToE/lNRtWZZ4JM4J

2. Does fcrepo-webapp belong in the fcrepo4 github project?

   1. One issue is that there are two webapp modules: one for core, one for core+optional modules. This may not be ideal, especially as more optional modules become available (e.g. fcrepo-audit)
   2. Another issue is that putting fcrepo-webapp in core ties the reference implementation to a particular deployment strategy (tomcat/jetty). Other strategies, however, may be more appropriate for some adopters (e.g. OSGi or "containerless"). The counter argument is that a reference implementation should be minimally deployable. 
3. F4 core, extras, and labs (mailing list thread)
   1. What are the "core" Fedora capabilities/projects?
   2. Which projects are always included in any given release?
   3. Should we decouple the version number schemes of optional projects from core releases?
   4. Should optional projects share the same "org.fcrepo" package namespace?
   5. What are the criteria for graduating from (1c)? - Practices from Islandora? Hydra?
   6. What is the policy for deprecating a project from (1a) or (1b)?
   7. What should the name of a third GitHub organization be, if such an organization is needed?

4. ...

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

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

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