I went ahead and generated a blog post for the "Iceberg Summit 2026",
please take a look! https://github.com/apache/iceberg/pull/15013
Would love to get this out so that we can spread awareness for the summit
and CFP deadline.

Best,
Kevin Liu


On Fri, Jan 9, 2026 at 1:44 PM Kevin Liu <[email protected]> wrote:

> Awesome, thanks Danica!
> Yet another reminder that *the Iceberg Summit CFP is due in 8 days*!! On
> Jan 18th, https://sessionize.com/iceberg-summit-2026
>
> On Fri, Jan 9, 2026 at 12:45 PM Danica Fine via dev <
> [email protected]> wrote:
>
>> Kevin,
>>
>> This looks great! Thanks to you and everyone who helped to push this
>> forward.
>>
>> As for making the first post about promoting Iceberg Summit, I love that
>> idea, and I'd love to volunteer to help write/make that happen once the PR
>> is ready to go.
>>
>> Danica
>>
>> On Fri, Jan 9, 2026 at 12:34 PM Kevin Liu <[email protected]> wrote:
>>
>>> Thanks for the feedback everyone. I went ahead and prototype the blog
>>> page. Please take a look at https://github.com/apache/iceberg/pull/15013
>>>
>>> Looking for feedback from the community!
>>>
>>> I think it would be a great opportunity to launch the project blog and
>>> use the first post to highlight the Iceberg Summit 2026. (
>>> https://www.icebergsummit.org/)
>>>
>>> Max, I definitely got the idea from your original devlist thread.
>>> Thanks! :)
>>>
>>> Best,
>>> Kevin Liu
>>>
>>> On Thu, Jan 8, 2026 at 3:08 AM Gang Wu <[email protected]> wrote:
>>>
>>>> +1
>>>>
>>>> Apache Arrow is doing the same thing for a long time:
>>>> https://arrow.apache.org/blog/
>>>>
>>>> Dipankar Mazumdar <[email protected]> 于2026年1月8日周四 18:30写道:
>>>>
>>>>> +1 to having a project-level blog.
>>>>>
>>>>> Best,
>>>>> Dipankar
>>>>>
>>>>> On Thu, Jan 8, 2026 at 3:42 PM Renjie Liu <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> On Thu, Jan 8, 2026 at 3:44 PM Eduard Tudenhöfner <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> On Thu, Jan 8, 2026 at 12:27 AM Matt Topol <[email protected]>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> On Tue, Jan 6, 2026, 2:55 PM Yufei Gu <[email protected]> wrote:
>>>>>>>>
>>>>>>>>> +1
>>>>>>>>> Yufei
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Jan 6, 2026 at 11:39 AM Neelesh Salian <
>>>>>>>>> [email protected]> wrote:
>>>>>>>>>
>>>>>>>>>> +1 to this. We spoke about this during the Python sync this
>>>>>>>>>> morning too.
>>>>>>>>>> I like the format for Arrow: https://arrow.apache.org/blog. It's
>>>>>>>>>> a bit similar to Datafusion but feels more connected to the Arrow 
>>>>>>>>>> project
>>>>>>>>>> overall.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 6, 2026 at 11:19 AM Russell Spitzer <
>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>
>>>>>>>>>>> I'm +1 and I think we should stick to project updates and
>>>>>>>>>>> features. Release notes, events, design walkthroughs etc
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Jan 6, 2026 at 10:18 AM Tushar Choudhary <
>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I think this is a great idea too. +1
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>> Tushar Choudhary
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, 6 Jan 2026 at 9:42 PM, Maximilian Michels <
>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Kevin,
>>>>>>>>>>>>>
>>>>>>>>>>>>> +1 I had a similar idea a while back:
>>>>>>>>>>>>>
>>>>>>>>>>>>> https://lists.apache.org/thread/txhw1f27pj7444t8o8jf5qoyqk2zhjxf
>>>>>>>>>>>>> /
>>>>>>>>>>>>> "[Discuss] Iceberg Blog Posts".
>>>>>>>>>>>>>
>>>>>>>>>>>>> For example, Swapna Marru just published this Iceberg-related
>>>>>>>>>>>>> post on
>>>>>>>>>>>>> the Flink blog:
>>>>>>>>>>>>>
>>>>>>>>>>>>> https://flink.apache.org/2025/11/11/from-stream-to-lakehouse-kafka-ingestion-with-the-flink-dynamic-iceberg-sink/
>>>>>>>>>>>>> It would be great to see similar posts on the Iceberg blog.
>>>>>>>>>>>>> Even if we
>>>>>>>>>>>>> just put the release notes, I think that would already provide
>>>>>>>>>>>>> a lot
>>>>>>>>>>>>> more visibility for Iceberg.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Obviously, the posts should reflect the Iceberg community, i.e.
>>>>>>>>>>>>> revolve about Iceberg internals, using Iceberg, and not be
>>>>>>>>>>>>> affiliated
>>>>>>>>>>>>> with companies. Basically, the same rules apply to blog posts
>>>>>>>>>>>>> as to
>>>>>>>>>>>>> the rest of the code base.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>> Max
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Dec 29, 2025 at 8:03 PM Kevin Liu <
>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > Hey folks,
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > I want to gauge the interest of starting a project-level
>>>>>>>>>>>>> blog at iceberg.apache.org/blogs/, drawing inspiration from
>>>>>>>>>>>>> the Apache Datafusion blog (datafusion.apache.org/blog/)
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > The blog would focus on project-level news and updates. I
>>>>>>>>>>>>> believe starting a project blog would be beneficial to the 
>>>>>>>>>>>>> community.
>>>>>>>>>>>>> > There are many great features in-development that would
>>>>>>>>>>>>> benefit from the wider visibility that the blog will provide. 
>>>>>>>>>>>>> Thinking back
>>>>>>>>>>>>> to the V3 ratification announcement, as an Iceberg community 
>>>>>>>>>>>>> member, I
>>>>>>>>>>>>> would like to see the announcement come from the project instead 
>>>>>>>>>>>>> of
>>>>>>>>>>>>> summarized by various other blogs. Release notes would also be 
>>>>>>>>>>>>> helpful to
>>>>>>>>>>>>> put into the blog.
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > I know there were previous concerns around the logistics;
>>>>>>>>>>>>> what content belongs on the blog, who should write the blog, and 
>>>>>>>>>>>>> how should
>>>>>>>>>>>>> the community/committer/PMC review the content. I'm happy to work 
>>>>>>>>>>>>> with the
>>>>>>>>>>>>> community to provide general guidance.
>>>>>>>>>>>>> > I strongly believe the blog would have an outsize benefit to
>>>>>>>>>>>>> the community.
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > Would love to hear thoughts here.
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > Best,
>>>>>>>>>>>>> > Kevin Liu
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Regards,
>>>>>>>>>> Neelesh S. Salian
>>>>>>>>>>
>>>>>>>>>>

Reply via email to