RFC 0028: new target version and schema identifier
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 64/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation
Research direction
Read RFC 0028 and compare its target version with the references named in RFC 0020, the workflow companion, the RFC index, and the VERSIONING heading. Review schema/workflow-contributors-2.schema.json for its $id. Update the target and schema identifier when RFC 0028 is next worked on, then check that those references agree; the issue leaves the release values to be decided.
Written by the indexing model from the issue text.
Description
RFC 0028 (Draft) names Spec 0.5.0 as its target, and its draft schema schema/workflow-contributors-2.schema.json carries an $id under the /schema/0.4.0/ namespace.
Both are now out of step:
specVersion0.5.0is assigned to the Core version that adds annotations and value sets, so RFC 0028 needs a new target. The same target is named in RFC 0020, the workflow companion, the RFC index and a VERSIONING heading.- No Core
0.4.0exists or will exist, so the draft$idsits under a namespace that no released version owns. It is unpublished draft staging and was left as it stands by thev0.4.0andv0.5.0releases.
To decide when RFC 0028 is next worked on: its target version, and the $id its schema takes when it is released. Until then nothing published depends on either.
- Dominant language
- Python
- Stars
- 5
- Forks
- 6
- Avg merge
- 2h 39m
- Merged PRs (30d)
- 77
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the 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 Judgment-Pack/judgment-pack-spec
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Judgment-Pack/judgment-pack-spec#335 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Judgment-Pack/judgment-pack-spec#299 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
Judgment-Pack/judgment-pack-spec#293 ·
Maintainers usually reply within 1 day
-
dialect §2: drop the adapter-http query exception once Runner v0.28.0 holds query to §4.1May be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Judgment-Pack/judgment-pack-spec#282 · 1 comment ·
Maintainers usually reply within 1 day
-
Cover a rule's or an exception's reference list written without its array, or with a repeated entryOpengood first issue
Difficulty 2/5 Half a day Newbie friendliness 76/100
Judgment-Pack/judgment-pack-spec#158 ·
Maintainers usually reply within 1 day
All issues in Judgment-Pack/judgment-pack-spec
Similar issues
-
cognition facet:consolidation memory ready size:S
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
proposal
Difficulty 1/5 Under an hour Newbie friendliness 68/100
j3ko/agent-plugins#29 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
-
area:cli area:security bug priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
docs pydanty:is-working
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pydantic/pydantic-ai#13563 ·
Maintainers usually reply within 1 day