Having more developers understand, use and evangelize this language will advance make the web better and more secure. Rust is also a great way to learn about WebAssembly.
Rust is a systems programming language that runs blazingly fast, prevents segfaults, and guarantees thread safety. Find out more…
For duration, we recommend at least a 2-3 hours event with a minimum of 10 attendees.
- Put an event team together. Going alone is fine, but at least two people is advisable. Check the Rust Community Calendar - maybe there’s already people in your area. You can also get in touch with the Rust Community Team for additional support.
- Try to find people with Rust experience who want to help. If you find none, this is fine - many Hack and Learns started out by curious people.
Some Mozillians have already done such sessions. For example see past Mozilla Reps events.
2-4 Weeks Before the Event
- Read the event guide on how to set up an event page and how to organize an event.
- Choose a date and secure a venue.
- Fill the event template for access to the calendar so that you can enter it there. It will then be sent around with Rust’s weekly newsletter and promoted in other fashions. You can also ask the Rust Community Team if they can send some stickers.
- Setup the event on the Reps Portal (instructions). Please make sure the initiative is set to “MozActivate” and the functional area indicates “Rust”.
1 Week Before the Event
- Get Material and print them to hand them out.
- Promote your event locally and online.
Hack & Learn are mainly structureless, which allows for people of all experience levels to feel great. They can follow their interests and can interact with people. As an organiser, you can try to also bring your own project, please note that you will the first point of contact for problems.
- Give people some time to get in and wait 5-10 minutes to get them set up and comfortable
- Do an intro round (5 minutes). Ask everyone for:
- Who they are
- What previous programming experiences they have
- What they intend to work on (or if they are searching for a project)
- Encourage people to group up or work alone
- Introduce new people to the existing resources
- Help people that don’t have a project to find one
- Open time: people should just work on whatever they have. Some people will just chat, make sure they don’t disturb others.
- Closing: go through the group again and ask people for their progress.
- If time allows, make a Show & Tell and have people actually present their learnings in a very short talk.
- If this is the first time you run it: ask people about their schedules and try to find a regular date for repeats.
If the event is just 2 hours long, keep the intro and the closing short. If you spend 2.5 hours or more, you can spend more time on the closing. If the event is even longer, consider running something by the middle of it, to give people a moment to step away from the project.
Directly at the end of the activity
Immediately after the event don’t forget to share the link to the impact form with your attendees:
Remember this is how you’ll know who attended your event, and if you successfully inspired them to action! We recommend adding it to your final slide AND emailing it out after the event.
Learn by Example
Coming from other programming languages
In addition to the recommended event flow here are some things we’d like you, the event organizer, to do:
- Fill out the post-event metrics on the event page you setup on the Reps portal
- Share your own experience on social media and encourage your attendees to do so as well:
While the focus of this activity should be on these events, people can get more involved with the Rust community after.
- Follow up with attendees to highlight more things happening in the community to get involved with