Fedora Futures - CNI 2012


Published on

This is the announcement and introduction of the Fedora Futures project at the December 2012 CNI Members Meeting in Washington DC

1 Comment
1 Like
  • New technology is going to appear, spurred on by ipv6, by tablets, by desktops without hard disks or cd roms, etc.

    We need to start to look at anticipating and designing opensource technology (hardware and software) that meets that Fedoras needs and inspires.

    A short term development is to look at an open source computer bios that hardware manufacturers can implement

    I look forward to reading more about futures.
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Fedora Futures - CNI 2012

  1. 1. Fedora FuturesCNI 2012, Washington DC
  2. 2. Background● Original software created 2000-2008 ○ $2.4 million from the Mellon Foundation ○ $500,000+ from UVA Library● Codebase management and improvement has been continued by the committers group ○ Acuity Unlimited, Columbia, Cornell, DTU, FIZ Karlsruhe, the Denmark State Library, MediaShelf, UVa, U. of Wisconsin ○ Plus 3 independent software developers● DuraSpaces sponsorship program has provided funding for the technical lead
  3. 3. Fedora Futures Genesis● Fedora Futures started with meeting of stakeholders at OR2012 in July● Decision to discuss a project to move Fedora technology to next stage● 2nd meeting in DC, Sept 17-18● Decision to define details for a Pilot to determine interests and use cases● Launch of the initiative being held in DC after CNI
  4. 4. Fedora Futures: Groups● Steering Committee: M Leggott (Chair), E Shin, J Markow, T Cramer, T Staples, R Cartolano, R Ruggaber, W Horstmann, M Razum● Tech Group: E Shin (Product Manager), B Armintor, J Green, A Soroka, Ben OSteen, Chris Beer, F Asseg● Fundraising Committee: Jonathan Markow (Chair), Tom Cramer, Thorny Staples, Rob Cartolano
  5. 5. Current Strengths● Architecture is Flexible & Extensible● Support for Durability● A decade of maturity & proven use● Substantial community of adopters and contributors● One foot in the linked data world ○ rels-ext, triplestore, flexible content modelling
  6. 6. Opportunities● Performance● Fault tolerance and scalability● Complexity● Aging code base● Relatively small, fixed pool of active developers
  7. 7. Objectives1. Preserve the strengths of the architecture and community2. Address the needs for robust and full- featured repository services (that we now understand very well)3. Provide a platform in the repository ecosystem for the next 5-10 years
  8. 8. Goals: Functional● Work for small, medium & large institutions● Support the traditional IR (et al.) use cases● Support new data management needs● Retain emphasis on Durability● Interoperate with other systems● Go "native" in the Web of Data
  9. 9. Goals: Organizational● Revitalized pool of contributors● Remake the codebase and development environment to promote a "Joy of Coding"● Increase the level of community involvement, support & governance in Fedora
  10. 10. Use Cases● FF Steering Group and FF Tech Group identified some 30 use cases● Large overlap - four major topics ○ manage research data ○ improve administrability ○ handle heterogenous data more efficiently ○ interact with linked open data/semantic web
  11. 11. Main Actors● Curator● Administrator● Researcher● Developer
  12. 12. Derived High-levelRequirements● Technical Requirements ○ improve scalability and performance ○ more flexible storage options ○ support for dynamic metadata ○ globally unique and reliable identifiers ○ improved audit trail/capturing events● Non-technical requirements ○ straightforward and fun to use API
  13. 13. The Plan● Fedora, revisited ○ Fedora is the Flexible, Extensible, Durable, Object Repository Architecture. Fedora provides the essential platform for institutions to provide durable, sustainable services to collect, curate and disseminate their digital assets.● Object Lessons from Our Community ○ High risk, long lead-time product development processes ○ Agile is not a panacea
  14. 14. The Plan, contd● A "Lean" Methodology ○ Build - Measure - Learn● Our promises to the community ○ Continuity & Growth ○ Shipping product● Regular, short deliverables ○ Measured & validated with ambassadors representing large constituencies ○ Developer workshops● Project Kick-off ○ 12 December 2012
  15. 15. Closing Comments● Staffing● Funding● Governance● How to get involved: ○ Questions and discussion: Tuesday, 3:30pm (right after CNI), Pan American Room - All invited ○ Cant stick around? Email us: ■ Jonathan Markow - jjmarkow@duraspace.org ■ Eddie Shin - edwin.shin@yourmediashelf.com