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 
• James R. Griffin III
• Unknown User (acoburn)
  
• Unknown User (escowles@ucsd.edu)
• Bethany Seeger
• Nick Ruest 
• Andrew Woods
• Jared Whiklo
• David Wilcox
• Unknown User (daniel-dgi)

Agenda

1. Discuss: Java8 Stream construct vs. Guava Iterators for lazy evaluation (the kernel modules currently rely extensively on Iterators, for example: RdfStream)

2. 4-position versioning scheme, redux
3. Github Housekeeping: Close stale branches, old issues
4. 2015-08-14 - Fedora API Extensions Meeting tomorrow

5. Tickets resolved this week:

6. Tickets created this week:

Minutes

1. We have been using Guava, but now Java8 provides us with a lot of the same functionality without external libraries. So, should we refactor?
   1. Pros: Less code. Less external library dependencies.
   2. Cons: Stream and iterator are not the same thing.

   3. Not a full find and replace.

   4. Consensus: Use stream where it is appropriate. Use iterator where it is appropriate.

   5. Meta-discussion about priorities and focus
   6. 
   • Action: Andrew Woods to restructure priorities and focuses in JIRA to represent the project vision [as Andrew Woods described it earlier in this call].
2. Discussion about Fedora's versioning scheme
   1. Should we move to normal sematic versioning?
   2. Should we have LTS releases, or terms of support for each release?
   3. If we abandon the 'Product version' in our versioning policy, how do we handle messaging and marketing – communication?
   4. No general consensus on moving from status quo.
3. We should do some house keeping!
   1. Keep an eye on GitHub notifications to see if you have pinged.
4. Please attend the meeting if you can.