From: Bastien <bastienguerry@googlemail.com>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-mode as a bug tracker.
Date: Sat, 18 Jul 2009 12:46:07 +0200 [thread overview]
Message-ID: <87ab329sls.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87ocrj728a.fsf@telefonica.net> ("Óscar Fuentes"'s message of "Fri, 17 Jul 2009 17:34:13 +0200")
Hi Oscar,
Óscar Fuentes <ofv@wanadoo.es> writes:
> Right now I'm using Trac (a bug tracker and wiki combo) for bug tracking
> and project documentation on my personal projects.
>
> Looking at org-mode it seems a superb system for a this task, at least
> for one-person projects:
>
> * Plain text.
>
> * No server required.
>
> * Can be stored on the same VCS than the source code.
>
> * Great for working off-line.
>
> * Features such as time tracking and others that Trac does not support
> or does badly with plugins.
>
> * It's Emacs!
Yes, Org-mode matches perfectly the needs for a personal bug tracker.
I use Org for all my tasks and software bugs are just a subset of them.
Or maybe using Org makes me think of "repair the washing machine" as a
bug? In both case, Org greatly helps tracking stuff.
> The only downside is the lack of a referenced wiki system: simple links
> to revisions (r1010) tickets (#245) etc.
I guess simple revisions can be emulated with notes: C-c C-z
But revisions themselves are not linkable then.
Or a revision can be a new subtree in this task? Then this
revision can have its own ID (check org-id.el in contrib/)
and you can link to the revision. But that's perhaps too
much structure for bug.
> Any reasons why this is not a good idea?
Not a single one :)
> Any example of a similar org-mode usage?
Maybe have a look at org-mode/ORGWEBPAGE/todo.org - but I guess Carsten
has some other secret todo.org :)
--
Bastien
next prev parent reply other threads:[~2009-07-18 10:46 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
2009-07-20 14:35 ` Óscar Fuentes
2009-07-18 10:46 ` Bastien [this message]
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=87ab329sls.fsf@bzg.ath.cx \
--to=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).