jumpy
jumpy copied to clipboard
fishfolk
Development Tracks
Now that we have all our essential items queued up, we need to map out the other “main tracks” of development we wanna kick off next. Item dev will always be an available track because there’s an infinite number of items (-variations) to be made.
Tracks
- https://github.com/fishfight/FishFight/issues/160 (lead: @zicklag )
- #129 (lead: @zicklag )
- https://github.com/fishfight/FishFight/issues/120 (lead: @legendiguess )
- #230 (leads: @cdsupina, @tigleym )
- #43 (lead: @Zac8668 )
- #272 (lead: @jamie-null )
- Builds #127 #128 (lead: @orhun )
- General Physics, e.g. https://github.com/fishfight/FishFight/issues/30
🎨 👉 We also need main tracks for pixel-art, sounds, level design etc., but we’ll return to those in a few weeks, once the coding tracks are in progress.
🚧 Under Construction: ( edit by @zicklag ) With bevy rewrite, a lot of things have been moved around and we are still getting things stabilized. We're in the middle of documenting and re-organizing so these development tracks may not be 100% accurate at the moment. Feel free to comment, open a discussion, or hop on the Discord if you have questions on how you can contribute!
A few other potentially low/medium priority tracks might be:
- Continuous Integration (e.g. build for different architectures)
- Continuous Deployment (e.g. automate GitHub releases)
- Packaging (e.g. there is fishfight package in the AUR)
I guess you can put these together under "chores". Maybe I can create tracking issues if they are fine.
Just giving my 2 cents.
You’re welcome to create tracking issues for these 👍
I’d consider them all part of an overarching ‘Builds’ track.
@erlend-sh do you think this issue should be updated or maybe closed in favor of new tracking issues?
