Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We prefer smaller PRs that merge more often.
Haiku-length summary
Documentation
Better in than out, I say
The repo tracks all
Additional details
The ticket for the
collect
service captured a lot of the design thinking for this service. After a discussion with @IsabelLaurenceau , I wrote it up and put it in the docs. It is assumed that as we work on this (and as @luisgmetzger dives in) that questions will arise/edits will be made/etc. But, for now, it provides a concrete starting point for implementation and discussion.The checklist is mostly empty,a s this is a strictly documentation commit. Related to #64.
PR Checklist: Submitter
main
into your branch shortly before creating the PR. (You should also be mergingmain
into your branch regularly during development.)PR Checklist: Reviewer
make macup ; make e2e"
(FIXME)The larger the PR, the stricter we should be about these points.