Get off of our divergent bevy fork

Open
#189 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust
Domain
game-dev

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.

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.

Dominant language
Rust
Stars
69
Forks
14
Avg merge
15d 22h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

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 processing/libprocessing

All issues in processing/libprocessing

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.