emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "Eric Schulte" <schulte.eric@gmail.com>
To: sebastian_rose@gmx.de
Cc: emacs-orgmode@gnu.org
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	[thread overview]
Message-ID: <871vy5mtv7.fsf@gmail.com> (raw)
In-Reply-To: <87ljwd4tao.fsf@gmail.com> (Eric Schulte's message of "Fri, 24 Oct 2008 13:44:31 -0700")

"Eric Schulte" <schulte.eric@gmail.com> writes:
> Sebastian Rose <sebastian_rose@gmx.de> 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

     prev parent reply	other threads:[~2008-10-24 23:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 16:03 Regression testing for org-mode Robert Goldman
2008-10-23 23:57 ` Eric Schulte
2008-10-24  0:03   ` Avdi Grimm
2008-10-24  2:41     ` Robert Goldman
2008-10-24  3:04       ` worg for bug reports and feature requests was: (Regression testing for org-mode) Eric Schulte
2008-10-24  4:42         ` Robert Goldman
2008-10-24 14:12           ` Sebastian Rose
2008-10-24 14:27             ` Avdi Grimm
2008-10-24 20:44             ` Eric Schulte
2008-10-24 23:54               ` Eric Schulte [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871vy5mtv7.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sebastian_rose@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).