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)
• ReadyTalk:
  
  • 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 #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

• Greg Jansen
• Esme Cowles
• Michael Durbin 
• Andrew Woods
• Benjamin Armintor

Agenda

1. Review current fcrepo4 work.
   
   1. Triple store integration
   2. Customizable search indexes
   3. Large file performance
   4. Fcrepo3 migration
   5. roles-based AuthZ
2. 4.0.0-alpha-2 release
3. Merging Fedora 3 and 4 community resources
   
   1. IRC
   2. Mailing lists
   3. Wiki
   4. GitHub
   5. Issue tracker?
4. European hackfest

Previous Actions

• Michael Durbin to create Pivotal tickets for UI polish
• Benjamin Armintor to send email for others to sign his and other committers' keys

Minutes

1. Decided upon rotating scrum master, Greg did great, and will moderate this meeting.
2. Review current work
   
   1. Triplestore integration
      
      1. Esme added documentation to the wiki, will finish clear instructions on easily installing and configuring the major components
      2. Esme intends to fix a bug he discovered relating to property updates not triggering events (like indexing)
   2. Customizable search indexes
      
      1. The plan is for completion of a stub implementation of a solr indexer, with a fuller implementation expected on the next sprint
      2. everyone should look over the original wiki brainstorming and provide feedback
   3. Large file performance
      
      1. a pull request has been made to ModeShape to use external library to more quickly compute SHA-1
      2. updates have been made to cache the SHA-1 rather than recompute
      3. Consideration has been given to using a hash of the path, rather than the content for the identifier
   4. Fedora 3 migration
      
      1. Fixed bug with content download
      2. Added fedora 3 object and datastream properties
      3. Intends to complete a hierarchical view of the repository to work around limitations on nodes with lots of children
      4. University of of New South Wales has started acceptance testing on the fedora 3 upgrade path
         
         1. Documentation for acceptance testing could follow the template here: Acceptance Testing - Beta
   5. Roles based AuthZ
      
      1. All the right checks are coming into the authorization provider, expect to be completed tomorrow.
      2. Difficulty encountered writing integration tests with OAuth tests due to Grizzly shortcomings.
3. Fedora 4.0.0-alpha-2 release
   
   1. Moving towards having regular releases (ie, every 2 sprints)
   2. Ensure that any of a number of people can easily produce a release
   3. Release versions are useful for acceptance testing
   4. difficulty when releases are infrequent and release manager is new to the process
   5. sometimes plugins work in dry run but fail in production run (ie pushing javadocs)
   6. create documentation about release, with notes of all difficult parts and the solutions
4. Merge community resources (fedora 3 and 4)
   
   1. Bifurcation made sense when "fedora futures" was just an experiment, but does it continue to serve us?
   2. Should we move towards talking about this project as just the next version of fedora?
   3. Merge issue tracking.
      
      1. Pivotal isn't as community friendly for bug tracking
      2. JIRA isn't very development happy for sprints (though greenhopper is an improvement)
      3. we'll likely tackle this consolidation effort last
   4. Merge wiki
      
      1. some of the fedora 4 structures may be worth keeping rather than applying the fedora 3 templates
      2. we should maintain naming convention continuity ("fedora futures" --> "fedora 4") 
   5. Merge github, cleaning out cruft projects
   6. Move to uniform google group mailing list
5. European Hack Fest
   1. DC Steering committee meeting
      1. Hackfest
         1. Should there be two or three a year?
         2. There should be one in Europe, between December and March.
         3. Some concerns with a two week thing (doubling up with a conference) due to productivity drop-off in second week and the difficulty of taking 2 weeks away from work and family.

Actions