Versions Compared

Old Version 1

changes.mady.by.user Danny Bernstein

Saved on

compared with

New Version Current

changes.mady.by.user Andrew Woods

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attendee

  1. Danny Bernstein
  2. Andrew Woods
  3. Jared Whiklo  (star)David Wilcox
  4. Ben Pennell 
  5. Peter Eichman (star) 
  6. Bethany Seeger
  7. Aaron Birkland
  8. Yinlin Chen
  9. Doron Shalvi
  10. Daniel Lamb

Agenda

  1. AnnouncementsDebrief: Washington D.C. Area Fedora User Group Meeting and OCFL Hackathon: 7-8 May 2019

    1. Barriers to Migration Survey

      1. Key take aways
        1. Fedora 3 File System Layout is popular
        2. People like Fedora's linked data support
        3. API is popular with users
        4. Lack of staff time and good migration tooling present biggest barriers for migration
    2. 2019-05 Fedora Camp Atlanta
    3. Fedora 6 Sprint Doodle
  2. Fedora 5.1.0  Release... manager?
    1. In-Review:
      1. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-2991
    2. 5.1.0 Open (is triage complete for inclusion in 5.1.0?):


      1. Expand

        Jira
        serverDuraSpace JIRA
        jqlQueryfilter=14902
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


    3. 5.1.0 Closed


      1. Expand

        Jira
        serverDuraSpace JIRA
        jqlQueryfilter=14901
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


    4. 5.1.0 Open (need to re-evaluate for inclusion in 5.1.0):


      1. Expand

        Jira
        serverDuraSpace JIRA
        jqlQueryfilter=14902
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  3. Import Export
  4. Fedora 6.0.0 Sprint planningplanning 
    1. High-level roadmap 
    2. Tactics
      1. Development Roadmap
      2. Pilot Program
      3. Contracting
  5. <Your agenda item here>
  6. What is the breakdown of tasks?
    7. Could we potentially contract any of it?

Tickets

  1. In Review

    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=13100
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  2. Please squash a bug!

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13122
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  3. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  4. Tickets created this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13029
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


Notes

  1. announcements
    1. barriers to migration survey
      1. why are people still on F3
      2. people like the idea of linked data
      3. sharing data is valuable, people recognize that
      4. we do hear a lot about how people don't like linked data
        1. main pushback sources:
          1. people designing against the API (e.g. Samvera), may not be as easy as other models
          2. people who want to have a non-exposed/buried Fedora
      5. linked data is more useful/popular with users than developers
      6. general approach: emphasize linked data is optional
      7. there is value in showing how to replicate F3 models in F4+
        1. Jared has a presentation for OR about Fedora without linked data
      8. missing features in F4
        1. query support
        2. validation in the repository
        3. field ordering; difficult in RDF
      9. file system layout in F3 is very possible
    2. Fedora Camp
      1. there is still room
      2. encourage people to come if it would benefit them
    3. Fedora 6 sprint Doodle
      1. dates when Danny and/or Andrew are available
      2. ideally 3 sets of 2 week sprints
      3. please fill out the dates when you think you could be available
      4. once we have dates, come up with broad goals for each sprint
  2. Fedora 5.1.0 release
    1. Jared is release manager
    2. raised and resolved a couple issues regarding binary descriptions (FCREPO-2996, FCREPO-2997)
    3. state token issue merged
    4. 3 outstanding bugs
      1. been open a while
      2. may be difficult to fix under Modeshape
    5. Andrew will have PRs for FCREPO-2782 with DuraSpace checkstyle rules
      1. contains suppressions for new DuraSpace rules Fedora doesn't conform to
      2. future conversation about whether to adopt these
      3. release buildtools with updates
      4. then update the maven stuff to use the new release of buildtools
    6. 5.1.0 RC once checkstyle updates are in place
      1. goal is RC this week, 3 weeks before OR
      2. 2 week window for community review
  3. import/export
    1. Mohamed started testing at UMD
    2. there might be a way to import a F4 export to F5 if we can ignore ACLs and versions
      1. UMD is not using versions, and only has a tiny number of ACLs
    3. no work happening on Danny's end next week (Fedora camp)
      1. maybe target week after next
    4. process:
      1. export with F4 tool
      2. remove ACLs (by hand) from exported files
      3. import with F5 tool
    5. not a formal release per se
      1. wait for F5-to-F5 round tripping to release
    6. resumability is a huge feature for UMD
      1. borrow features from plastron, UMD's batch tool
      2. use an embedded SQL database to track progress?
  4. Fedora 6 sprint planning
    1. David put together a public high-level roadmap
    2. there is also a committer-generated development roadmap
    3. F6 high-level roadmap
      1. synchronous query, i.e., synchronously updating index for querying
        1. is this for Samvera?
        2. synchronous is not in the design document
        3. maybe it means that they want a bundled query service
        4. want a query service that talks to the same store as persistence; guarenteed consistency
        5. F3 had a simple synchronous query service
          1. indexed a defined subset of content
          2. F3 also had integration with triplestore, could be either synchronous or asynchronous
        6. need to pilot these query services with folks who have these use cases
          1. determine to what extent synchronicity is required
          2. could there be an optional way to enable synchronous indexing? header? config setting?
  5. Announcements
    1. Vote at the Leadership level to approve the Fedora 6 design at a high level. So we are going to work on a more detailed layout to help identify resources that might be needed.
  6. DC Fedora Users Group
    1. Folks are wondering on the timeline for Fedora 6. Are we talking about 2 years? Are we talking about Fedora + all migration tooling. We need to document our plans and what we are going to create to help the community know what they are getting.
    2. A release in 2019 is probably not realistic at this point, but on some leader calls there is a notion that until we have our ducks in a row that there will be beta releases. Tying in to some things discussed at the FUG, there is a concern to commit to Fedora 6 without a level of comfort that it covers the needs and is supported and stable. If we are at the end of the year with a couple "pilots" to show some different use cases and scenarios that could be a good place.
    3. Get some good design and implementation feedback from some of these "pilot" partners. We can then produce some data modeling recommendations for the community.
    4. If we fire up Fedora 6 on top of OCFL, how does Fedora know what to do with it. Need a pilot partner that needs that to happen.
    5. There is a plan to secure pilots discussed with Leaders and yes there is a concern about building another island.
    6. Question of resources? Do we bring in contractors for partners who don't have the developer team to support. Perhaps working with the contractors for testing which requires less knowledge of the internals but would provide a lot of useful information.
    7. The Barriers to Migration survey has been completed with over 100 responses, so the hope is to collect this data and perhaps use that data to support some grant applications for funding.
    8. Could funds from Duraspace be put in to mini-grants to entice partners to look at and perhaps participate in a Fedora 6 pilot.
    9. Could we offer additional support from the technical team if the "pilot" organization doesn't have the internal resources.
    10. What is the next step in this pilot process? Should we clarify any of this with Leaders? We are largely on the same page as Leaders, but we do need to make some specific requests (this goes back to the detailing of the plan from above) for code sprints, funding, etc.
  7. 5.1.0 - Jared Whiklo has volunteered to be release manager. Hoping to get https://github.com/fcrepo4/fcrepo4/pull/1523 and https://github.com/fcrepo4/fcrepo4/pull/1520 merged next week with the release candidate put out on May 17. Then we have 3 weeks until Open Repositories. Bethany Seeger has volunteered to help with the release.
  8. Do we work on two proof of concept storage layers at the same time. Broader question of having a storage API, but what is it written in. Is this an externally accessible API? Do we stick with a Java implementation only for the community implementation.  For now we just build a Java interface. Concern that people is too LDP heavy and is a web standard and so if you just want to store your data and don't care about the LDP stuff. Could there be a separate API at a lower level to avoid the LDP specification.
  9. How big of a need is not having to deal with the LDP interaction, it would be good to get the survey results from the the Barriers to Migration.
  10. Jared Whiklo is also hoping to fix FCREPO-2996 and FCREPO-2997
  11. Islandora 8 is using Fedora 5 when it is released.

Actions

...