This meeting is open for anyone to come and observe. Even though the meeting is primarily meant as a forum for the members of the Rust teams, it can be hard to define the borders of a community like ours. We'd love to have people who work on major Rust libraries in the ecosystem, for example, or who work on the various Rust teams at different companies.
This meeting is meant for busy people. It's not just a bunch of random status updates. It's a carefully selected set of topics meant to spark both discussions and new ideas for how the Rust teams operate, and a place for us to coordinate on cross-cutting technical projects.
One other point: because the agenda will be circulated in advance, it may be that you pick and choose which meetings to attend based on whether this is a discussion topic that you have a lot of interest in.
To start, nikomatsakis plans to do those things. Assuming the meeting is a success, we'll figure out next steps then.
We're looking for three kinds of things:
- Status updates on projects that could affect multiple teams;
- Experience reports with insights to share;
- "Rough draft" proposals that are ready to be brought before a wider audience.
For sensitive items, this is likely not the right meeting, but you can reach out to nikomatsakis privately to discuss it.
Yes. For this to work, we need people to pay attention for an hour. We're all really busy, and asynchronous communication is all too easy to ignore.
The Rust project includes people from all over the world, and some time zones are just plain incompatible. We've put some thought into how to structure the meeting to make it accessible to folks from different time zones:
- We will alternate between different times so that folks in different time zones can more readily attend.
- We will also distribute recordings of the meeting (and perhaps consider livestreaming as well) so that people can watch.
- Per Rust's 'No new rationale' principal, we will not use the meeting to make decisions, particularly on controversial issues, but rather to generate discussion and distribute information. (See the next question.)
Per Rust's 'No new rationale' principal, we will not use the meeting to make decisions, particularly on controversial issues, but rather to generate discussion and distribute information. This means that folks who couldn't attend the meeting can watch the recordings and then participate in the follow-up discussion.
Some time back we attempted a Project Leadership Sync Meeting. The structure was basically status reports and -- after a time -- it petered out in favor of (sparsely used) Zulip streams.
This meeting has a different structure. To start, it will have more active curation of the agenda, and it will not have a "round robin" format. We'll not be looking to find out what is going on, but rather to distribute the key points of that information, and to focus conversation on interesting agenda items that merit discussion.
Further, the scope of the meeting is broader. The meeting will representatives from project groups like error handling and other key efforts of the Rust project.
The timing for the meeting is something I would like feedback on. I think it's important that we make the meeting accessible, but I also think we should take into account the time zone that the majority of participants are coming from. Here is a kind of survey of possible times and how accessible they are to folks from different time zones:
|12:00 🥰||06:00 ❌||03:00 ❌||18:00 🥱||20:00 ❌||22:00 ❌||link|
|15:00 🥰||09:00 🥰||06:00 ❌||21:00 🥱||23:00 🥰||00:00 ❌||link|
|17:00 🥰||11:00 🥰||08:00 🥰||23:00 ❌||01:00 ❌||02:00 ❌||link|
|21:00 🥱||15:00 🥰||12:00 🥰||3:00 ❌||5:00 ❌||7:00 ❌||link|
|01:00 ❌||19:00 🥱||16:00 🥰||7:00 ❌||9:00 🥰||10:00 🥰||link|
|02:00 ❌||20:00 🥱||17:00 🥰||8:00 ❌||10:00 🥰||11:00 🥰||link|
|03:00 ❌||21:00 🥱||18:00 🥱||9:00 🥰||11:00 🥰||12:00 🥰||link|
- 🥰 working hours (9:00..18:00)
- 🥱 rather late (18:00..22:00) -- which could be good for some folks!
- ❌ totally unreasonable (22:00 - 9:00)
Glad you asked! I love it too! @Xfactor521 made it! 🙏