Return-Path: X-Original-To: apmail-tajo-dev-archive@minotaur.apache.org Delivered-To: apmail-tajo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3CF6410BE3 for ; Fri, 7 Mar 2014 06:38:57 +0000 (UTC) Received: (qmail 90416 invoked by uid 500); 7 Mar 2014 06:38:56 -0000 Delivered-To: apmail-tajo-dev-archive@tajo.apache.org Received: (qmail 90235 invoked by uid 500); 7 Mar 2014 06:38:42 -0000 Mailing-List: contact dev-help@tajo.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tajo.incubator.apache.org Delivered-To: mailing list dev@tajo.incubator.apache.org Received: (qmail 90226 invoked by uid 99); 7 Mar 2014 06:38:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Mar 2014 06:38:38 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of henry.saputra@gmail.com designates 74.125.82.49 as permitted sender) Received: from [74.125.82.49] (HELO mail-wg0-f49.google.com) (74.125.82.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Mar 2014 06:38:34 +0000 Received: by mail-wg0-f49.google.com with SMTP id a1so63879wgh.8 for ; Thu, 06 Mar 2014 22:38:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ikBLhLQaq8ccAR/U0L+vRH+mBB617P8JdzlM6iHffik=; b=PT9Afe4ll+Pvae7vVK+O3Jqt0xWb5uWqyTHv99AXwDpFXd5/I6KnNkJr6dGt3KCbJs 4MZWqR+MjoS9h66Vcy2FM/aH7B0lfaJ3vOo+rMZ0gWujSUNqLGxRirXTYsKegaVqM8Bz RAMmf6dEl8YdR/RcH8XphFg/i60WZPwudC1ckCZ20EvWoIaglJ5fQQROUlJol2RLIjW1 7ubREQ4oBzICRidb7MPomqDq4Kdizu52LtZ4ap7ZkUZXvMcu9+uoeDzU5dXvSBiUeiZO zCD/fSWFnNZotZmhJzrseubqo8EBUZA6FdPlX/MfaDGwpqKrGGE5q/opiI4zWH63hY6n m26w== MIME-Version: 1.0 X-Received: by 10.194.121.129 with SMTP id lk1mr16218426wjb.80.1394174292362; Thu, 06 Mar 2014 22:38:12 -0800 (PST) Received: by 10.217.10.198 with HTTP; Thu, 6 Mar 2014 22:38:12 -0800 (PST) In-Reply-To: References: Date: Thu, 6 Mar 2014 22:38:12 -0800 Message-ID: Subject: Re: [Discussion] Tajo documentation From: Henry Saputra To: "dev@tajo.incubator.apache.org" Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Thanks Hyunsik, this is helpful On Wed, Mar 5, 2014 at 11:57 PM, Hyunsik Choi wrote: > Hi guys, > > I've added HowToWriteUserDocumentations ( > https://wiki.apache.org/tajo/HowToWriteUserDocumentations) in Tajo wiki. > I hope that it would be helpful for you guys. > > - hyunsik > > > On Thu, Mar 6, 2014 at 1:33 PM, Hyunsik Choi wrote: > >> Sure, I'll add one page into wiki to explain how to write and make the new >> doc. >> >> - hyunsik >> >> >> On Thu, Mar 6, 2014 at 4:19 AM, Henry Saputra wrote: >> >>> W00t! >>> >>> Do you have any wiki or info on how to update the new doc? >>> >>> - Henry >>> >>> On Wed, Mar 5, 2014 at 1:11 AM, Hyunsik Choi wrote: >>> > The user documentation has been updated at >>> > http://tajo.incubator.apache.org/docs/0.8.0/index.html. >>> > >>> > As you can see, there are many missed docs. In order to add more >>> documents, >>> > I've created the jira issue ( >>> https://issues.apache.org/jira/browse/TAJO-658). >>> > If there are any volunteers, feel free to assign the issue or create >>> more >>> > jira issues. >>> > >>> > Best regards, >>> > Hyunsik Choi >>> > >>> > >>> > >>> > On Mon, Mar 3, 2014 at 10:31 AM, Hyunsik Choi >>> wrote: >>> > >>> >> I missed to mention that; I mentioned only in Jira. >>> >> Yes, they are just different themes. >>> >> >>> >> - hyunsik >>> >> >>> >> >>> >> On Mar 3, 2014, at 10:08 AM, Henry Saputra >>> >> wrote: >>> >> >>> >> > Hi Hyunsik, both using different themes but still using Sphinx ? >>> >> > >>> >> > - Henry >>> >> > >>> >> > On Thu, Feb 27, 2014 at 11:59 PM, Hyunsik Choi >>> >> wrote: >>> >> >> I've created TAJO-642 issue. Please take a look at the candidate >>> >> >> documentations: >>> >> >> >>> >> >> http://people.apache.org/~hyunsik/new_docs/ >>> >> >> http://people.apache.org/~hyunsik/rtd/ >>> >> >> >>> >> >> Best regards, >>> >> >> Hyunsik >>> >> >> >>> >> >> >>> >> >> On Thu, Feb 27, 2014 at 8:58 AM, Hyunsik Choi >>> >> wrote: >>> >> >> >>> >> >>> Hi Henry, >>> >> >>> >>> >> >>> You can see lots of examples at >>> http://sphinx-doc.org/examples.html. >>> >> >>> >>> >> >>> I think that we will mostly make user documentations with Sphinx. >>> >> Sphinx >>> >> >>> uses pygments for syntax highlighting. It supports a variety of >>> >> languages >>> >> >>> as you can see http://pygments.org/languages/. So, there is no >>> >> language >>> >> >>> dependent problem. In addition, developer documentation would be >>> >> sufficient >>> >> >>> with javadoc and wiki. >>> >> >>> >>> >> >>> Yes, I have a plan to change a single user documentation md file ( >>> >> >>> http://tajo.incubator.apache.org/tajo-0.8.0-doc.html) into RST >>> format >>> >> of >>> >> >>> Sphinx. As you can see, I have faced many problems aforementioned >>> >> while I'm >>> >> >>> making the documentation. I believe that Sphinx will solve these >>> >> problems. >>> >> >>> >>> >> >>> Thanks, >>> >> >>> Hyunsik >>> >> >>> >>> >> >>> >>> >> >>> >>> >> >>> On Thu, Feb 27, 2014 at 8:31 AM, Henry Saputra < >>> >> henry.saputra@gmail.com>wrote: >>> >> >>> >>> >> >>>> Sorry for the late reply Hyunsik. >>> >> >>>> >>> >> >>>> I have never used Sphinx before but quick glance from the website >>> I >>> >> >>>> thought it is primarily used to document Python code? >>> >> >>>> >>> >> >>>> Is the plan to move all md files for Tajo doc into bunch of >>> Sphinx >>> >> files? >>> >> >>>> >>> >> >>>> Looks like Pandoc [1] can help covert md files into Sphinx code. >>> >> >>>> >>> >> >>>> - Henry >>> >> >>>> >>> >> >>>> [1] http://johnmacfarlane.net/pandoc/ >>> >> >>>> >>> >> >>>> On Mon, Feb 24, 2014 at 9:23 PM, Hyunsik Choi >> > >>> >> wrote: >>> >> >>>>> Hi folks, >>> >> >>>>> >>> >> >>>>> I would like to discuss the choice of documentation tool. >>> Currently, >>> >> we >>> >> >>>>> have used markdown and generated single page HTML document from >>> the >>> >> >>>>> markdown via maven-site-plugin. >>> >> >>>>> >>> >> >>>>> I think that this approach has several problems as follows: >>> >> >>>>> * a single page is very inconvenience to edit documents. I >>> should >>> >> have >>> >> >>>>> frequently scrolled a long page. >>> >> >>>>> * The generated html from markdown page does not support table >>> of >>> >> >>>>> contents. The table of contents in the current doc has been >>> manually >>> >> >>>>> written by hand. >>> >> >>>>> * It is hard to output multiple doc formats from single source. >>> >> >>>>> >>> >> >>>>> According to the characteristics of our project, we should >>> maintain >>> >> >>>> lots of >>> >> >>>>> documentations. I think that it is very important to choose the >>> >> proper >>> >> >>>>> documentation tool before too late. >>> >> >>>>> >>> >> >>>>> I've found open source documentation tools for Tajo. I would >>> like to >>> >> >>>>> propose using sphinx (http://sphinx-doc.org) for our >>> documentation >>> >> >>>> tool. It >>> >> >>>>> seems to meet our needs. >>> >> >>>>> >>> >> >>>>> If you know other nice doc tools, feel free to suggest. >>> >> >>>>> >>> >> >>>>> Best regards, >>> >> >>>>> Hyunsik Choi >>> >> >>>> >>> >> >>> >>> >> >>> >>> >> >>> >> >>> >> >>