I agree that it will get out of date. But I think we would just put the date on each article we post and leave it to the reader to decide if what is posted is still relevant. We could perhaps include a disclaimer. I think it's useful for newcomers to see the activity happening around Calcite. -- Michael Mior mm...@apache.org
Le lun. 23 sept. 2019 à 18:06, Julian Hyde <jh...@apache.org> a écrit : > > A section of the web site might take quite a bit of curation, because these > links go out of date. Also, we might find ourselves asked to endorse > companies and products, which we shouldn’t be doing. > > I think a reasonable compromise is to use the @ApacheCalcite twitter account > to forward interesting content. The good stuff often gets picked up by > aggregators such as Data Eng Weekly[1], and by tweeting we can help the > editors of those aggregators find the good content. > > Julian > > [1] https://dataengweekly.com/ <https://dataengweekly.com/> > > > > > On Sep 23, 2019, at 7:39 AM, Michael Mior <mm...@apache.org> wrote: > > > > Thanks for sharing! > > > > On a related note, I wonder what others think about having a section > > of the website where we include links to such b blog posts and > > articles referencing Calcite. > > -- > > Michael Mior > > mm...@apache.org > > > > Le lun. 23 sept. 2019 à 09:50, Robert Yokota <rayok...@gmail.com> a écrit : > >> > >> Hi, > >> > >> In case anyone is interested, I wrote a post about integrating Calcite, > >> Omid, Avatica, Avro, and Kafka here: > >> https://yokota.blog/2019/09/23/building-a-relational-database-using-kafka/ > >> > >> Regards, > >> Robert >
