No matter how you stumbled upon this project, this little page exists to guide you in the right direction. There's a bit more information depending on what you're interested in:

Great! Unfortunately we currently lack a centralized directory of all RustBridge events happening around the globe (although that would be really nice to have), so for now your best bet is to have a look at the issues tagged with event, that's generally where all events that run under the RustBridge name are tracked, but it's not always reliable.

Oh, fantastic! We've prepared a document just for you, you can have a look at it here.

First of all: Welcome to the RustBridge team! We have a very flat hierarchy, and any person that's interested in organizing is very welcome in our ranks.

That being said, organizing a RustBridge event is much simpler than you might think. What makes RustBridge events RustBridge events can be boiled down to three points:

• The event has to be free
• The event has to be targeted towards underrepresented minorities in Tech
• The event has to follow the Rust Code of Conduct

But apart from that, you can use any venue, use any curriculum, with as many people as you want! Although we also provide materials specifically for people who have never organized a RustBridge event before, so maybe you'd want to check those out...

With organizing any event, it's usually good to have an overview of what you want to accomplish before setting out to do the first steps. That means that you should be clear where, (roughly) when and with who you want to organize your event. It's usually better if you have an organizing/teaching team of at least two, or more depending on the size of your audience. Also if you have a rough date and a potential venue, it might be good to give them a call before doing anything concrete.

First things first, settle on a date. This can be during the work week, but keep in mind that it's usually an all-day event, so people's capabilities might be limited. Make sure that nothing else is happening at your chosen date (like a world cup finale in your city, for example).

After that, probably the most important step is to secure a venue for your date. Try asking around, be it on Twitter, at meetups, or in other local circles. If you live in a bigger city, there's usually some companies who would be happy to sponsor the venue for your event.

Phew, that's the two most important things done! Now's probably the point at which you should post your meetup in our GitHub issue tracker. If you want to, or if you're unsure about anything, you can contact us privately before. Once you're ready, post a new issue in the rustbridge/team GitHub repository. It doesn't have to be an incredibly detailed issue, it just needs the time and the name of an organizer (maybe you?). A venue is also recommended, but if you don't have one at this stage, we have ways to help you with that.

Because RustBridge events are aimed towards underrepresented minorities, you might want to consider not making it a "everyone can come without registration" type of event. Not only does it make some people feel unwell, but we've had cases in the past where events got interrupted by third parties with bad intent. For that same reason, consider not making the venue location public, especially if it's a publicly accessable venue.

In the past, we've usually used a simple Google Forms form for signups to RustBridge events. This works fairly well, especially if your event is small to medium-scale. If you need or want more information/help regarding these processes, don't hesitate to contact us!

If you want to spread the word about your event, we can definitely help you with that. We have multiple channels over which we can announce your event, so feel free to talk to us regarding that.

Getting nervous yet? Good, everyone does! Here's a couple of things that you might want to consider as your event draws closer:

• Catering. People probably want lunch, so if the venue offers catering, great! If not, no worries, you can always just tell the group to go and organize lunch on their own.
• Drinks. Some venues have a fridge with drinks, if not, you might just want to get some water and plastic cups from the local supermarket.

On the day of the event, make sure you're at the venue early so you can get everything set up. Having multiple teachers/mentors is recommended, but depends on the size of your group. Set yourself a schedule that you'll follow during the day, and be careful to meet the deadlines imposed by your venue. Other than that, have a great time!

It's unlikely that this document will ever reflect everything that goes into a RustBridge event, so if you have questions, we'll do our best to help you out.

If you need help from the RustBridge team, we're on the RustBridge Slack, in the #rustbridge Mozilla IRC channel, in the #rustbridge Rust Discord channel, as well as on GitHub. In doubt, just open a new issue on rustbridge/team.

If you need help regarding spreading the word, finding a venue, or finding other interested people in your area, the Community Team can probably help you with that. They're on the #rust-community Mozilla IRC channel, as well as at community@rust-lang.org via email.

The RustBridge team is comprised of individuals who whost RustBridge events, work on tooling for RustBridge, and people who are just interested in improving existing conditions under which events are organized.

The team is formally a sub-team of the Rust Community Team, and the current team lead is Olivia Hugger. This means that RustBridge is fully integrated into the Rust project, which brings with it many benefits such as cross-cutting team concerns and easier internal communication.

RustBridge team meetings are nominally held every 2 weeks (alternating with the Community Team meetings), at 5:00 PM UTC. A timezone-aware overview of the next meeting time can be found here.

Meetings happen over video and audio, using meet.jit.si. Our meeting room is here.

Every meeting has an agenda which is documented as a GitHub issue in the rustbridge/team repository. You can browse past meeting agendas here.

Meetings are also sometimes discussed in our Discord channel. If you want to start attending our meetings, that's the best place to ask!

The main open discussion space for the RustBridge project is in the Rust project Discord server. Discord is a chat platform that's easy to use and available on most platforms. You can join the Discord server of the Rust project by visiting this link.

RustBridge has a channel called #rustbridge, which is categorized under the "Community" section. If you use the Ctrl/Cmd+K shortcut and search for RustBridge, you will find it. Feel free to ask questions and hang out!

Internally, most RustBridge events are centrally planned using Airtable. This gives us overview and flexibility over which events are happening where. These sheets are not available to the public, as they contain potentially private information. They're only visible to RustBridge team members and select event organizers and teachers.

RustBridge uses GitHub to manage and publicly plan events, as well as develop infrastructure around the project. Here's some interesting repositories:

• team: This is where the team plans meetings and publicly announces RustBridge events.
• in-a-box: A somewhat complete resource for RustBridge event organizers needing a curriculum, funding advice, et cetera.
• book: The source to this book!