Versions Compared

Key

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

...

Attendee

Agenda

...

  1. Upcoming Sprints
  2. Sept 10-22
  3. Oct 1-12 
    1. Please sign up
    2. Focus of each sprint
      1. Sprint 1: Release 5.0
        1. Optimally we start Sprint 1 with a release candidate  
        2. Complete documentation
        3. Wrap up the compatibility test kit
      2. Sprint 2: Ecosystem Tools
        1. Camel Toolbox
        2. Java Client
        3. Import/Export
  4. On the subject of Import/Export...
  5. Getting to 5.0 Release Candidate
    1. In progress tickets
      1. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-2742
      2. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-2771
    2. Remaining external content (low-hanging: ie volunteers?) issues:

      Expand

      Jira
      serverDuraSpace JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      maximumIssues20
      jqlQuerykey in (FCREPO-2776,FCREPO-2801,FCREPO-2752,FCREPO-2802,FCREPO-2796,FCREPO-2797)
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


    3. 5.x Documentation Effort matrix
    4. Compatibility Test Kit
  6. Possible New Feature (Set): Signposting
    1. Does it belong in the Fedora Layer? API-X? Other?
    2. If so, should the spec be modified to include it? 
  7. Ecosystem tools progress report
    1. Outstanding PRs
  8. Sidecar specification update
    1. Review Spec committee's direction on Fedora API Specification github issue (one-step fixity check)
      1. Also what about dangling question about storing checksums as a server managed triple? 
      2. Fedora API Specification "Candidate Recommendation #2" in the process of being released
      3. Fixity check encouraged as a sidecar specification
    2. Transactions
  9. <Add your agenda item here>

...