Re: Managing the community information stream

Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Alvaro Herrera wrote:
> > > Bruce Momjian wrote:
> > > > Alvaro Herrera wrote:
> > >
> > > > > In Debian's bug tracking system, when the bug is created (which is done
> > > > > by sending an email to a certain address) it gets a number, and the
> > > > > email is distributed to certain lists. People can then reply to that
> > > > > mail, and send messages to 12345(at)bugs(dot)debian(dot)org and it gets tracked in
> > > > > the bug, and you can see all those messages in the bug report. I
> > > > > ass-ume that BZ 3.0 does something similar.
> > > >
> > > > But often a TODO item has multiple threads containing details (often
> > > > months apart), and it isn't obvious at the time the thread is started
> > > > that this will happen. Note the number of TODO items that now have
> > > > multiple URLs. How is that handled?
> > >
> > > Just add the bug address to CC and reply to it, just like when you reply
> > > to say "added to TODO", only that you don't need to manually go and
> > > modify the TODO file by hand. The bug tracking system puts that mail
> > > into the bug report. Subsequent followups keep the bug address in CC
> > > and thus the whole discussion is saved in the bug report.
> >
> > Right, but you are adding the bug addresss at the end of the email
> > thread. How do you point to the email you want to reference?
>
> I am not sure. We will have to investigate more the capabilities of the
> bug tracking system we intend to use. In the worst case one could add
> the URL for the archived message copy; second worst would be bouncing
> (hopefully not forward) the interesting messages to the bug address.

Sounds like what I do with the TODO list now.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +