Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 81927 invoked from network); 20 Jul 2004 09:49:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 20 Jul 2004 09:49:54 -0000 Received: (qmail 53553 invoked by uid 500); 20 Jul 2004 09:49:54 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 53340 invoked by uid 500); 20 Jul 2004 09:49:52 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@forrest.apache.org Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 53329 invoked by uid 99); 20 Jul 2004 09:49:52 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [194.224.161.14] (HELO smtpout.juntadeandalucia.es) (194.224.161.14) by apache.org (qpsmtpd/0.27.1) with ESMTP; Tue, 20 Jul 2004 02:49:50 -0700 Received: from guadix1.juntadeandalucia.es ([10.240.216.7]) by smtpout.juntadeandalucia.es (8.11.6/8.11.6) with ESMTP id i6K9kq006960 for ; Tue, 20 Jul 2004 11:46:52 +0200 Received: from guadix1 (root@localhost) by guadix1.juntadeandalucia.es (8.11.6/8.11.6) with SMTP id i6K9kqT31485 for ; Tue, 20 Jul 2004 11:46:52 +0200 Received: from juntadeandalucia.es ([10.240.216.44]) by guadix1.juntadeandalucia.es (8.11.6/8.11.6) with ESMTP id i6K9kqP31475 for ; Tue, 20 Jul 2004 11:46:52 +0200 Received: (qmail 22181 invoked from network); 20 Jul 2004 09:46:52 -0000 Received: (QMFILT: 1.0); 20 Jul 2004 09:46:52 -0000 Received: from unknown (HELO juntadeandalucia.es) (thorsten.scherler.ext@[10.240.193.24]) (envelope-sender ) by smtpin03.juntadeandalucia.es (qmail-ldap-1.03) with SMTP for ; 20 Jul 2004 09:46:52 -0000 Message-ID: <40FCEDCC.6080905@juntadeandalucia.es> Date: Tue, 20 Jul 2004 12:02:52 +0200 From: Thorsten Scherler User-Agent: Mozilla Thunderbird 0.5 (X11/20040208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@forrest.apache.org Subject: Writing our guidelines by use-cases Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,SIGNATURE_SHORT_SPARSE,SPAM_PHRASE_00_01,USER_AGENT,X_ACCEPT_LANG version=2.43 X-Spam-Level: X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hello David, hello devs, I just want to let you know that I really like our way writing the guideliness. I feel that the last time I wrote a harsh reply regarding the "contribution procedure". I am sorry for that! I hope it was not offensiv for David and other devs! I felt to write that to this list. I was a wee bit angry with myself having the feeling that I am doing everything wrong. I now can understand better that e.g. documentation can always go into SVN seeing that other committer will pick it up and helping to fix it. This committer would not be able to help if the document is still *only* on my local harddrive. Like I said in the reply I am still learning the Apache way. Please be patient with me and my temperament . Hope that clears things up. King regards thorsten -- Thorsten Scherler Departamento de Desarrollo de Proyectos Sociedad Andaluza para el Desarrollo de la Sociedad de la Informaci�n S.A.U.