​​Integrating RustConf Meeting
​​Feel free to pass around to anyone interested
​​
​​Link: https://3tRv.mozilla.com/flex.html?roomdirect.html&key=3G7mbrBFBf
​​
​​Facilitator: Florian 
​​Attendees: aturon, jan-erik, mgattozzi, skade
​​
​​Agenda (Feel free to add things):
  • ​​Intro Florian (2 min)
  • ​​First steps (3min)
  • ​​Meeting time/cadence
  • ​​Aligning on meeting spot
  • ​​Alignment of goals (10min)
  • ​​What do we feel are good things for common standards?
  • ​​What do we feel are good things for collaboration/pooling?
  • ​​Things that should be explicitly left out?
  • ​​Picking first goals (10min)
  • ​​Setting _one big_ goal for 2019
  • ​​Identifying smaller things to work on

​​Notes

  • ​​All prior issues with RustConf have been addressed in one way or another — so here  we want to be forward-looking
  • ​​Events meeting is currently:
  • ​​Wed 8pm in Berlin (noon on West Coast, 3pm on East Coast)
  • ​​bi-weekly
  • ​​on Telegram
  • ​​Events team orientation
  • ​​Want to support a variety of events, not force everyone in the same mold
  • ​​However, want to provide some common standards across events
  • ​​Common standards + best practices:
  • ​​CoC
  • ​​What are the precise requirements?
  • ​​Accessibility and related
  • ​​Diversity of presenters
  • ​​For RustConf 2018:
  • ​​Program committee did initial voting while blinded
  • ​​Second stage: deciding on some definite talks, and categories
  • ​​After: unblind, judge for presenter expertise and diversity
  • ​​(we used invitations in stage 3 as well, though we came up with invite ideas beforehand, mostly)
  • ​​Can provide incentives to go beyond common standards (see Ruby Central)
  • ​​e.g. continued support contingent on improvements
  • ​​Thing to not standardize
  • ​​Overall format
  • ​​Collaboration + pooling
  • ​​CFP app — provide setup for new events
  • ​​Q&A
  • ​​Mentoring
  • ​​Best practices
  • ​​Post mortems