Session: RustBridge
Audience | team + anyone interested in rustbridge (mgattozzi said he’d be interested?) |
When | Tuesday, 11am-12am |
Where | White Smoke |
Meeting Style | Discussion |
Notes
- Website
- liv: Take down website as is, replace by placeholder
- include simple list for upcoming events
- matt: content is still relevant, don’t take it all away
- florian: who is in charge of website?
- → katharina + aaron
- bridge.community.rs should go away (redirect)
- jan-erik takes care of that
- link to rustbridge on https://www.rust-lang.org/community should change to website
- liv takes care
- How to help
- liv: rustbridge in-a-box started last year as one-stop for starting rustbridge events
- florian: integrate into foss-events-planner as “small event” use case
- liv: what do we do with people approaching us telling they want to run rustbridge
- florian: pro-actively search for teams/groups that want to run an event
- make it recurring
- aaron: TWiR
- matt: guide how to run it on website
- 2019 roadmap
- Re-do/update the website → Katharina
- Preparing resources and do outreach pro-actively (sign-up form) → Liv
- Collaborate with Women Who Code in Berlin → Berlin Org Team
- GitHub Tracking issue/meeting org → Liv
- RustBridge happening at:
- Rust Latam (March 29/30) ? → Matt
- RustConf (August 22/23) → Katharina
- RustFest (Sep-Nov) → Liv
- Rust Asia (April 20, contact: Hoverbear) ? → Katharina reaches out
- Meetings
- liv: how frequent? what format (video, text)?
- katharina: once a month (same as community team)
- michael: text, easier for people to adopt
- liv: update thread in the bug tracker for visibility/reporting
- fill in weekly updates
- florian: some kind of feedback to these weekly updates would be nice
- github reactions
- just to show that you’re not shouting into the void
Deliverables
- Consensus on our online presence
- Capacity planning
Agenda
- Intros (5 mins)
- How was 2018 for us? (20 mins)