Historically this has actually been quite easy, so I would stick with a loose guideline until there's a real problem - inline/bottom reply by default, top/inline reply for patches.
We're all hopefully smart enough to handle the edge cases. -- http://puppetlabs.com/ | +1-615-594-8199 | @puppetmasterd On Sep 24, 2010, at 9:38, Jacob Helwig <ja...@puppetlabs.com> wrote: > Personally, I also prefer bottom-posting, but I think that if we're > top-posting at all, that we should be doing it all of the time. > > I don't think that the distinction between "patch review threads", and > "discussion threads" is quite as clear as your summary would imply, > since I can see discussions being spawned from patch reviews (such as > this one). Where exactly does the line get drawn? > > Top-posting all of the time would have fewer exceptional cases for > people to have to remember (IOW: No exceptions). If you're replying > inline, you did top-post saying "The rest of my replies are inline with > the quoted text.". With bottom-posting some of the time, would we > switch if a discussion results from a patch review? When would we > switch? If we don't, then we're no longer bottom-posting in discussion > threads. Just seems like too much for a new member (IE: Me) to pick up > from just lurking on the lists; it would seem like the "convention" is > that there isn't one. > > -- > Jacob Helwig > > On Fri, 24 Sep 2010 12:04:15 +0200, Brice Figureau wrote: >> >> On Thu, 2010-09-23 at 18:27 -0700, Jacob Helwig wrote: >>> Actually, for me, it's harder to top-post, since my mail client is setup >>> to automatically put me just above my signature (below the quoted email) >>> when composing. ;-) >> >> I feel the same. >> >>> If it's standard practice, because that's what we want, then I'll change >>> what I do. If it's standard practice because most people are using the >>> gmail web interface, and are lazy... ;-) So...in light of what appear >>> to be a number of ambiguities in our processes, as of late: Should I >>> actually change what I'm doing, or were you just trying to save me some >>> effort? (Top-posted, assuming the former.) >> >> I myself largely prefer bottom-posting for discussion thread like this >> one. But top-most make sense for patches, since you wan't your answer to >> be noticed at first glance (ie without to scroll page long). >> Of course code comments should be inlined in the patch. >> >> If I had to choose a convention: >> * discussion thread: bottom-post with proper off-context text >> elimination respecting attributions >> >> * patch code reviews: answer at top, code review inlined >> >> My 0.02$ >> -- >> Brice Figureau >> Follow the latest Puppet Community evolutions on www.planetpuppet.org! >> -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-...@googlegroups.com. To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
