You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

Time/Place

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

Attendees

  1. Danny Bernstein
  2. Peter Eichman
  3. Bethany Seeger
  4. Jared Whiklo 
  5. David Wilcox (star)
  6. James Silas Creel
  7. Andrew Woods
  8. Kevin Ford
  9. Aaron Birkland
  10. Michael Durbin
  11. Ben Pennell
  12. Longshou Situ

Agenda

  1. Announcements

  2. Weekly Progress Update
    1. JIRAs Closed

      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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. JIRAs in Review
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    3. CTS Progress Report 

      1. 1 PR Awaiting more feedback : https://github.com/fcrepo/Fedora-API-Test-Suite/pull/150
    4. Documentation Efforts

  3. State of WebAC

  4. State of JIRA

    1. (Fedora 5.0.0 Preparation Tasks)

  5. Review of Pre-Sprint Opportunities for Contribution (In other words: what can we do this week)
    1. Review the Jira List
    1.  Ideas for coming week

      1. Low hanging fruit (once 2742 is merged)
        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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

      2. A little higher in the tree:
        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.
  6. Why is the OriginalResource link header required for creating a Versionable object?
  7. Community contribution:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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

Announcements

  • Fedora IMLS grant awarded to investigate barriers to upgrade/migrate to Fedora 4.x. Work starting this Fall.

Weekly Progress Update

  • Andrew leaving room for others to review PRs
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Ready to be merged in after one more review
  • https://github.com/fcrepo/Fedora-API-Test-Suite/pull/150 
    • Concerns have been addressed
  • Documentation effort
    • Kevin has been working on this, particularly with regard to versioning

State of WebAC

  • In good shape for upcoming sprint
  • Only missing feature for spec compliance is ACL control
  • Peter will make a ticket to look through AuthCommon for deprecations

JIRA Tickets

  • 5.0.0 preparation tasks
  • Need to review list of tasks not in the API alignment epic
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Still some coupling to ModeShape in role provider
    • Bethany will work on this
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  
    • Not much work left to do on this one
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Use URIs instead of strings to identify people in WebACs. Basic auth doesn't allow URIs instead of strings. Andrew will close the ticket
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • This will be discussed more actively next week as we dig into the sprint work
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Peter running tests now, should be able to resolve today
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Longshou working on this, close to finished
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Peter needs to add a couple tests. Will finish later this week or early next week
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • External content documentation task. 
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Research task. Is there a way to decouple this? Marked as minor but could be a major issue for API-X, reindexing, etc. 
    • Jared could take a look between sprints. 
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Need to make sure tests are passing. Should be a quick review.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Is the approach taken here one that we want to pull in?
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Both tickets are low hanging fruit

Actions


Future Agenda Topics: 

  • No labels