processing / processing/libprocessing
Get off of our divergent bevy fork
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 69
- Forks
- 14
- Avg merge
- 15d 22h
- Merged PRs (30d)
- 3
Description
Our particle solution is currently enabled by this work that has yet to be merged back into bevy: https://github.com/processing/bevy
We need to merge this or find a way to have this functionality without maintaining a fork ideally. We are here because we wanted to prove the functionality, but we want to move towards stability and removing this is a necessary step.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by tracing how libprocessing currently depends on the divergent processing/bevy fork and where the particle functionality is integrated. Compare that functionality with the upstream Bevy project and determine whether it can be merged or replaced without the fork. Done means retaining the particle behavior while removing the need to maintain the divergent fork.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- game-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100