This is an automated email from the ASF dual-hosted git repository.
stevenwu pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iceberg.git
The following commit(s) were added to refs/heads/main by this push:
new baff19fa94 Docs: Update community meetup guidelines (#14770)
baff19fa94 is described below
commit baff19fa94b562402d9119683c42585c9ac66619
Author: Danica Fine <[email protected]>
AuthorDate: Fri Dec 12 14:02:58 2025 -0800
Docs: Update community meetup guidelines (#14770)
---
site/docs/community.md | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/site/docs/community.md b/site/docs/community.md
index d8611fc6b2..3aa5a1c69e 100644
--- a/site/docs/community.md
+++ b/site/docs/community.md
@@ -88,6 +88,15 @@ Hosts are required to ensure that:
4. Planned meetups ought to be brought to the attention of the [dev
list](#mailing-lists)
5. All [Community Guidelines](#community-guidelines) must be respected
+Meetups *must* be small events under the [ASF branding
guidelines](https://www.apache.org/foundation/marks/events.html#dates) and are
typically small, informal gatherings. If you're unsure whether an event is a
meetup, meetups usually:
+
+* Rely on a curated selection of talks, where organizers work with the
community to include a diverse representation of speakers, topics, and
companies. Due to the small number of submissions, meetups might use, but don't
require, a CfP.
+* Are single-tracked and accommodate only a handful of sessions.
+* Have at most 2-3 hours of content, plus networking time.
+* Are sponsored by 1-3 companies providing food, drinks, or meeting space; not
by selling booth space or marketing opportunities. They don't require
substantial financial support.
+
+If you don't know whether an event qualifies as a meetup, please ask the PMC
through the private mailing list! (Be sure to do this *before* using the Apache
Iceberg brand or trademark.)
+
## Community Guidelines
### Apache Iceberg Community Guidelines
