i'm thinking that moving all of these into a fishbones repo makes sense, so that releases of these crates can happen without impacting the jumpy release, or confusing users when they see that multiple different projects are being released from the same repository.

I'm just not sure what we should call the new repo at this point.

Nothing stops us from renaming if we have to so it's not mission critical, but I wanted to get your thoughts.

There's also the question of whether the repo goes under the fishfolk organization, or if it goes under the spicylobster organization.

Let’s call it bones, in fishfolk org

Cool, sounds good.

I sent an email to the bones crate owner but no response yet.

@erlend given zicklag permissions to install bors on the github bones repository

Thank you!

There, got the scaffolding for the bones repo setup: https://github.com/fishfolk/bones

The camera shake from #1014467829682155570 has been extracted to its own crate for the bones repo pending review: https://github.com/fishfolk/bones/pull/4

Are we already locked into the v2.0.0 versioning? I haven’t heard back from the bones crate owner so we likely have to register our own thing anyhow, in which case we can start with any version.

I think bones_lib would be fitting. bracket-lib is the same.

Maybe call it fish bones so it fits better with fishfolk

fishbones was the original name and it was shortened to bones

Ah

Hey, I just ""updated"" the bones crate ``bones_camera_shake`` to bevy 0.8.0 (the current version is 0.9.0) and I do not know what I'm supposed to do. Should I make a PR to a new branch or what?

I think the sensible thing to do would be to temporarily maintain a 0.8 branch while we wait for jumpy to upgrade to bevy 0.9

Zicklag, would you agree here? If so, could you create a new branch for this? I don't have the permissions

If it's especially for jumpy, should I import the 3d features too?

3D features?

3d functions** sorry

Still unclear on what you mean

Ah, forget what I said, the last crate about shaking screen that I worked with had functions especially for 3D games and I had a little confusion about that. 😅

Ahhh I see, no worries lol

Well, while we don't have any answer, I will keep it in a fork

Jumpy@probably won’t migrate until zig can port to bones ecs

Hey @Pit ( I can't ping you for some reason 🤷‍♂️ ), I just wanted to give you a quick brain dump on how/when I think we might be able to test bones out with bomby.

( Sorry if you see weird

rc!

chats, I'm trying to figure out if this channel is still connected to discord over the bridge, I think it is. )

Anyway, right now I'm trying to get Jumpy merged and using

bones_lib

in

jumpy_core

, so that we can start using

bones_ecs

.