Time/Place

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

Attendees

Agenda

  1. Upcoming Sprints 
    1. Please sign up
    2. Sprint 1: Release 5.0
      1. Optimally we start Sprint 1 with a release candidate
      2. Mostly complete documentation
      3. Wrap up the compatibility test kit
    3. Sprint 2: (if 5.0 is release) Ecosystem Tools
      1. Camel Toolbox
      2. Java Client
      3. Import/Export
    4. What is the best way to prepare as a team?
      1. Proposal:  mini sprint for external content and minor spec alignment issues that are coming out of the CTS development.
      2. Alternative to a mini sprint:  form group willing to commit to doing (1?2?3?) of the following small things each week:
        1. work a minor bug
        2. review a documentation page
        3. write a new CTS test (lots of opportunities)
        4. fix an existing CTS test (lots of opportunities here as well)
  2. Getting to 5.0 Release Candidate
    1. 5.x Documentation Effort matrix
    2. In progress tickets
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    3. Remaining external content (low-hanging: ie volunteers?, mini-sprint?) issues:

      key summary type created updated due assignee reporter priority status resolution

      Unable to locate Jira server for this macro. It may be due to Application Link configuration.

    4. All API Alignment Issues

      type key summary assignee reporter priority status resolution created updated due

      Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Closing Fixity conversation:  
    1. UMD + NLM design collaboration
    2. Andrew's suggestion of a "pluggable module"
      1. (What is a pluggable module in fedora today? Does that notion exist independently of API-X?)
  4. <Add your agenda item here>

Ticket Summaries

  1. Please squash a bug!

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Tickets resolved this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Tickets created this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Minutes

Upcoming Sprints

  1. Outstanding work
  2. Continual effort on the above would potentially prepare us for the sprints
  3. How do people feel about picking up work leading up to sprint?
  4. Could mini-sprints help?
    • Mini-sprint: focused effort on specific tasks in limited timebox
  5. Interest in executing on intentions
    1. Planning for the following week could be helpful
  6. Team commitments / intentions
    1. Jared to commit 1/2 of Fridays to Fedora items
    2. Ben available on Thursdays (versioning and external-content)
    3. Bethany has availability
  7. Priorities
    1. Delta document wiki
    2. Compatibility test suite
    3. Documentation
    4. Fedora implementation

Tickets

  1. fcrepo-2742: Allow single-document ACLs using hash URIs for authorizations
    • No GET on /fcr:acl (ticket?) 2806 / 2807
    • PATCH on hash URIs may not have the correct subjects (Peter to create ticket)
    • PUT to /fcr:acl with body not yet supported (Peter to create ticket)
  2. fcrepo-2771: Mementos have incorrect subject returned
    • Bethany familiarizing with the surrounding code
    • No blockers at this time



  • Danny to explore inserting a macro into documentation for Fedora version.
  • Send email to community seeing who is interested in reviving OAI




  • No labels