...
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 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 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
Outstanding issues on API spec
- Privacy and security settings
- Should we add security/privacy specifications ?
- Call attendees should review this issue and approve/disapprove
- Clarify LDP 5.5.1.2
- Should we specify a behaviour or remain silent?
- Daniel Lamb: we should probably remain silent but this creates problems for swapping out implementations
- Hard to say now if we will need this down the road
- Don’t use lists with indirect containers
- Anyone with an opinion should comment on this issue
- Revisit PUT for creating new resources
- Discussion revolves around POST, not PUT
- Jared will add a comment to try to achieve some consensus
- Say `Expect: 202-digest` intended for use with `HEAD`?
- Needs to be summarized so we can proceed to comment further