Time/Place

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

Attendees 

Agenda

  1. Review of fcrepo4-labs and fcrepo4-exts for shifting

    1. fcrepo-kernel-filesystem - remove?

    2. fcrepo-karaf - promote to exts?

    3. fcrepo-message-consumer - archive?

    4. fcrepo4-packer-aws-grinder - archive?

    5. fcrepo-aws-puppet - archive?

    6. fcrepo-test-grinder - archive?

  2. Fedora 4.6.0 release plan?
    1. Support influx of Sufia7 users' use of JDBC over LevelDB ()

    2. Support ModeShape 5.1 – ready to test now ()

    3. Support WebAC alignment with Hydra community

    4. Common logging practice in fcrepo-http exception mappers? ()

  3. Source code license header, see: http://apache.org/licenses/LICENSE-2.0.html#apply
  4. DGI's announcement of an attempt at an alternative Fedora 3 implementation
  5. Import/export of Bags
  6. Use of Maven BOMs in the fcrepo4 codebase... embrace or abort? And generally, how are dependencies managed?
  7. Commons RDF in fcrepo-kernel-api
  8. ...

  9. Status of "in-flight" tickets

Ticket Summaries

  1. Please squash a bug!

  2. Tickets resolved this week:

  3. Tickets created this week:

Minutes

  1. Review of fcrepo4-labs and fcrepo4-exts for shifting
    1. fcrepo-kernel-filesystem
      1. Remove or archive
    2. fcrepo-karaf
      1. Not ready to exts yet
        1. Needs tests
        2. Needs second maintainer
        3. Leave in labs
    3. fcrepo-message-consumer
      1. Move to archive
    4. fcrepo4-packer-aws-grinder
      1. Move to archive
    5. fcrepo-aws-puppet
      1. Move to archive
    6. fcrepo-test-grinder
      1. Move to archive
  2. Fedora 4.6.0 release plan
    1. Blockers
      1. Modeshape5; Blocker for release until there is reliable migration tooling
        1. Is JCR import/export functionality sufficient? Need more information/testing.
          1. Esmé Cowles will test this
      4. Issues revealed in the testing of
        1. Discussion about approach in the pull request, and alternative solutions
          1. On-behalf-of principle should only be limited to admin users OR On-behalf-of principle be limited to a list that is defined and users can delegate
          2. "I think this ticket requires a document of expected behaviors we can test against"
          3. Too much reliance on client instead of principle provider; principle provider should handle it.
          4. Benjamin Armintor will investigate feasibility of both solutions tomorrow.
      6. Taking out file connector
    2. Want, but not blocker
    3. Revisit this all next week
  3. Source code license header, see: http://apache.org/licenses/LICENSE-2.0.html#apply
    1. Updating the year, every year is a sustainability issues
    2. Have a header that references Apache 2 in each file that references a single notice file that gets updated on a yearly basis
    3. Nick Ruest will create a JIRA ticket, and Andrew Woods will do the work
    4. Need to do a new release of the build tools, which enforces the header.
  4. DGI's announcement of an attempt at an alternative Fedora 3 implementation
    1. Discussion about discoverygarden's announcement and how it affects the Fedora, Islandora, and Hydra communities
    2. Extend conversation to discoverygarden, we would like to hear from them
    3. Bring to Fedora Leadership Group
    4. Bring to Islandora Foundation Board of Directors
  5. Import/export of Bags
    1. Ran out of time
    2. Add your name as a stakeholder if you're interested!