Rename to bevy_warbler_grass?

[morgenthum]

Hey! It’s usually a convention to name Bevy plugins using the “bevy_*” pattern. What do you think about renaming it?

Edit: Very cool plugin btw, ty 👍🏼

[EmiOnGit]

Hey mate, thanks for the comment. Feedback is highly appreciated :).

The crate was actually already renamed from warblersneeds at some point in time. Some parts of the discussion can be read here but I believe a large chunk of the discussion was in the bevy discord directly. bevy_grass was declined by the bevy team because it sounds to official and may collide with a official grass implementation in the future (in a couple of years)

We decided against bevy_warbler because we thought warbler_grass just sounded cooler. I also still think it sounds a bit better and bevy_warbler_grass is too long for a crate name.

I also think that the convention is also often used to indicate that the crate is an integration of another project into bevy, such as bevy_rapier bevy_egui bevy_iced and optional for bevy-only crates such as pixelated_mesh big-brain bevior_tree seldom_state

Edit: After taking a look over the asset page I do have to agree, that the vast majority does follow the bevy_* convention. I'm open to renaming, but only if a majority agrees that this is a good change. After all, renaming does break all dependency chains and shouldn't happen lightly.

Feel free to react to the comment with: :heart: to keep warbler_grass :+1: to rename to bevy_warbler_grass :tada: to rename to bevy_warbler