You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Francis Chuang (JIRA)" <ji...@apache.org> on 2018/06/02 09:36:00 UTC

[jira] [Updated] (CALCITE-1937) Web site for Avatica Go

     [ https://issues.apache.org/jira/browse/CALCITE-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francis Chuang updated CALCITE-1937:
------------------------------------
    Fix Version/s: avatica-1.12.0

> 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
>            Priority: Major
>             Fix For: avatica-1.12.0
>
>
> 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
(v7.6.3#76005)