emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: JBash <bashveank@gmail.com>
To: Bastien <bastienguerry@googlemail.com>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-orgmode@gnu.org
Subject: Re: Re: Org-mode as a bug tracker.
Date: Mon, 20 Jul 2009 10:15:28 -0400	[thread overview]
Message-ID: <407c66ac0907200715u62b84fdfodcefe0fca2f825b@mail.gmail.com> (raw)
In-Reply-To: <87fxcr513q.fsf@bzg.ath.cx>


[-- Attachment #1.1: Type: text/plain, Size: 3537 bytes --]

Not sure if this helps, and I don't know the details or the mechanism, but I
believe that John Wiegley uses org-mode as a bug tracking tool for his
ledger app.

http://wiki.github.com/jwiegley/ledger

On Mon, Jul 20, 2009 at 2:18 AM, Bastien <bastienguerry@googlemail.com>wrote:

> Óscar Fuentes <ofv@wanadoo.es> writes:
>
> > Using org-mode instead of outline-mode is a no-brainer. The only
> > incovenient is org's complexity. A basic but effective use of org is
> > straightforward but its extensive documentation may seem daunting for
> > the occasional user. Maybe a paragraph or two at the beginning of the
> > file explaining what's required for adding entries and doing simple
> > queries would help those developers who don't know nor plan to use org
> > for other uses.
>
> I will write a page on Worg about this.
>
> >> This is the basic workflow.  Of course, permissions and other issues
> >> could be refined but I think such a system is feasible.
> >
> > IMAO this setup is more complex and fragile than a conventional bug
> > tracker. The idea may seem appealing at first for a group of veteran
> > emacs users (those who insist on managing the bug database via e-mail
> > because they refuse to use a web browser, for instance) but I'm far from
> > convinced about its effectiveness.
>
> Aside from the scalability of Org wrt to big bug databases, I'm myself
> only 50% convinced it's an effective setup.  I'd be glad to work on the
> remaining 50%.
>
> >> I don't think the size of the database would really be an issue for the
> >> system above - but maybe I'm wrong on this.
> >
> > I'm afraid you are. Lots of emacs bug reports comprises hundreds of
> > lines of stack dumps, plus e-mail discussions with lots of quoted text,
> > etc. Org is great for notes, but is it practical for containing tens of
> > thousands of bug reports, some of them made of thousands of lines? And
> > you don't control what's on a bug report, they usually contain all sorts
> > of text constructs and random characters. How well it would deal with
> > bug reports about org's itself, containing excerpts from other org
> > files?  Wouldn't this confuse org?
>
> I don't know.  Org is certainly not written for that purpose.  But
> cannot the dumps and discussions but attached as files?  If so, the
> Org database would only need links to these files, not the full bug
> entry.
>
> > Nope, the 20MB is the bugs' text alone.
>
> Gee...
>
> > But attached files belong to the
> > tickets and supposedly provide key information, so you can wipe them
> > away to a place where they are not distributed along with the bug
> > database.
>
> Yes.
>
> > I think org as a bug tracker may work very well for individual
> > developers or for small groups, but not for open big projects such as
> > emacs.
>
> Yes.  In the setup I described in the previous email, no human directly
> write anything in an Org buffer, everything is taken care of by scripts.
> Which is kinda sick, 'cause Org is for humans.
>
> But still, I will continue to brainstorm on this, because if Org is so
> useful for individual bug databases, there should be a clever and useful
> way to *share* these individual databases and have a collective tool.
>
> --
>  Bastien
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

[-- Attachment #1.2: Type: text/html, Size: 4606 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-07-20 14:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 15:34 Org-mode as a bug tracker Óscar Fuentes
2009-07-17 16:25 ` Óscar Fuentes
2009-07-17 17:58   ` Eric S Fraga
2009-07-17 18:35     ` Matthew Lundin
2009-07-17 19:02       ` Eric S Fraga
2009-07-18 10:46   ` Bastien
2009-07-19 21:12     ` Óscar Fuentes
2009-07-20  6:18       ` Bastien
2009-07-20 14:15         ` JBash [this message]
2009-07-20 14:35           ` Óscar Fuentes
2009-07-18 10:46 ` Bastien
2009-07-20 23:26 ` OrgmodeOrg-mode " Wes Hardaker
2009-07-20 23:48   ` Óscar Fuentes
2009-07-21  6:01     ` Bastien

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=407c66ac0907200715u62b84fdfodcefe0fca2f825b@mail.gmail.com \
    --to=bashveank@gmail.com \
    --cc=bastienguerry@googlemail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ofv@wanadoo.es \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).