Re: Quoting and attribution (was: Python and IDEs [was Re: Python 3 is killing Python])
On 2014-08-12 10:11, Steven D'Aprano wrote: It is rude to deliberately refuse to give attributes While I find this true for first-level attribution, I feel far less obligation to attribute additional levels (and the verbosity they entail). If the reader is really that interested in who said what, then they can go back to previous posts to disinter that information. I find that On 2013-12-14 Ian Paul Freely wrote: On 2014-12-11 Xavier Onasis wrote: On 2014-12-10 Pat McCann wrote: On 2014-12-09 Mike Easter wrote: Lunch for Mary's birthday? How's Wednesday? Wed is good, what time? Earlier is better for me. 11:30? How about at that little Greek place on 4th Street? could just credit Ian and snip out the other attributions for the sake of quoting just the parts that I find matter. On 2013-12-14 Ian Paul Freely wrote: Lunch for Mary's birthday? How's Wednesday? Wed is good, what time? Earlier is better for me. 11:30? How about at that little Greek place on 4th Street? If I really care about who was associated with more historical comments, I'll pull up my message history and read the details. -tkc -- https://mail.python.org/mailman/listinfo/python-list
Re: Quoting and attribution (was: Python and IDEs [was Re: Python 3 is killing Python])
On Mon, 11 Aug 2014 19:27:25 -0500, Tim Chase wrote: On 2014-08-12 10:11, Steven D'Aprano wrote: It is rude to deliberately refuse to give attributes While I find this true for first-level attribution, I feel far less obligation to attribute additional levels (and the verbosity they entail). If the reader is really that interested in who said what, then they can go back to previous posts to disinter that information. I cannot disagree with that. I consider that the first-level attribution MUST be given, second-level SHOULD be given, and third- and subsequent levels MAY be given, where MUST/SHOULD/MAY have their conventional meanings from RFC 2119. https://www.ietf.org/rfc/rfc2119.txt With one proviso: if you respond *directly* to something quoted at the Nth-level, for any N, (as opposed to merely leaving it in to establish context), then you MUST given an attribution. Even if that attribution is just Sorry, I don't know who said this, you ought to make an honest effort to give credit to those you quote directly. -- Steven -- https://mail.python.org/mailman/listinfo/python-list
Re: Quoting and attribution (was: Python and IDEs [was Re: Python 3 is killing Python])
On Tue, Aug 12, 2014 at 12:07 PM, Steven D'Aprano st...@pearwood.info wrote: I cannot disagree with that. I consider that the first-level attribution MUST be given, second-level SHOULD be given, and third- and subsequent levels MAY be given, where MUST/SHOULD/MAY have their conventional meanings from RFC 2119. https://www.ietf.org/rfc/rfc2119.txt That's fair. It's also very easy to give first-level attribution (just set your client up properly and that's that), while giving second-level means carefully retaining it from upstream. If it's easy (if you're quoting the beginning of the quote), then it's still of value, but it's not as important as first-level. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Quoting and attribution (was: Python and IDEs [was Re: Python 3 is killing Python])
On 2014-08-12 02:07, Steven D'Aprano wrote: It is rude to deliberately refuse to give attributes While I find this true for first-level attribution, I feel far less obligation to attribute additional levels (and the verbosity they entail). I cannot disagree with that. I consider that the first-level attribution MUST be given, second-level SHOULD be given, and third- and subsequent levels MAY be given With one proviso: if you respond *directly* to something quoted at the Nth-level, for any N, (as opposed to merely leaving it in to establish context), then you MUST given an attribution. For these case, I tend to do it interlinearly with my response, e.g. while you have some good points, I still lean towards Terry's recommendation to frobniculate the hammerjammer rather than have a long list of attributions at the top of the email. -tkc -- https://mail.python.org/mailman/listinfo/python-list
