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
• Unknown User (acoburn)
  
• Unknown User (escowles@ucsd.edu)
• Bethany Seeger
• Michael Durbin
• Andrew Woods
• Jared Whiklo 
• Yinlin Chen
• Aaron Birkland
• Kevin S. Clarke
• Andy Wagner

Agenda

1. F4 GitHub Organizations - "Becoming an fcrepo4-exts project"
2. WebAC update
   1. Hydra and Islandora involvement?
3. m2.duraspace.org hosting update

4. Please squash a bug!

5. Tickets resolved this week:

6. Tickets created this week:

Minutes

1. F4 GitHub Organizations:
   4 github organization: fcrepo4 (core), fcrepo4-lab (new effort), fcrepo4-archive (old projects, no longer development), and fcrepo4-exts (projects related to fedora). Detail info F4 GitHub Organizations . Please feel free to edit that page and add your comments.
   Note: ajs6f: The core is closed. New project to fcrepo4-exts need at least 2 owners in order to be considered.
   
   
2. WebAC update:
   First sprint end tomorrow, has initial implement covered some basic scenarios. Detail info: Design - WebAccessControl Authorization Delegate . You can download the code, build a war file and play it. Will have a second Sprint.
   Note: escowles will bring this up to hydra people to sync both efforts.
   
   
3. m2.duraspace.org hosting update:
   m2.duraspace.org hosting will be phased out in next 12 months.
4. Cluster:  yinlin will investigate

5. Asynchronous Storage:
   May go api-extension 

   ajs6f: We really don't have a good pattern available for asynchronous REST. The more strongly we commit to REST as the architectural style for the Fedora API, the more this kind of stuff should get pushed into extensions.

   awoods: Suggested people to add more use cases, send out emails to communities.

6. Welcome to pick some tickets and solve issues.