[tahoe-dev] "No Conversations in the Bug Tracker", help wanted for Tahoe-LAFS Weekly News

[Paul Rabahy]

I'm still new to the Tahoe community so am willing to follow others lead.

Personally I disagree with Karl's book because using the bug tracker
automatically organizes the conversation into a logical thread. If I want
to find out everything about some broken thingy, I can find that ticket and
read the entire history. I find the bug tracker much more searchable
and concise than the mailing list archive. I also believe that using the
bug tracker allows greater granularity of visibility than the mailing list.
For example, if I don't care about IPV6, I can subscribe/unsubscribe to
that bug at my choice. If all IPV6 comments are posted to the mailing list,
it is more difficult for me to filter that out from topics that I
am interested in.


On Mon, Feb 18, 2013 at 2:43 PM, Greg Troxel <gdt at ir.bbn.com> wrote:

>
> "Zooko O'Whielacronx" <zookog at gmail.com> writes:
>
> > The problem with this, according to Karl's book, is that then people
> > who read the mailing list are left out of conversations like that one.
> > That's a serious problem that can stymie forward progress. On the
> > other hand, I think this style has been working okay for us. If you
> > really want to understand all of the technical decisions, and the
> > reasoning behind them, then you have to read the trac timeline as your
> > daily newspaper or subscribe to get email from trac anytime a new
> > comment is published.
>
> This is a tough issue.  At work, I make the entire project get all
> ticket comments.  But those are people spending at least 20 hours/week
> on the project.  Here, it seems like perhaps the trac-stream should go
> to tahoe-dev.  But that might drive people away (even more than my v6
> ranting :-).
> So I think the way tahoe is set up now is ok.
>
>
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130219/f8c4010a/attachment.html>