Sounds good. Javadoc is the tool for Java. :) On Sat, May 7, 2016 at 9:44 AM, Uwe Korn <uw...@xhochy.com> wrote:
> Hello, > > as Arrow grows and we want to improve usage/adoption, we definitely need > to start documenting it a bit. I would volunteer to work on writing some > sections, but first we need to agree on the used tools. I would suggest the > following setup: > > * central Arrow documentation (i.e. the layout, IPC design, other > language independent stuff) could be written in asciidoc or markdown > * Language specific documentation, mainly API documentation, > installation how-tos and some basic usage (should link to the > central documentation as much as possible instead of copying content). > o Python with Sphinx and sphinx-apidoc > o C++ with doxygen > o Java with whatever currently the standard in the Java world is :) > > Please let me know if you feel comfortable with this structure and what > tools are preferred. > > Cheers > > Uwe > >
