Time/Place

Attendees

Topics
Establish previous minor release support policy i.e. What is the policy for back-porting bug fixes to 4.0.0? 4.1.0? etc
Fedora 4 migration survey results
Audit service planning and development
Designing a data migration tool
DuraSpace Summit responsibilities Project update on day 1 Breakout groups on day 2

Send out message to Leaders re: Migration Working Group (David Wilcox)
Send out message to Leaders re: feature priorities with Jan. 30 deadline for feedback (David Wilcox)

Establish previous minor release support policy

Came out of Committer team, should we back port to previous releases.
No Past policy for Fedora 3.
Depend on Fedora 4 stability advocates back ports. Will slow releases did it for major reasons.
Light adoption of fedora 4 so far.
Security issue maybe different
How much do we want to back port? Costs resources
Consensus: Security releases for X number of minor releases
Action: Offline discussion on how many versions to support.

Fedora 4 migration survey results

Everyone should have received a copy of the results but if not contact David
54 respondents
XML ingest + audit top 2 Fedora 3 requests.
Respondents Want documentation and migration tools both high on the TODO list
Also case studies and training.
Frontends a people moving from Custom to Hydra post migration. Custom front ends going down.
Most people in the 100k number of objects. 3/4 less than 10TB
Migration timescales varied
1/2 not duraspace members
Intending to send summary to community. Anyone opposed : no opposition
Any trends in misconceptions or impractical assumptions with migration? No trends a few misunderstandings but generally good understanding of Fedora 4. Lots of requests for documentation and case studies.

Audit service planning and development

Meeting this Friday (see https://groups.google.com/forum/#!topic/islandora/UE2TK781nmc)
Cost: 2 sprints from 3 developers
Seeking commitments 1 for sure
March 23rd sprint starts
Need 1 or 2 more developers for this sprint.
First feature trying to design this year.
Would be good to get more requirements before planning meeting on Friday.
Are there developers available for fedora 3 features? 4 features not in Fedora 4 (coloured in green in the Questionnaire summary), developers seem interested but difficult to get commitment. Audit service supported by one institution offering a developer which is why its going forward.
For LDP paging and Web Access Control waiting for the standards to be stable.

Designing a data migration tool

Mike Durbin working on designing and building a tool. Moving fedora 3 to Fedora 4 migration. Created page on wiki for people to enter their Hydra, Islandora and Custom models.
code4lib discussions: Hydra put a large amount of work in designing objects taking advantage of the linked data platform. Islandora community also reviewed and validated Hydra models. Will be a Unified approach to modelling data, custom installations will probably follow suit. Common language for talking across comunities.
Adam from Penn State already done some development for Hydra migration. Mike from UVA put together some tools for upgrading from Fedora 3 to 4, Ben from Columbia also thinking about this. Important that we involve community in discussion.
Upgration pilots waiting on this tooling.
Action: Andrew asks that we ask our technical people to review the approach specified in Fedora 3 to 4 wiki. Also look at the Java project and try it out.
Mike focusing on a straight Fedora migration rather than Hydra or Islandora based migration.
Using the Thursday technical call to discuss this. Wales and York happy to be part of the discussion. Ben from Columbia looking at this in March.

DuraSpace Summit responsibilities

Have ideas for breakout groups, chair of steering group will provide updates for the projects.
Robin asked to do 20 min presentation on Fedora : status, progress in the last year, what to look forward to for next year. 10mins of questions. (Day 1)
Day 2: planning 3 x 45 minutes session in the morning for project breakouts, discuss top 3 issues. After lunch general session and David (Product Manager) summaries what was discussed.
- Topic 1: Sustainability
- Topic 2: Positioning Fedora future
- Topic 3: Pilot Test and Implementation
- Topic 4: What do you need the digital repository to do in the next 3 years
Group number 1 & 2 to keep to 3. Will send out details closer to the time. Robin to approve order with steering

Offline discussion on how many Fedora 4 versions to support and back port security fixes to.
Andrew asks that we ask our technical people to review the approach specified in Fedora 3 to 4 wiki. Also look at the Java project and try it out.