While I understand the concerns of maintainability, I would recommend a deprecation of the page vs outright removal. (basically update the page saying it will no longer be updated, vs removing it)
Reasons Why: - To avoid breaking links on pages referring to the blog list around the web and in print - To not negatively negatively affect the several contributors the list (this would have a serious search engine listing cost to the articles on the list which helped build the community and iceberg knowledge base especially in the early days) Reasons to consider keeping the list: - Being able to contribute articles on the website creates an additional incentive for people to write more about iceberg, which is a good incentive. - Also creates more reason to link to iceberg.apache.org when people refer people to where they can find more blogs on iceberg Possible Reforms to the List: - going forward only blogs on community blog platforms like medium/substack/ dev.to can be posted - deciding on an official cadence of update like once a month - any other guidelines If you need someone to help maintain, I'd also volunteer. But otherwise, I'd deprecate the page not completely remove the page. On Thu, Sep 18, 2025 at 4:03 PM Russell Spitzer <russell.spit...@gmail.com> wrote: > Hi Y'all > > We talked about this a bit in a community sync a while back and I know a > bunch of committers have > been working off some of the consensus we reached then but I'm not sure we > ever actually documented > this. > > *1. Should the Apache Iceberg community still maintain a set of Blogs and > Talks that are curated on the * > *main site by committers and PMC members?* > > The arguments in favor: > > The current state requires individuals to make decisions on about > inclusion/exclusion of content > It is very difficult to maintain and keep up to date > There are lots of blog and talk aggregations for Iceberg content out there > already > > The arguments against: > > Have an easy place for folks to find more Iceberg Content > Have a location to post internal announcements > ----------- > > Personally I think we should just drop the blogs site for now with the > option of bringing back an Iceberg > dev only blog in the future and switch the Talks page to just link out to > the official Youtube channel which mostly > has entries for Iceberg Summit and our community syncs. > > ------- > > *2. Should all vendor/integrations link out to external documentation > rather than having in tree maintained* > *documentation?* > > This I think is more straightforward. We have already had a lot of > link-rot and Integration documentation falling behind > actual integrations. Here I really don't want to break any previous hard > links to Iceberg's docs so I think we should leave > everything currently in tree, in tree. But for all new contributions and > on any updates to a vendor.md or integration.md we > should always link out to third party documentation unless we are > documenting something that is actually in the Iceberg > library (like S3FileIO and friends). > > Thanks as usual everyone, > Russ > > Here is a PR with my suggested changes for the above two points > https://github.com/apache/iceberg/pull/14110 > > -- *Alex Merced <https://bio.alexmerced.com/data>, * *Head of DevRel, Dremio **Dremio.com* <https://www.dremio.com/?utm_medium=email&utm_source=signature&utm_term=na&utm_content=email-signature&utm_campaign=email-signature>*/ **Follow Us on LinkedIn!* <https://www.linkedin.com/company/dremio> *Resources for Getting Hands-on with Apache Iceberg/Dremio* <https://medium.com/data-engineering-with-dremio/a-deep-intro-to-apache-iceberg-and-resources-for-learning-more-be51535cff74>
