Update AppNote 0001 to include an example of retaining the original segment
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- documentation
Research direction
Start by reading docs/appnotes/0001-multi-mono-essence-flows-sources.md and review its existing Flow and Source examples. Add an example and diagram for retaining the original single-segment mixed Flow alongside segmented mono-essence Flows and transcoded proxies, and explain that the segmented Flows can map essence from the concrete multi when only the container changes. Done means the AppNote clearly covers this upload scenario.
Written by the indexing model from the issue text.
Description
Context
AppNote 0001 describes a variety of structures of Flows and Sources for various purposes.
When discussing a tool for uploading camera cards, it came up that you might want to retain the original single-segment mixed Flow from the card, as well as segmented mono-essence Flows, and transcoded proxies.
Actions
We should provide an example and diagram for this case, and indicate that the segmented Flows can be the same ones that map essence from the concrete multi, providing only the container has changed.
Outcome
AppNote improvements
Note this is also tracked as https://jira.dev.bbc.co.uk/browse/CLOUDFIT-5587
- Dominant language
- Makefile
- Stars
- 110
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
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.
More from bbc/tams
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
documentation spec
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100