From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Avdi Grimm" Subject: Re: Re: How you can help Date: Fri, 24 Oct 2008 14:41:32 -0400 Message-ID: References: <967CE7ED-05E9-4031-9F3B-CFB826511554@alexanderonline.org> <878wsfpgtp.fsf@gollum.intra.norang.ca> <877i7zbbe4.fsf@kassiopeya.MSHEIMNETZ> <87iqrj9rdl.fsf@kassiopeya.MSHEIMNETZ> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KtRbP-0007aS-Dr for emacs-orgmode@gnu.org; Fri, 24 Oct 2008 14:41:39 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KtRbL-0007XN-Ud for emacs-orgmode@gnu.org; Fri, 24 Oct 2008 14:41:39 -0400 Received: from [199.232.76.173] (port=34172 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KtRbL-0007XH-Oc for emacs-orgmode@gnu.org; Fri, 24 Oct 2008 14:41:35 -0400 Received: from rv-out-0708.google.com ([209.85.198.245]:25646) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KtRbK-0000Qz-R6 for emacs-orgmode@gnu.org; Fri, 24 Oct 2008 14:41:35 -0400 Received: by rv-out-0708.google.com with SMTP id k29so1164690rvb.6 for ; Fri, 24 Oct 2008 11:41:33 -0700 (PDT) In-Reply-To: Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Manish Cc: Bernt Hansen , emacs-orgmode@gnu.org, Richard Riley , Ben Alexander On Fri, Oct 24, 2008 at 12:27 PM, Manish wrote: > Let me take a step back and think aloud why we need a bug-tracking and > testing system (if only to clarify my understanding) and who/when does > it help. Following scenarios come to mind (and how they can be > handled best (again only my limited understanding)): First of all, bug tracking are completely separate beasts, and should be considered separately. You can have either one without the other. Second: I don't care as much about bug tracking, except for the following case: if there is a bug tracker and I'm feeling bored and want to contribute a little, I'll check it for something that I think I can fix. If there is no such list, I won't do this, and I'll contribute less. I do *not* follow the mailing list closely enough to pick up bugs from there except by sheer chance, and this is not going to change. I really don't care where or how the list is kept, so long as there is a list. Third, regarding testing. I'm a coder, I know some ELisp, I *love* org-mode, and I would like to contribute. That said, I am completely uninterested in doing manual QA for Org. I am not going to go clicking around just to look for broken behavior. I have neither the time nor the interest. However, if there is an automated test suite I can promise you that a) I will run it before submitting any change I make; and b) I will add new tests to cover any functionality I add. However, you should take all of this with a grain of salt because I haven't submitted any code at all yet. -- Avdi Home: http://avdi.org Developer Blog: http://avdi.org/devblog/ Twitter: http://twitter.com/avdi Journal: http://avdi.livejournal.com