Many people who are interested in Avatica are not interested in Calcite. (Yes the Board are interested in both, because they are interested in the communities, which overlap. But users of Avatica, not so much. And if people perceive that Avatica requires Calcite they might be less likely to adopt it.)
I think Avatica would be more discoverable if it was hosted at https://avatica.apache.org <https://avatica.apache.org/>, rather than https://calcite.apache.org/avatica/ <https://calcite.apache.org/avatica/>. I think the brief mention of Avatica on Calcite’s home page is adequate. Perhaps there should be a section on Avatica in https://calcite.apache.org/community/ <https://calcite.apache.org/community/>. In other words, it’s time to move Avatica a little further along its evolution from module to sub-project to independent project. Julian > On Oct 17, 2019, at 6:54 AM, Michael Mior <mm...@apache.org> wrote: > > Since there's only one sub-project, why don't we convert the > Sub-Projects section on the homepage into a short description of > Avatica? > -- > Michael Mior > mm...@apache.org > > Le jeu. 17 oct. 2019 à 06:19, Francis Chuang > <francischu...@apache.org> a écrit : >> >> This was one of the comments on the October Board report for Calcite: >> >> df: Great progress! >> >> About Avatica - I had to google to find the subproject as I did >> not see anything obvious on the Calcite site. I would also be >> good to provide more status on the subproject in your future >> reports. >> >> The Avatica sub-project is currently linked on Calcite's homepage, but >> it is not very noticeable or discoverable. >> >> Any thoughts on how we can improve the visibility of Avatica? >> >> Francis
