[ocis][adr] Write ADR for activities API and store - 4 PD

[micbar]

Description

User Stories

• As a client, i want to obtain history information about resources to show a timeline of events

Value

Brings transparency to the collaboration spaces

Acceptance Criteria

• [ ] Written ADR
  • [ ] Clients cat obtain activity information about resources
  • [ ] Clients can narrow the search on a space/folder/ file
  • [ ] Results should list recursively the events of all possible children of the selected resource
  • [ ] Lookup should be efficient and fast 😄
  • [ ] Expect huge amounts of data
  • [ ] Depending on the store, describe how data can expire

Definition of ready

• [ ] Everybody needs to understand the value written in the user story
• [ ] Acceptance criteria have to be defined
• [ ] All dependencies of the user story need to be identified
• [ ] Feature should be seen from an end user perspective
• [ ] Story has to be estimated
• [ ] Story points need to be less than 20

Definition of done

• Functional requirements
  • [ ] Functionality described in the user story works
  • [ ] Acceptance criteria are fulfilled
• Quality
  • [ ] Code review happened
  • [ ] CI is green (that includes new and existing automated tests)
  • [ ] Critical code received unit tests by the developer
• Non-functional requirements
  • [ ] No sonar cloud issues
• Configuration changes
  • [ ] The next branch of the ocis charts is compatible