Julian Hyde commented on CALCITE-1937:

The challenge is that we would like it to appear integrated with the Avatica 
web site, but (presumably) we want to keep the source files in Avatica-Go. So, 
maybe the simplest thing is few symbolic links in {{calcite-avatica/site}} to 
files under {{calcite-avatica-go/site}}. Then someone would re-generate the 
Avatica site from within an Avatica sandbox. 

> 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

Reply via email to