-
Notifications
You must be signed in to change notification settings - Fork 117
rlua is now part of the Amethyst organisation #174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'm not really involved with or use this project any more, there's no need for me to have triage access. |
Thanks! I need to enable two-factor authentication before joining - any recommendations for Android apps? |
I just use the Google Authenticator app, but GitHub makes some other recommendations here: |
I'm happy to know rlua is potentially going to have more attention! I appreciate previous constributors have been given some access to assist the repository, including me with my single pull request. This is surprising to not say the least! Currently, I'm not doing much contributions to open source projects. However, I'm considering the use of rlua for a project, where Hope to see support for the upcoming Lua 5.4 runtime! |
That's great news. Seeing such good updates will help keep Rust gaming community pumping :) |
This has been fairly quiet, and there are some new (and a few old) PRs with not much response. So, @rustysec @Grokmoo @khvzak (or anyone else) - do you still want to be involved? If so I think we should agree on how decisions are made. If not (or if I don't get any reply in the next week or two) then I'll start accepting and/or making changes as I see fit, taking into account how I think @kyren might like things to go. I still don't have the time to do this full time, but I'm happy to do light maintenance - approving/merging PRs which look good to me and occasionally looking into things myself as I need to/find time for - but with no guarantee I'd get around to much! |
I was actually looking at some PRs last week but just didn't have time to give them any kind of thorough review. I'd like to help the project any way I can, but I'm in a similar situation (not having as much time as I'd like). |
In that case can I suggest this informal process?
This means:
|
I think this can be closed now. |
Uh oh!
There was an error while loading. Please reload this page.
rlua
is now part of the Amethyst organisation! 🎉 We will be co-maintaining this project together with @kyren and whoever else wants to become involved. 🤝How did this happen?
I've been chatting asynchronously with @kyren for the past two weeks regarding #172.
Her ask boils down to what is also a very generous offer:
This is exactly the sort of overhead the Amethyst org can cheaply absorb into our existing processes and structures. In the less abstract: For now we'll just take care of granting the necessary GitHub privileges to any willing contributors. There are a handful of active
rlua
users with a real stake in its continued maintenance and even betterment. Amethyst org will help facilitate the onboarding of the people who raise their hand up to help.Handing out access
All repeat-contributors have been granted Triage access: @lemarcuspoilus, @Timidger, @jonas-schievink, @Shiroy. @azdle already has Write access.
@rustysec, @jugglerchris and @Grokmoo have all expressed an interest in co-maintaining, so you've all been set up with Maintain access. You aren't committed to anything, but it should be easy for you to take action if you find an opportunity to do so. 🦸
@khvzak also has Maintain access. Whether or not we are able to find a way to directly collaborate,
rlua
andmlua
have way more in common than not; cross-pollination is encouraged. 🐝Feel free to ask org-related questions here, or join the Amethyst #scripting channel on Discord: https://discord.gg/KqkvQsC
The text was updated successfully, but these errors were encountered: