Re: Clarification: public private replies [WAS Re: Formal reminder of Codes of Conduct]

2023-12-22 Thread Andrew M.A. Cater
cc. to commun...@debian.org because I'm explaining CT involvment. On Fri, Dec 22, 2023 at 12:47:51PM +, Andy Smith wrote: > Hello, > > On Thu, Dec 21, 2023 at 03:49:13PM -0800, David Christensen wrote: > > On 12/21/23 14:27, Andrew M.A. Cater wrote: > > > Posting well-intentioned private repl

Re: Clarification: public private replies [WAS Re: Formal reminder of Codes of Conduct]

2023-12-22 Thread Andy Smith
Hello, On Thu, Dec 21, 2023 at 03:49:13PM -0800, David Christensen wrote: > On 12/21/23 14:27, Andrew M.A. Cater wrote: > > Posting well-intentioned private replies back to the list is not > > appropriate. > > Please clarify how the Debian Community Team wishes us to respond to the > following u

Re: Clarification: public private replies

2023-12-22 Thread Michael Kjörling
I'm not Andrew, and can't answer for Andrew or for anyone on the Debian Community Team, but my take on this is: On 21 Dec 2023 15:49 -0800, from dpchr...@holgerdanske.com (David Christensen): > On 12/21/23 14:27, Andrew M.A. Cater wrote: >> Posting well-intentioned private replies back to the lis

Re: Clarification: public private replies [WAS Re: Formal reminder of Codes of Conduct]

2023-12-21 Thread David Christensen
On Thu, Dec 21, 2023 at 02:59:26PM -0700, Charles Curley wrote: Clarification, please. Occasionally a miss-configured mail reader will cause a private off-list reply, which the correspondent does not notice. My usual response to that sort of thing is to suggest that the correspondent fix his mail