> Using org-mode instead of outline-mode is a no-brainer. The onlyI will write a page on Worg about this.
> 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.
Aside from the scalability of Org wrt to big bug databases, I'm myself
>> 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.
only 50% convinced it's an effective setup. I'd be glad to work on the
I don't know. Org is certainly not written for that purpose. But
>> 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?
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
> Nope, the 20MB is the bugs' text alone.
> 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
Yes. In the setup I described in the previous email, no human directly
> 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
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.