I don't think I'll have much time to contribute to help, but I would
absolutely help if possible.

That said, I'll definitely want to give a talk / speak at this summit when
it happens :)

On Mon, Aug 21, 2023 at 1:38 AM Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:

> Hi guys,
>
> I'm back from vacation and I'm resuming the work on the Iceberg Summit
> proposal doc. I will share the doc asap.
>
> Regards
> JB
>
> On Wed, Jul 5, 2023 at 4:37 PM Jean-Baptiste Onofré <j...@nanthrax.net>
> wrote:
> >
> > Hi everyone,
> >
> > I started a discussion on the private mailing list, and, as there are
> > no objections from the PMC members, I'm moving the thread to the dev
> > mailing list.
> >
> > I propose to organize the first Apache Iceberg Summit \o/
> >
> > For the format, I think the best option is a virtual event with a mix of:
> > 1. Dev community talks: architecture, roadmap, features, use in
> "products", ...
> > 2. User community talks: companies could present their use cases, best
> > practices, ...
> >
> > In terms of organization:
> > 1. no objection so far from the PMC members to use Apache Iceberg
> > Summit name. If it works for everyone, I will send a message to the
> > Apache Publicity & Marketing to get their OK for the event.
> >  2. create two committees:
> >   2.1. the Sponsoring Committee gathering companies/organizations
> > wanting to sponsor the event
> >   2.2. the Program Committee gathers folks from the Iceberg community
> > (PMC/committers/contributors) to select talks.
> >
> > My company (Dremio) will “host” the event - i.e., provide funding, a
> > conference platform, sponsor logistics, speaker training, slide
> > design, etc..
> >
> > In terms of dates, as CommunityOverCode Con NA will be in October, I
> > think January 2024 would work: it gives us time to organize smoothly,
> > promote the event, and not in a rush.
> >
> > I propose:
> > 1. to create the #summit channel on Iceberg Slack.
> > 2. I will share a preparation document with a plan proposal.
> >
> > Thoughts ?
> >
> > Regards
> > JB
>

Reply via email to