Page History

...

1. Housekeeping: 
   1. Sprint Dates:  https://doodle.com/poll/2vgw3huvr8dugeuq:  
      
      1. Sept 10-2422
      2. Oct 1-14 12 
   2. Leader for next week's call
2. OR Impressions discussion
   1. Did OR change your thinking about future directions for Fedora?
      
      1. New features
      2. Future integrations
      3. ? 
   2. Other discussion questions here: 
3. Getting to 5.0
   1. In progress tickets
      

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2742

      2. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2717

      3. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2718

      4. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2771

   2. Remaining external content (low-hanging: ie volunteers?) issues:

      Expand
      Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery key in (FCREPO-2776,FCREPO-2801,FCREPO-2752,FCREPO-2802,FCREPO-2796,FCREPO-2797) serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

      
      

   3. 5.x Documentation Effort matrix
   4. Compatibility Test Kit
4. 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? 
5. Ecosystem tools progress report
   
   1. Outstanding PRs
6. 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
7. <Add your agenda item here>

...

1. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

2. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

3. Tickets created this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

Minutes

1. Housekeeping: 
   1. Sprint Dates:  https://doodle.com/poll/2vgw3huvr8dugeuq:  
      
      1. Sept 10-24
      2. Oct 1-14 
   2. Leader for next week's call
2. OR Impressions discussion
   1. Did OR change your thinking about future directions for Fedora?
      
      1. New features
      2. Future integrations
      3. ? 
   2. Other discussion questions here: 
3. Getting to 5.0
   1. In progress tickets
      
      1. Image AddedFCREPO-2742 - Allow single-document ACLs using hash URIs for authorizations. Reopened
      2. Image AddedFCREPO-2717 - A PUT on an LDP-RS should be denied if acl:Append applies In Progress
      3. Image AddedFCREPO-2718 - Disallow PUT, POST, and DELETE on LDP-NR where acl:Append applies In Progress
      4. Image AddedFCREPO-2771 - Mementos have incorrect subject returned Open

   2. Remaining external content (low-hanging: ie volunteers?) issues:

   3. 5.x Documentation Effort matrix
   4. Compatibility Test Kit
4. 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? 
5. Ecosystem tools progress report
   
   1. Outstanding PRs
6. 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
7. <Add your agenda item here>

Actions

•  Write JIRA ticket regarding calculating the SHA1 checksums Carrick Rogers (

  Jira
  server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2805

  )
•  Consider Extending Doodle Poll to later date, it closes this Friday (Danny Bernstein)
•  Send an email to fedora-tech seeing if anyone is using the java client (people are and importexport tool uses it)
•  Send email to community seeing who is interested in reviving OAI

...