Versions Compared

Key

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

...

  • (15 mins) Developer Stand Up - Developers give brief updates on their effort (or their team's effort).

    • Update/see "Current Work" section below based on your status. Please feel free to update prior to meeting.
    • Please highlight any new work (needing reviews/testing), any blockers (for you), and any discussion topics you may have.
  • (30 mins) General Discussion Topics
    1. REST API discussion:  Reminder to all (self included) which endpoints can support which methods
      1. Per our Contract README: https://github.com/DSpace/Rest7Contract/blob/master/README.md#use-of-the-http-verbs-and-http-response-code
      2. Multiple Resource (i.e. Collection) Endpoints (e.g. /items) may support only POST and GET
      3. Single Resource Endpoints (e.g. /items/:uuid:) may support GET, HEAD, PUT, PATCH and DELETE
      4. Sub-paths only act on associations between resources (e.g./items/:uuid:/mappedCollections), and only allow GET, PUT, POST, DELETE of those associations.
        1. We may need to revisit the decisions in these two recent PRs:
          1. https://github.com/DSpace/Rest7Contract/pull/79 (Community & Collection Logo).  Should PUT/DELETE just use /bitstreams/<:logo_uuid>? (as Logos are Bitstreams!)
          2. https://github.com/DSpace/Rest7Contract/pull/80 (Collection Item Templates).  Should PATCH/DELETE just use /items/<:itemtemplate_uuid>? (as Templates are Items!)
    2. Revisiting REST API Projections: https://jira.duraspace.org/browse/DS-3533Revisiting our Code Review processes for PRs
      1. Up until now, all PRs require two code reviewers
      2. As we've seen, this provides good feedback, but can cause review/implementation delays if only one reviewer can be identified in a timely fashion
      3. This issue was brought to Steering Group.  Recommendation is to consider allowing for single reviewers for smaller / more obvious PRs, with option of that reviewer asking for an additional reviewer if they find something requiring additional feedback.
    3. Revisiting REST API Projections: https://jira.duraspace.org/browse/DS-3533
    4. Reviewing & scoping tasks flagged as "NEEDS MORE INFO" in Development Planning Spreadsheet
      1. This is necessary to prepare for the next phase of the DSpace 7 Estimation Process
  • (15 mins) Planning for next week

...