-
Notifications
You must be signed in to change notification settings - Fork 0
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
Moving the team to fully async #20
Comments
Sounds good to me. |
I'm on board. I feel like it may help us make decisions faster, rather than waiting for everyone to be around at the right time. |
I wonder if we could get rfcbot in here to help make decisions? |
LGTM |
This sounds better. |
I'm neutral on this, but let's give it a shot. The meetings have mostly been falling apart this last month anyways. |
✅ Been very busy with non-Rust things the past couple months so I'm in favor of trying this out |
Hey all,
I've been feeling like the meetings haven't been serving the team well. We don't have a big list of RFCs to review like other teams, and a lot of the time, are sorta working on our own stuff. We do have decisions to make from time to time though.
The core team has recently changed its meeting schedule to "triage meetings" and "topical meetings". Triage is dealing with stuff that's come up, topical is like, we want to discuss a thing. That got me thinking, maybe we should try and change up the doc teams' meetings.
Instead of having a set meeting every week, what about this instead: if there's a topic we want to discuss, we make an issue on this repo and discuss it there. If we want to have a synchronous discussion on a big topic, we can set up a one-off meeting at a time that works for everyone.
Thoughts?
The text was updated successfully, but these errors were encountered: