Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add speaker guidelines for meetups to Druid #505

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions src/pages/community/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -25,8 +25,7 @@ Also check out:
* **User mailing list:** [druid-user@googlegroups.com](https://groups.google.com/forum/#!forum/druid-user) for general
discussion, questions, and announcements.
* **LinkedIn** Connect with other Apache Druid professionals in the [LinkedIn group](https://www.linkedin.com/groups/8791983/).
* **Meetups:** Check out [Apache Druid on meetup.com](https://www.meetup.com/topics/apache-druid/) for links to regular
meetups in cities all over the world.
* **Meetups:** Druid Meetups can be found all over the world, to find out more about Druid Meetups and to find your local one see [Druid Meetups](/community/meetups).
hevansDev marked this conversation as resolved.
Show resolved Hide resolved
* **StackOverflow:** While the user mailing list is the primary resource for asking questions, if you prefer
StackOverflow, make sure to tag your question with `druid` or `apache-druid`.
* **Linen:** Check out the [Apache Druid community on Linen](https://www.linen.dev/s/apache-druid/c/troubleshooting) for a digital archive of Apache Druid Slack threads.
Expand Down
28 changes: 28 additions & 0 deletions src/pages/community/meetups.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
---
title: Druid Community Meetups
layout: simple_page
canonical: 'https://druid.apache.org/community/meetups'
---

## Druid Community Meetups

Check out [Apache Druid on meetup.com](https://www.meetup.com/topics/apache-druid/) for links to meetups in cities all over the world.

All Apache Druid Meetups subject to the Apache [anti-harassment policy](https://www.apache.org/foundation/marks/events#anti-harassment) and speakers are expected to follow the guidelines below.

### Speaker Guidelines

**Skip the Sales Pitch:** Keep your talk unbiased and educational. It’s okay to mention commercial products you’re using, but only if they are a key part of your data architecture and Apache Druid or if what you are demonstrating can be accomplished with a free or free tier version of the commercial product or service. Content which is solely focused on promotion of a product or service is never permitted at an Apache Druid Meetup.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**Skip the Sales Pitch:** Keep your talk unbiased and educational. It’s okay to mention commercial products you’re using, but only if they are a key part of your data architecture and Apache Druid or if what you are demonstrating can be accomplished with a free or free tier version of the commercial product or service. Content which is solely focused on promotion of a product or service is never permitted at an Apache Druid Meetup.
**Skip the Sales Pitch:** Keep your talk unbiased and educational. It’s okay to mention commercial products you’re using only when they are a key part of your data architecture with Apache Druid, or your demonstration can work with a free or free tier version of the commercial product or service. Content which is solely focused on promotion of a product or service is never permitted at an Apache Druid Meetup.

Run on sentence


**Share Challenges:** Feel good about sharing roadblocks you hit and how you worked around them – or ones you might still be struggling with – there may be a community member in the audience who can help you out! Engineering always involves trade-offs, so being realistic about them helps establish you as a credible advisor.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could add some example topics? Like

  • Making contributions (docs, code)
  • Tutorials - things people can do on their own, whether it's for real or just experimentation, complete with re-usable code.
  • Coaching - like tips and tricks, guidance on how to use features, and lessons learned.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**Share Challenges:** Feel good about sharing roadblocks you hit and how you worked around them – or ones you might still be struggling with – there may be a community member in the audience who can help you out! Engineering always involves trade-offs, so being realistic about them helps establish you as a credible advisor.
**Share Challenges:** Feel good about sharing roadblocks you hit and how you worked around them – or ones you might still be struggling with. There may be a community member in the audience who can help you out! Engineering always involves trade-offs, so acknowledging your challenges helps establish you as a credible advisor.

Run on sentence.


**Focus on the Technical:** This audience understands and has built data architectures – if you get it, they’ll get it. Of course, start with the basics of who you are, what you built, and why before going all-in on the technical insights, examples, and demos.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**Focus on the Technical:** This audience understands and has built data architectures – if you get it, they’ll get it. Of course, start with the basics of who you are, what you built, and why before going all-in on the technical insights, examples, and demos.
**Focus on the Technical:** This audience understands and has built data architectures. If you get it, they’ll get it. Of course, start with the basics of who you are, what you built, and why. Then go all-in on the technical insights, examples, and demos.


**Keep an open mind:** The Apache Druid project has [a vendor neutrality policy](https://community.apache.org/projectIndependence#:~:text=Apache%20projects%20are%20managed%20independently) because it is important to keep an open mind about approaches and not only share one product or solution when many are available. A community that obviously favors one specific vendor in some exclusive way will often discourage new contributors from competing vendors, and this would be an issue for the long-term health of the project.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**Keep an open mind:** The Apache Druid project has [a vendor neutrality policy](https://community.apache.org/projectIndependence#:~:text=Apache%20projects%20are%20managed%20independently) because it is important to keep an open mind about approaches and not only share one product or solution when many are available. A community that obviously favors one specific vendor in some exclusive way will often discourage new contributors from competing vendors, and this would be an issue for the long-term health of the project.
**Keep an open mind:** The Apache Druid project has [a vendor neutrality policy](https://community.apache.org/projectIndependence#:~:text=Apache%20projects%20are%20managed%20independently) because it is important to keep an open mind about different ways to solve problems. A community that obviously favors one specific vendor in some exclusive may discourage new contributors from competing vendors, potentially impacting the long-term health of the project.


**Show and Tell:** If you can, prepare a short demo to accompany your presentation to showcase your work. This will help put everything in context for your fellow developers and the more visual learners in the audience.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**Show and Tell:** If you can, prepare a short demo to accompany your presentation to showcase your work. This will help put everything in context for your fellow developers and the more visual learners in the audience.
**Show and Tell:** If you can, prepare a short demo to accompany your presentation to showcase your work. This add context for your fellow developers and the more visual learners in the audience.


**Watch the Clock:** If you run over, then the next will, and so on, until we’re either completely off schedule or someone else’s talk gets cut short! Practice your presentation ahead of time to make sure you stay within your allotted time.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**Watch the Clock:** If you run over, then the next will, and so on, until we’re either completely off schedule or someone else’s talk gets cut short! Practice your presentation ahead of time to make sure you stay within your allotted time.
**Watch the Clock:** If you run over, then the next will, and so on. Eventually the Meetup is completely off schedule , meaning someone's talk may be cut short! Practice your presentation ahead of time to make sure you stay within your allotted time.


Need help with your a talk on Druid or have questions about Druid Meetups? Please reach out at [community@imply.io](mailto:community@imply.io).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull this and replace with a new channel in Druid Slack - what do you think @reenadotio @techdocsmith @abhishekagarwal87 ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you can just add the Apache Druid slack channel. Or a link to where we tell people to sign up. We don't want to manage the invite code in multiple places IMO.