Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Pipeline: references, large scenes and robustness

Open
  • Is something wrong?
#58 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
desktop

Research direction

This is a tracking issue, not a code task. Read .project-docs/parity.md (the Pipeline and robustness section) and the pinned reference in #5 to see what is pending. The first step is to split each unchecked item into its own child issue with a sourced workflow list, which a maintainer needs to approve. Done means those child issues exist and follow the feature gates, not that any feature is built here.

Written by the indexing model from the issue text.

Description

area/file-io area/infra epic type/feature

Problem

No references, large-scene handling or robustness workflows.

Current behavior

.project-docs/parity.md (Pipeline and robustness): references, recovery, large scenes pending.

Expected behavior

Staged support.

Checklist:

  • File references
  • Large-scene performance budgets
  • Recovery (see its issue)
  • Signed and notarized platform packages (needs a maintainer decision on release authority)

Acceptance criteria

  • Each checklist item is split into its own issue before work starts, with a sourced workflow list.
  • Every child follows the feature gates: visibly unsupported until done, MCP coverage with schemas, Editor protocol tests and docs, native visual check.
  • No percentage or parity claim until the pinned reference (#5) and the audited inventory exist.
Dominant language
Rust
Stars
4
Forks
2
Avg merge
2h 28m
Merged PRs (30d)
76

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cristim/AztecCraft

All issues in cristim/AztecCraft

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.