Tracking: OpenRecipe as a standalone open format
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- json, typescript
- Domain
- backend
Research direction
Start with the linked work in packages/core, especially #97, then follow #98 for the spec, JSON Schema and conformance fixtures and #99 for versioning and upgrade-on-read. The issue says these first three steps can happen in the monorepo; #100, publishing a separate repository, is deferred until the format settles or has an outside user. Done means the format is separated, specified and versioned, with OpenSkillet consuming it as a dependency.
Written by the indexing model from the issue text.
Description
Summary
Make the OpenRecipe recipe format a standalone open-source spec that other projects can use and give feedback on, with OpenSkillet consuming it as a versioned dependency (like a separate API definition the app pulls its structure from).
No pressure on timing. Parked here to come back to.
Steps
- #97 Separate the format from app features in
packages/core - #98 Spec, JSON Schema and conformance fixtures
- #99 Versioning policy and upgrade-on-read
- #100 Move to its own repo and publish
Steps 1–3 can happen inside this monorepo and are worth doing regardless. Step 4 makes sense once the shape has settled or there's an outside user. Until then, a second repo mostly adds publish-and-bump friction.
Related: #63 (the CLI's lint command would be a natural first consumer of the standalone format).
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 10h 51m
- Merged PRs (30d)
- 48
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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 dnerever/OpenRecipe
-
UI/UX improvementsOpenenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
dnerever/OpenRecipe#73 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
dnerever/OpenRecipe#100 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
dnerever/OpenRecipe#99 ·
Maintainers usually reply within 1 day
-
documentation enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
dnerever/OpenRecipe#98 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
dnerever/OpenRecipe#97 ·
Maintainers usually reply within 1 day
All issues in dnerever/OpenRecipe
Similar issues
-
e2e-failure ready-to-code
Difficulty 1/5 Under an hour Newbie friendliness 82/100
redhat-developer/rhdh-plugin-export-overlays#4616 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
ai-handle
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nextlevelbuilder/dewee-web-v2#73 ·
Maintainers usually reply within 1 day
-
backend bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
PoCInnovation/Distribox#255 ·
Maintainers usually reply within 1 day