Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 88714 invoked from network); 10 Oct 2006 16:22:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Oct 2006 16:22:52 -0000 Received: (qmail 46111 invoked by uid 500); 10 Oct 2006 16:22:51 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 46067 invoked by uid 500); 10 Oct 2006 16:22:51 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 46058 invoked by uid 99); 10 Oct 2006 16:22:51 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Oct 2006 09:22:51 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of scotsmatrix@gmail.com designates 66.249.92.175 as permitted sender) Received: from [66.249.92.175] (HELO ug-out-1314.google.com) (66.249.92.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Oct 2006 09:22:50 -0700 Received: by ug-out-1314.google.com with SMTP id g33so780046ugd for ; Tue, 10 Oct 2006 09:22:29 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=bjRcNc76sKPFHRu68HLE2pzZPIOzpHv8/b0zNDpHH2taaaRAWyX+/UInsSku9mH+0Re4gWZzhjCKYpj/Mj7YCPY42nJ2xc0eZ3rKuI1fcgllB5ikCDwNRhsBfFBY0F+Orr34gOIyNvHe6zXGPlzeeHVKlyR0y42GJwFslaxdysQ= Received: by 10.67.100.17 with SMTP id c17mr8427395ugm; Tue, 10 Oct 2006 09:22:29 -0700 (PDT) Received: by 10.66.255.3 with HTTP; Tue, 10 Oct 2006 09:22:29 -0700 (PDT) Message-ID: <9f40b500610100922p31d3a595n73f459cd59b6404@mail.gmail.com> Date: Tue, 10 Oct 2006 09:22:29 -0700 From: "Laura Stewart" To: derby Subject: Discussion: What prevents you from updating derby documentation? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N The Derby Documentation page that describes how to setup your environment, update the files, and submit patches. http://db.apache.org/derby/manuals/dita.html Yet there are very few contributors who actually update the documentation. WHY? What prevents you from updating the documentation when you update the code? Please add your suggestions for the things that you would like to see updated/added to make it easier to for people to update the Derby documentation. Here are a few of my recommendations: 1) The instructions on the Derby Documentation page need to be more comprehensive... there are missing steps or assumptions made about a contributors knowledge. 1.a. The instructions for downloading and unzipping the DITA toolkit are for the first time that you do it. If you already have it downloaded and unzipped, the steps are missing for what you should do. 2) For new information, there aren't any "templates" for the topic types: concepts, reference, task. There also isn't a good description of how to decide which type to use. 3) There are no guidelines for how to tag the text. -- Laura Stewart