Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A1FC411AB3 for ; Fri, 19 Sep 2014 14:03:44 +0000 (UTC) Received: (qmail 68153 invoked by uid 500); 19 Sep 2014 14:03:44 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 68128 invoked by uid 500); 19 Sep 2014 14:03:44 -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 68115 invoked by uid 99); 19 Sep 2014 14:03:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Sep 2014 14:03:44 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of camilla.haase@oracle.com designates 156.151.31.81 as permitted sender) Received: from [156.151.31.81] (HELO userp1040.oracle.com) (156.151.31.81) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Sep 2014 14:03:17 +0000 Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s8JE3Eno004644 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 19 Sep 2014 14:03:15 GMT Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by ucsinet22.oracle.com (8.14.5+Sun/8.14.5) with ESMTP id s8JE3DMa008869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 19 Sep 2014 14:03:14 GMT Received: from abhmp0016.oracle.com (abhmp0016.oracle.com [141.146.116.22]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s8JE3DpU022329 for ; Fri, 19 Sep 2014 14:03:13 GMT Received: from [10.152.23.26] (/10.152.23.26) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 19 Sep 2014 07:03:13 -0700 Message-ID: <541C379E.4000305@oracle.com> Date: Fri, 19 Sep 2014 10:03:10 -0400 From: Camilla Haase Organization: Oracle Corporation User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: Please contribute to the Derby documentation References: <54132B93.7000408@oracle.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Source-IP: ucsinet22.oracle.com [156.151.31.94] X-Virus-Checked: Checked by ClamAV on apache.org Thanks to everyone for the kind words. I have really enjoyed working on this project over the years and am finding it hard to disengage! I am staying on the mailing lists and am still a committer, so I will be monitoring doc issues in my spare time when I can. You have all been terrific to work with, and I look forward to seeing Derby continue to improve. Best wishes, Kim On 9/19/2014 7:54 AM, Knut Anders Hatlen wrote: > Camilla Haase writes: > >> Hi, all, >> >> I've been working on the Derby user manuals for quite a few years now, >> but my project assignments have been changing and I won't have time to >> spend on Derby in the future. New features will continue to be >> documented, but staffing for fixing bugs will not be available. >> Therefore, I would like to invite other Derby developers to help with >> fixing documentation issues. >> >> I've spent the past few days weeding out these issues so that the ones >> left are all legitimate (I think), though not all solvable at present >> -- >> some depend on a software fix, others on updating our tools. >> >> Instructions on how to work with the documentation are on the Derby >> web site (http://db.apache.org/derby/manuals/index.html) under "DITA >> Source" and "Writing Guidelines." They are mostly current, though >> there's an issue requesting some updates >> (https://issues.apache.org/jira/browse/DERBY-5182). >> >> A number of you have worked with the documentation before, and I will >> be happy to answer questions from any of you, whether you're new to >> the docs or just a bit rusty. I know you're all committed to >> maintaining the quality of the manuals, so I hope we can preserve it. >> >> Thanks very much! > > Hi Kim, > > Many thanks for all the work you've put into the documentation, both > improving it and making sure all new features get properly documented. > You've helped the rest of us enormously, not only by writing docs, but > also by providing early feedback when experimenting with new features > and helping us improve them. >