Return-Path: X-Original-To: apmail-tuscany-dev-archive@www.apache.org Delivered-To: apmail-tuscany-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 A4BEF3598 for ; Wed, 4 May 2011 08:28:03 +0000 (UTC) Received: (qmail 94620 invoked by uid 500); 4 May 2011 08:28:03 -0000 Delivered-To: apmail-tuscany-dev-archive@tuscany.apache.org Received: (qmail 94585 invoked by uid 500); 4 May 2011 08:28:03 -0000 Mailing-List: contact dev-help@tuscany.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tuscany.apache.org Delivered-To: mailing list dev@tuscany.apache.org Received: (qmail 94578 invoked by uid 99); 4 May 2011 08:28:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 May 2011 08:28:03 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of simonslaws@googlemail.com designates 209.85.216.181 as permitted sender) Received: from [209.85.216.181] (HELO mail-qy0-f181.google.com) (209.85.216.181) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 May 2011 08:27:57 +0000 Received: by qyg14 with SMTP id 14so683141qyg.5 for ; Wed, 04 May 2011 01:27:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=EMTaCeVtJgNovMvJvKyVtHjao2igAnY/PDs4ciVUr8k=; b=h/nzU9E9+YpuG30Be2a9dG85KMsO2HIbqkO8rzSBcBI2CRmDttAoExgiq1Vr2N3zop LLFICQrjDWpdxzkYNsf+V8dU7R0SX/VPbRls4q+/NQNhuPAIweMnnJHBRjlG4Egx2vC9 CVDDz6IHeMokoT4jGfPZFfOh+papRR8Yvy9KA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=E80L1SdVJz0ww5AvmEgNmRpKb80harnGYQnklw2Xr37z6bru5/V4JutW+omXjqLps+ N0qXBLbUuUmmJCpYQX6aH426IHSZaNJXU12HHShApv42UD2fkTNkKW9XsvM03zBa5ZqI hNz2r+K65HK6yT48V97DWdA7kAo1ijHuXPPIA= MIME-Version: 1.0 Received: by 10.229.8.195 with SMTP id i3mr521441qci.26.1304497656802; Wed, 04 May 2011 01:27:36 -0700 (PDT) Received: by 10.229.73.71 with HTTP; Wed, 4 May 2011 01:27:36 -0700 (PDT) In-Reply-To: References: Date: Wed, 4 May 2011 09:27:36 +0100 Message-ID: Subject: Re: Documentation Patch Creating Guide From: Simon Laws To: dev@tuscany.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Sun, May 1, 2011 at 6:45 PM, Nirmal Fernando wr= ote: > Hi, > > Is there any guide on providing documentation patches to Tuscany? > > Thanks. > > -- > Best Regards, > Nirmal > > C.S.Nirmal J. Fernando > Department of Computer Science & Engineering, > Faculty of Engineering, > University of Moratuwa, > Sri Lanka. > Blog:=A0http://nirmalfdo.blogspot.com/ > Hi Nirmal Do you mean documentation on the website or in readmes? For the web site we're still using the wiki to create the pages. This makes it very easy for those with karma to go and fix it but a bit tricky to create patches for it. There are some instructions here [1]. The Tuscany 1.x. web site wiki can be found here [2] and the Tuscany 2.x web site here [3]. If it's some readme docs in the distribution you want to change then just create a patch file base on the difference between what's in svn and what you want and attach it to a JIRA. [1] https://cwiki.apache.org/confluence/display/TUSCANYWIKI/Home [2] https://cwiki.apache.org/confluence/display/TUSCANY/Home [3] https://cwiki.apache.org/confluence/display/TUSCANYxDOCx2x/Index Hope that helps Simon --=20 Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com