Project needing maintainers

[makspll]

Bevy scripting needs you!

So far I am the only committed maintainer of this crate. This has worked very well when I didn't have any other major responsibilities, but since getting a full time job, I've been struggling to keep the updates coming.

Do not be scared, I am not pausing development or anything of the sort, I will eventually be able to fall back into the rhythm and keep improving the crate. In fact I am looking forward to a big re-write when dynamic systems are possible in Bevy!

Having additional maintainers would mean a much more predictable release cycle, and at the very least keeping up with the Bevy train on time.

Scope

At the beginning, this library was just a single crate, and everything was simple. Then the scope increased, and suddenly I was supporting an ever changing bevy scripting API, which is still unfinished, as well as keeping up with a multitude of tools including tealr, teal, rhai etc..

The library reached the point where coming back to it after long breaks means re-discovering all the design choices I have made. This means that new people joining the project wouldn't be far behind me in understanding everything ;)

At the very least I am looking for a dedicated person able to commit to keeping this crate updated whenever Bevy changes (which usually isn't that much work), so I can focus on improving the library. Ideally we'd have more people, a subject matter expert for every language we support, and maybe some people dedicated to other bits and bobs (like docs, optimisation etc..). I am aware this might be a bit much considering the library isn't that popular, but one can hope :)

Contact

If you're at all interested in using this crate, and would like to contribute, reach out to me over at [email protected], nothing formal, just tell me about yourself, how you use this library and/or how/to what extent you'd like to help out! Alternatively use this google form: https://forms.gle/vTQnrj2nf8e4n97F9 if that's more your speed!

Thanks

I'd also love to thank everybody who helped out in the past again (in no particular order)!

Code contributions:

• @opfromthestart
• @a-soulspark
• @katk0smos
• @awestlake87

Issue contributions (yes these matter too!):

• @a1393323447
• @apriori
• @themaxhero
• @Semihazah
• @schungx
• @ChrisPWill
• @coderedart
• @Lightnet
• @chrisburnor
• @darthdeus
• @ValorZard

Every issue, line of code, and piece of grammar checking helps!