On 2011-02-04 15:15, Zooko O'Whielacronx wrote: > On Fri, Feb 4, 2011 at 6:21 AM, Greg Troxel <[email protected]> wrote: >> >> I'm going to stop sending a few hand-selected messages from the trac >> instance to tahoe-dev > ... >> Why? I suppose it might too noisy to subject every to, but I find that >> I'm more likely to post a ticket comment knowing that it will be part of >> the tahoe-dev conversation.
That's also my objection to this change. > First that it takes some of my time to manually choose which messages > to forward, but more importantly that it gives people a false > impression of the trac-based conversations. > > Some people don't realize that there are trac tickets that never > appear on tahoe-dev, and they may be relying on tahoe-dev to notify > them of trac tickets and thus miss out on something that is important > to them. Agreed. > I'm not sure what the best solution is. Maybe people who have things > to say to *both* a ticket discussion and to tahoe-dev should manually > cut-and-paste their comment into both forums. Manually sending a comment both to the ticket and the list crosses a significant inconvenience threshold. Also, it causes anyone who would have got a copy from trac (e.g. because they are the owner or are subscribed to tahoe-lafs-trac-stream), to receive a duplicate, which will not be suppressed by their mail software because it will have a different Message-ID. > People frequently have things to say to both forums and I think this > is a very healthy pattern. Or, people could post to tahoe-dev and then > update the trac ticket with a link to their message in the tahoe-dev > archives. I do that occasionally, but find it to be a significant hassle. > Or, specific trac tickets could have Cc: tahoe-dev added to them, and > readers could understand that only specific tickets are being posted > to the list, but for those tickets every comment is being posted? > > I'm really not sure what is best. If I had to choose right now I would > say that people are encouraged to "cross post" their trac comments by > setting Cc: tahoe-dev when they post their trac comment and then > immediately unsetting it afterward. That will result in a spurious message to tahoe-dev when the cc: is unset, I think. It will also result in noise in the comment stream (both on the ticket and to tahoe-lafs-trac-stream). Can the moderation be set to post to tahoe-dev whenever a comment contains the string "[tahoe-dev]" (and for all openings of new tickets)? This would also trigger when that part of the comment is quoted in a reply, which I think is a desirable feature. > Then at least the decision about whether a given comment goes to the > list would be in the hands of the comment-writer instead of a moderator > and would be made on a per-comment basis. Right, the "[tahoe-dev]" trigger also has this property. -- David-Sarah Hopwood ⚥ http://davidsarah.livejournal.com
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tahoe-dev mailing list [email protected] http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
