Server management of data
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
The specification should provide guidance on how servers are expected to manage data with data pods.
For example, data pod owners ought to expect the following:
- data is encrypted at rest, with keys securely managed by the data pod (ie no shared keys)
- secure internal data transfers between components of the server
Ideally the server should also support data immutability and history, thereby allowing owners the option to manage some or all of their data in different ways.
Finally the server should support metadata and audit for each item of data.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing specification guidance for servers and data pods. Clarify the expected guidance for encryption at rest, secure internal transfers, immutability and history, metadata, and audit; done means these requirements are documented consistently in the specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100