From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eric Schulte" Subject: Re: Re: worg for bug reports and feature requests was: (Regression testing for org-mode) Date: Fri, 24 Oct 2008 16:54:52 -0700 Message-ID: <871vy5mtv7.fsf@gmail.com> References: <4900A06B.8020605@sift.info> <87wsfyx3tp.fsf@gmail.com> <490135D1.4030208@sift.info> <87od1a1ynr.fsf_-_@gmail.com> <49015239.1020008@sift.info> <4901D7E3.1060809@gmx.de> <87ljwd4tao.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KtWUa-0003Nt-EC for emacs-orgmode@gnu.org; Fri, 24 Oct 2008 19:54:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KtWUY-0003Mv-NA for emacs-orgmode@gnu.org; Fri, 24 Oct 2008 19:54:55 -0400 Received: from [199.232.76.173] (port=36340 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KtWUY-0003Mp-Bz for emacs-orgmode@gnu.org; Fri, 24 Oct 2008 19:54:54 -0400 Received: from wf-out-1314.google.com ([209.85.200.172]:8653) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KtWUX-0005KR-Sf for emacs-orgmode@gnu.org; Fri, 24 Oct 2008 19:54:54 -0400 Received: by wf-out-1314.google.com with SMTP id 28so1096947wfc.24 for ; Fri, 24 Oct 2008 16:54:52 -0700 (PDT) In-Reply-To: <87ljwd4tao.fsf@gmail.com> (Eric Schulte's message of "Fri, 24 Oct 2008 13:44:31 -0700") 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: sebastian_rose@gmx.de Cc: emacs-orgmode@gnu.org "Eric Schulte" writes: > Sebastian Rose writes: >> And, the list is, what everyone reads. Sometimes new people show up, >> read about a bug and provide patches. Why 'hide' the bugs somewhere? >> > > Point taken, the list has worked very well, and there is probably no > need to change it. > > That said I couldn't help myself... and implemented a very simple little > web-form which can accept error reports, and append them to a "bugs.org" > org-file. This gives every new report it's own headline in the outline, > uses TODO keywords to track the status of the report, uses properties to > track information such as the type of the report, and who is responsible > for completion, and it comments out the users input using the "^: " > syntax, to thwart any malicious inputs. I know, I know, we should use a > mature bug tracking system or none at all, but org seems so well suited, > and this is so small. How much trouble could it cause? :) > >> Where will such a system live? >> Who installs and maintains it? > > also, this solves the above problems, because if such a page were to > live as part of worg, then the resulting bugs.org files could live in > the worg git repo, and be maintained by worgers... > > Thanks -- Eric > > The attached mini-web-application is a ruby "camping" application, it > will build and maintain a bug file named "bugs.org" in the same > directory the script is located in. figured I'd actually put this up, as a better demonstration than just the source. It's just running on a server in my study, so please if you see any glaring security holes, don't kill my machine. http://org-bug.suey.ath.cx/ Thanks -- Eric