Project Metamorphosis: Unveiling the next-gen event streaming platformLearn More

Confluent Community Meetups Rules of engagement

In order to ensure that everyone benefits from the meetup events we put on, we have a strict set of rules we impose on ourselves. In this document, we have included some RoE for speakers and hosts.

In order to ensure that everyone benefits from the meetup events we put on, we have a strict set of rules we impose on ourselves. In this document, we have included some RoE for speakers and hosts.

These rules are group-specific and this list is not an exhaustive explanation of how someone should behave as a host, speaker, organizer or attendee at a meetup! For this, we have a Code of Conduct that you can find here

Speakers

If you are interested in being a speaker at any of our community events around the world, please fill in the form within this link!

Don’t give a sales pitch

It’s hard to provide a closed-form definition of what a “sales pitch” is, but here are some guidelines for avoiding them:
  • It’s okay to mention commercial products, but only as a companion to something people can use or try for free. The core message of the talk should be achievable with the free version
  • Be willing to discuss shortcomings in your solution and other options besides the one you present. Engineering always involves trade-offs, so being realistic about them helps establish you as a credible advisor.
  • You are always trying to persuade the audience that a particular solution is a good one, so don’t be afraid to persuade—just do it as an educator, not as a partner in a commercial trading relationship.

All content must be vendor-neutral

We are here to learn about Apache Kafka and its ecosystem. Some parts of that ecosystem have commercial vendors behind them, and that is a good thing. However, you are there to equip developers with the tools they need to succeed, not advance the commercial interests of your employer. Don’t turn your talk into a vendor pitch.

All content must be vendor-neutral

We are here to learn about Apache Kafka and its ecosystem. Some parts of that ecosystem have commercial vendors behind them, and that is a good thing. However, you are there to equip developers with the tools they need to succeed, not advance the commercial interests of your employer. Don’t turn your talk into a vendor pitch.

This is an Apache Kafka® talk

This is a Kafka meetup which will be attended by people who are interested in learning about Kafka and engaging with the Kafka community. Make sure your talk is about Kafka or intimately related companion technology.
You may talk about other technologies, but only if they closely relate to and are interdependent with Kafka. From Confluent’s side, this will include parts of our ecosystem intertwined with Kafka, like Confluent Cloud or ksqlDB. The content surrounding them will be 100% technical, such that a developer in attendance may learn how to build something with the technology.

The talk is 100% technical

This summarizes every point made above and below. We want you to be technical! This is one of the only offline platforms where people can go to hear about Apache Kafka as a technology, and not just a business tool.

Let your technology do the talking (Demonstrate!)

Of course, we’re all here for a reason, but ultimately, we maximise our benefits from meetups by respecting the format and the community. People will like your stuff if you demonstrate it and if it’s good, rather than you just telling them it’s good.

Stick to your timeslot

If you run over time, you’re basically saying your time is more important than the next speaker or the organizer’s time. It is not. :)

Disagree? If you believe that any of these rules do not necessarily support our goal of serving the Apache Kafka community, feel free to reach out to your direct community contact in the group or community@confluent.io

Hosts

Introducing the speakers

As a host, you may have a quick opening line to introduce the event and speakers. This must be no more than a minute or two.
Feel free to say ‘welcome to [company/venue]’, introduce the talks and speakers and give any essential information to your attendees, such as telling them to throw stuff in bins, or where the fire exits are, etc.

Collection of information (attendees and registrants to meetup.com)

You must not collect any personal information from attendees unless:
  • This information is for security reasons and that you have stated this and you have asked your group owner prior to this.
  • The specific person has implicitly given you their information, and are fully aware if you intend to contact them with this information and you have asked your group owner prior to this.
If you do have their contact details for any of the reasons listed above, please make sure each person has agreed for you to contact them beforehand.

Recruitment and Sales

Hosts are often hosts in order to attract many Kafka users to their offices/facilities. This is not a problem and we hope that you can gain a healthy benefit from hosting one of our events.
Please, however, bear in mind, that all recruitment practice must be done to people who want to be hired. The strategy you follow will be an out-to-in strategy: lay some hiring brochures near the swag, place a banner listing your job openings, put identifiable t-shirts on your recruiting staff, but please don’t try to ‘ambush’ community members, it won’t reflect on you very well.
Also, please bear in mind, if you do want to communicate job vacancies (which are specifically related to Kafka), feel free to post them on our meetup groups’ discussion boards (scroll down the main page of the meetup you want to contact and you’ll find it!)

Contacting members afterwards

Never do it, unless you have direct expressed permission from that specific person.
Disagree? If you believe that any of these rules do not necessarily support our goal of serving the Kafka community, feel free to reach out to your direct community contact in the group or community@confluent.io