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

Animation: timeline, keys, graph/dope editors, layers and playback

Open
  • Is something wrong?
#52 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
computer-graphics, desktop

Research direction

This is an umbrella issue, so the first step is to read .project-docs/parity.md (Animation section) and the pinned reference in #5 to see what the scope covers. The issue asks for each checklist item to be split into its own child issue with a sourced workflow list before any work starts. Done here means those child issues exist and the acceptance criteria are met, not that animation code is written.

Written by the indexing model from the issue text.

Description

area/animation epic type/feature

Problem

Not implemented.

Current behavior

.project-docs/parity.md (Animation): not implemented.

Expected behavior

Staged animation support. References: Time Editor clips https://help.autodesk.com/cloudhelp/2026/ENU/Maya-Animation/files/GUID-0CE7D311-4B6E-4140-9DD3-850FFC970BEE.htm , clip layers https://help.autodesk.com/cloudhelp/2026/ENU/Maya-Animation/files/GUID-B3FFE1AA-F44D-4EC3-A570-316A3BF3DF88.htm .

Checklist:

  • Time Slider and Range Slider (see UI issue)
  • Keyframes and tangents
  • Graph Editor
  • Dope Sheet
  • Animation layers
  • Time Editor
  • Playback and cached playback

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 44m
Merged PRs (30d)
59

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.