[
https://issues.apache.org/jira/browse/CALCITE-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123227#comment-16123227
]
Francis Chuang commented on CALCITE-1937:
-----------------------------------------
I've done the following:
- Move documentation into go_client_reference.md under site/
- Create go_history.md under site/
- Reduced README.md to the barebones.
See PR: https://github.com/apache/calcite-avatica-go/pull/2
Question: I've removed most references to Apache Phoenix. Is this a good idea?
There may be some benefits of including references to Phoenix as there is no
doubt people are searching for a Go Phoenix database/sql driver using their
favorite search engine. Having no references to Phoenix reduces this
visibility, although it prevents confusion between the Phoenix and Calcite
projects.
> 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)
