In today’s Community Team meeting, we talked about how conferences should work for the officially sanctioned
RustConf conferences. While everyone agrees we’d love to have official conferences around the world (like every month or so), the core team has limited time and budget to organize multiple expensive events globally. This has resulted in this year’s official conference being organized in the US, which leaves out a large amount of our international community from attending.
One option we talked about is the possibility of more of a franchise model with these conferences in order to not have their organization bottlenecked on the core team’s availability. The Rust Legal Policies suggest that there is a process to get permission to use these reserved names, but we haven’t defined what this process is and what requirements would be imposed to use them. This unfortunately means that people like @skade who are ready and able to organize one of these events, but are unable to because there’s no process for him to follow.
So let’s start figuring out what our process should be. This thread hopefully will lead to a proper RFC that we can propose to the broader community so we can get rid of this ambiguity.
To start things out, @aturon said the core team has some initial requests for anyone using these conference names:
- A consistent experience across all the officially branded conferences.
- An equivalent level of quality.
- Being on message
- Control over the keynote
- Consistent media and branding over the look of the conference
How should we meet these, and any future requirements? @skade and @carols10cents pointed us to some conferences that use a franchising model, like JSConf and Devopsdays. Perhaps we can use that to help frame our approach.
- What does being on message mean to you? I assume some basic rules are that the conference must actually be a general conference about Rust, and that the conference needs to follow the Rust Code of Conduct. Are there more requirements?
- Does control over the keynote mean that the core team picks the keynote speaker, or just has veto over the speaker?
- Does the core team own the imagery that are used at past and future conferences, and will they be usable by the franchisee?