[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Orgmode] Re: worg for bug reports and feature requests was: (Regres

From: Eric Schulte
Subject: Re: [Orgmode] Re: worg for bug reports and feature requests was: (Regression testing for org-mode)
Date: Fri, 24 Oct 2008 16:54:52 -0700
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)

"Eric Schulte" <address@hidden> writes:
> Sebastian Rose <address@hidden> 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.


Thanks -- Eric

reply via email to

[Prev in Thread] Current Thread [Next in Thread]