Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:

• Time: 10:45am Eastern Daylight Time US (UTC-5)
• Google Hangouts: https://plus.google.com/hangouts/_/event/ccnv0ba94h3fb2je3gscunqc49g
• IRC:
  
  • Join the #duraspace-ff chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #duraspace-ff on irc.freenode.net

Attendees

• Andrew Woods
• Jonathan Green
• Unknown User (daniel-dgi)
• Harry R. Sidhunata
• Dr. Arif Shaon
• Chris Beer
• Greg Jansen
• Benjamin Armintor
• A. Soroka

Agenda

• 3.7 Status
• Recent Fedora4 updates
• Fedora4 Beta-phase Planning
  
  • CLAs
  • Sprint Schedule
  • Fedora4 Feature Priorities

Notes

Beta Logistics

1. Developer stand-up meetings
   
   1. Agreement that daily stand-ups are important
   2. Due to the spread of timezones, suggestion to schedule two stand-ups per day
      
      1. Exact times to be decided on-list (ff-tech@googlegroups.com)
2. Development iteration window
   
   1. The iteration schedule is posted here
   2. In order to accommodate European and Australian timezones, sprints will be run for 11 days
      
      1. Start on Monday
      2. End on Thursday of the following week
   3. Exact times for iteration planning meeting and iteration close meeting to be decided on-list (ff-tech@googlegroups.com)
3. Iteration definition and validation
   
   1. There is a need to have features of each sprint be driven by institutional use cases
   2. Representatives of Fedora stakeholder institutions (sponsors, advisors, steering group) will help define and "sponsor" sprint features
   3. At the sprint conclusion, the feature "sponsor" will validate the delivered feature
   4. Feature validation may be enabled by any of a number of mechanisms
      
      1. Install the iteration release at the institution
      2. Download the source code and run a given build command with a given configuration at the institution
      3. Execute HTTP commands against a Fedora hosted on behalf of the institution
4. CLAs
   1. Fedora committers should sign and return an individual CLA
   2. Fedora committer insitutions should sign and return CCLA

Fedora 3.7 Status

1. Ben A. has addressed several recent bugs
2. Fedora 3.7 release candidate will likely be ready for system testing this week

Recent Fedora 4 Updates

1. Ben A. is working on upgrading to JAX-RS 2.0
2. Chris B. and Adam S. have been working on bringing Fedora4 into line with principles of Linked Data Platform
3. First official sprint of the Beta phase starts Monday, July 29th