arrow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe L. Korn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARROW-95) Scaffold Main Documentation using asciidoc
Date Tue, 05 Apr 2016 15:59:25 GMT

    [ https://issues.apache.org/jira/browse/ARROW-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226520#comment-15226520
] 

Uwe L. Korn commented on ARROW-95:
----------------------------------

There was no real discussion why asciidoc versus Markdown. [~wesmckinn] suggested it and there
were no objections. Probably we should raise that on the ML? At least a mail with the rough
idea of how the documentation should be structured?

> Scaffold Main Documentation using asciidoc
> ------------------------------------------
>
>                 Key: ARROW-95
>                 URL: https://issues.apache.org/jira/browse/ARROW-95
>             Project: Apache Arrow
>          Issue Type: Task
>            Reporter: Uwe L. Korn
>
> For the general documentation of Arrow, we want to use asciidoc. The "general documentation"
includes:
>  * The Arrow spec / memory layout
>  * Howtos for building arrow on different platforms
>  * Getting Started snippets for each language and a link to the (to-be-build) API documentation
> It would be nice to have a build system and the main file/folder structure in place so
we can split the work up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message