This is about the "discussion tooling" part of your reply, and therefore
not really related to Subversion. I'm assuming Subversion uses
scarab.tigris.org and therefore posting to their user mailing list too.
I happen to use trac.edgewall.org (a popular competitor of Scarab) for
our projects. For each issue Trac has a Description text field that can
be edited only by the project engineers to summarize the discussion that
takes place in the comments. Comments can be added by anybody that has
access to the project. AFAICS adding the same feature to scarab would
give the best of both worlds (mailing list and issue tracker) in one
place. For one thing, I, as a user, would love to have a one-stop-shop
with the whole thing (discussion+conclusions+current state of affairs
for the issue). And my (wild) guess is that this enhancement would be
nearly trivial to add to scarab.
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:email@example.com]
> Sent: 21 September 2006 10:51
> To: firstname.lastname@example.org; email@example.com
> Subject: Re: [Issue 2610] Out-of-tree .svn directories
> Hi Alessio,
> thanks for your reply on issue 2610. I'm going to close it as
> duplicate, but I'd like to answer your questions too (here on
> the users list).
> I'll try to clarify my original answers to your request:
> Quoting firstname.lastname@example.org:
> > 1) The "curruptible .svn dirs" problem has been discussed, but the
> > discussion didn't seem to come to any conclusion. As far as
> > go, I thought the svn engineers were more qualified to
> discern good ideas from crazy talk.
> 1. This is just a tooling problem. The users and dev mailing
> list are the perfect place for discussions. Note that some
> Subversion developers also read the users mailing list. The
> issue tracker is not so good for discussions, so we like to
> keep only the outcome of the discussions there with a
> reference to the mail threads. This will help the people
> looking at the issue to easily find what discussions have
> already been done, and why certain conclusions were drawn.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Sep 22 20:38:05 2006