Hi Ryan

Yes I will update the proposal to address the concerns.

Thanks
Regards
JB

Le mer. 27 sept. 2023 à 23:11, Ryan Blue <b...@tabular.io> a écrit :

> JB,
>
> I think we're agreed that it would be great to promote the project and put
> together talks to help expand the community. What isn't clear is how to
> make this happen. Are you planning on updating the proposal to address the
> concerns I raised or do you want someone else to pick that up?
>
> Ryan
>
> On Tue, Sep 26, 2023 at 11:28 PM Jean-Baptiste Onofré <j...@nanthrax.net>
> wrote:
>
>> I mean that anyone interested can add it to the doc.
>> I think we have different motivation and ideas. It’s great to share all
>> together.
>> Personally, my motivation is to promote the project (because it’s super
>> interesting) and connect dots with other Apache projects. I also think it’s
>> good timing to grow/expand our community.
>> I will also work on the document thanks to your comment, as anyone can do
>> :)
>>
>> Regards
>> JB
>>
>> Le mer. 27 sept. 2023 à 00:47, Ryan Blue <b...@tabular.io> a écrit :
>>
>>> JB,
>>>
>>> What do you mean --- are you going to put together the proposal for how
>>> this would work? Or are you saying that anyone interested in that topic
>>> could add it to the doc?
>>>
>>> Ryan
>>>
>>> On Tue, Sep 26, 2023 at 12:26 PM Jean-Baptiste Onofré <j...@nanthrax.net>
>>> wrote:
>>>
>>>> Hi Ryan,
>>>>
>>>> My bad: I understood in the previous discussion about the summit that
>>>> we wanted something more concrete in terms of format, length,
>>>> organisation, how we can set this up.
>>>>
>>>> Of course, no problem to take a step back, and the document is
>>>> definitely where we can work all together. I'm also in the same
>>>> situation as you: I'm helping using my Apache/community hat, but I
>>>> included proposals from my company (Dremio) in the doc. For instance,
>>>> I think it's important to "split" committees for sponsoring and track
>>>> content, just to avoid "sales talk" as it's a community event.
>>>> As few of us helped on summits in the past, experience and how it went
>>>> are valuable.
>>>>
>>>> Special thank to you, Brian and Ed about the comments.
>>>>
>>>> I propose to work on the doc: anyone from the community can edit the
>>>> doc.
>>>>
>>>> Thanks,
>>>> Regards
>>>> JB
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, Sep 22, 2023 at 8:18 PM Ryan Blue <b...@tabular.io> wrote:
>>>> >
>>>> > To me, this proposal is getting a bit ahead of where I'm comfortable.
>>>> I was expecting this to address some of the big questions about how to run
>>>> an event like this from an open source community, but it seems to be
>>>> assuming that the event will happen and addresses logistics.
>>>> >
>>>> > Here's an example of what I mean: the doc suggests the different
>>>> levels of sponsors, slots at those levels, and prices. But I think the main
>>>> question the community has to think through before we get there --- and
>>>> what I'd expect in a proposal --- is how to ensure that such an event
>>>> remains commercially neutral. Because you're asking for this to be an
>>>> "official" event from the community and using its trademarks, we need to
>>>> think through how we want to strike that balance.
>>>> >
>>>> > I'd like to see more of a proposal around:
>>>> > 1. Should the Iceberg community put on an event? Clearly, we like the
>>>> idea of exchanging ideas, but it goes beyond that.
>>>> > 2. How would we balance the interests of different parts of the
>>>> community and why should we take that approach?
>>>> >
>>>> > We have a lot of different companies contributing and building around
>>>> Iceberg. The last thing that we want to do is give the impression that the
>>>> community is in any way "pay-to-play" --- that's one of this community's
>>>> distinguishing features.
>>>> >
>>>> > Also, I want to disclose that I'm also associated with a vendor
>>>> (Tabular). With that hat on, I think we'd happily sponsor an event like
>>>> this. But with my community hat on I want to make sure we plan it out and
>>>> think carefully.
>>>> >
>>>> > Ryan
>>>> >
>>>> > On Fri, Sep 22, 2023 at 2:09 AM Jean-Baptiste Onofré <j...@nanthrax.net>
>>>> wrote:
>>>> >>
>>>> >> Hi guys,
>>>> >>
>>>> >> Finally (sorry for the long wait :)), a first formal Iceberg Summit
>>>> >> proposal doc is ready to be populated/reviewed:
>>>> >>
>>>> >>
>>>> https://docs.google.com/document/d/1Uy9-qRxLtjMWJkRXsjj94Vq3VO1Mc0wGz_bnisevNh8/edit?usp=sharing
>>>> >>
>>>> >> Anyone can edit the document, so feel free to complete or ask
>>>> >> questions via comments.
>>>> >>
>>>> >> Thanks !
>>>> >> Regards
>>>> >> JB
>>>> >>
>>>> >> On Wed, Aug 23, 2023 at 11:25 PM Jean-Baptiste Onofré <
>>>> j...@nanthrax.net> wrote:
>>>> >> >
>>>> >> > It sounds great :)
>>>> >> >
>>>> >> > I will include a note in the proposal doc about that.
>>>> >> >
>>>> >> > Regards
>>>> >> > JB
>>>> >> >
>>>> >> > Le mer. 23 août 2023 à 14:14, Brian Olsen <bitsondata...@gmail.com>
>>>> a écrit :
>>>> >> >>
>>>> >> >> Out of curiosity, is anyone strongly opposed to doing antics like
>>>> this for summits?
>>>> >> >>
>>>> >> >>
>>>> https://youtube.com/playlist?list=PLFnr63che7wYFsknFAqisURvfm96rW0Dr
>>>> >> >>
>>>> >> >>
>>>> >> >> On Mon, Aug 21, 2023 at 6:58 PM Matt Topol <
>>>> zotthewiz...@gmail.com> wrote:
>>>> >> >>>
>>>> >> >>> 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
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Ryan Blue
>>>> > Tabular
>>>>
>>>
>>>
>>> --
>>> Ryan Blue
>>> Tabular
>>>
>>
>
> --
> Ryan Blue
> Tabular
>

Reply via email to