-
Notifications
You must be signed in to change notification settings - Fork 298
Add an update from the Rust Leadership Council #1123
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
Conversation
I've left a few comments that would be nice to address, but I'm also would be happy with the post as is so I've given my ✅. |
I can't tick my box but, modulo some comments which I agree we should address, this looks good to me. |
I can't tick the box from here either. |
@carols10cents @jonathanpallant you should have the ability to ✅ now |
I believe I've addressed all the comments in some manner. Thank you all for the great comments! |
@rylev mentioned on Zulip that this post might be better on Inside Rust. That makes sense to me as well. I'm tempted to push a commit here that does that, but a lot of us have consented already and I'm not sure whether that's a substantive enough change that we should clear everyone's checkboxes? |
I'm happy with recategorizing. |
@eholk I think we should move to the Inside Rust blog. We've had no concerns from @Mark-Simulacrum, @carols10cents, and myself. If someone has a concern, this is easily reversible even after we merge. |
Done! |
This is ready to merge. Just need to merge rust-lang/leadership-council#18 first. |
It's been about a month since our last leadership council post. In the interest of communicating proactively and publicly, it's time to post an update on what we've been up to.
I set the date for Monday, July 24, but we can move this earlier if everyone consents first.
This should get consent from all members of @rust-lang/leadership-council. Please check your box below when you're happy with the post.
Checkboxes: