[
https://issues.apache.org/jira/browse/CALCITE-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123484#comment-16123484
]
Julian Hyde commented on CALCITE-1937:
--------------------------------------
I think we should describe avatica-go as a general purpose client for avatica
but also have a section about how it works for PQS right out of the box. This
way we don't scare off people who are not using Phoenix. But we can make it
clear in the Phoenix section that it works great for Phoenix, is tested on
Phoenix versions x.x and y.y, and we have extensions such as the error message
codes.
Then I think Phoenix can also have a section on their site about the driver.
[~jamestaylor], What do you think?
> Web site for Avatica Go
> -----------------------
>
> Key: CALCITE-1937
> URL: https://issues.apache.org/jira/browse/CALCITE-1937
> Project: Calcite
> Issue Type: Bug
> Components: avatica-go
> Reporter: Julian Hyde
> Assignee: Francis Chuang
>
> Create a web site for calcite-avatica-go.
> How about this:
> * At run time, the pages should appear under http://calcite.apache.org/avatica
> * The pages should be source-controlled under calcite-avatica-go/site, in
> markdown format (same as calcite and avatica), and generated into svn using
> similar trickery to calcite and avatica.
> * Reduce the amount of content in
> https://github.com/apache/calcite-avatica-go/blob/master/README.md. The
> "documentation" stuff should move to under http://calcite.apache.org/avatica.
> So the page will be mainly a re-direct to the Apache home page. Similar to
> https://github.com/apache/calcite-avatica/blob/master/README.md, in fact.
> * Add a go_history.md file.
> Should avatica-go appear on http://calcite.apache.org/avatica/downloads, or
> should it have its own download page? I think it probably the former.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
