Sorry about this, can we please remove [email protected] as it is discontinued. I don't think [email protected] can work in this case.
Thanks. On 20 May 2014, at 09:37, Sneha Nathani <[email protected]> wrote: > Failed to deliver to '[email protected]' > SMTP module(domain [192.168.0.108]) reports: > host [192.168.0.108] says: > 550 [email protected] unknown user account > > Reporting-MTA: dns; inflightproductions.com > > Original-Recipient: rfc822;<[email protected] > > Final-Recipient: rfc822;<[email protected] > > Action: failed > Status: 5.0.0 > Remote-MTA: dns; [192.168.0.108] > Diagnostic-Code: smtp;host [192.168.0.108] says: > 550 [email protected] unknown user account > Received: from [192.168.0.246] (HELO ifpmax) > by inflightproductions.com (CommuniGate Pro SMTP 5.4.7) > with SMTP id 28593088; Fri, 16 May 2014 17:17:58 +0100 > Subject: Job Sheet Completed > To: [email protected] > From: [email protected] > Return-Path: [email protected] > Date: Fri, 16 May 2014 17:17:58 +0100 > Content-Type: multipart/alternative; > boundary="=_d1758738fcaa5d82784cdfb4f9ce416f" > MIME-Version: 1.0 > Message-ID: <[email protected] > > On 19 May 2014, at 21:30, Joan Touzet <[email protected]> wrote: > >> Jason, thanks for your time to review the text. >> >> I've inserted the Oxford comma everywhere. I've also added "excessive or >> unnecessary profanity" to the laundry list. >> >> For point 5, the parallel structure is limited to finishing the sentence >> "We strive to..." and doesn't have to start with "be," see point 7 for >> the canonical counterexample. >> >> I've explicitly avoided most of the terms you mention (respect, >> politeness, civility) because they don't alone capture all of the >> behaviours listed there. To wit, you can insult a friend jokingly, but >> others may not understand the humorous intent and find it upsetting or >> offputting. In the text, it does say you should not "insult or put down >> other participants." I think that's clear enough. I am open to "choose >> words carefully" if others think the current text is too wordy, but >> the current text does come directly from upstream @ >> http://speakup.io/coc.html >> >> -Joan >> >> ----- Original Message ----- >> From: "Jason Smith" <[email protected]> >> To: [email protected] >> Sent: Monday, May 19, 2014 2:09:52 PM >> Subject: Re: Code of Conduct & Diversity Statement draft needs your feedback! >> h >> Hi, Joan. Thanks for this! >> >> First, a perhaps trivial note: the document switches once or twice to and >> from the Oxford comma. ("...twitter, and"; "...friendly and") >> >> I have two comments about specific guideline 5 ("words we choose"). >> >> Can we get profanity explicity listed here? It is generally considered >> unprofessional; but I don't like it on inclusiveness grounds. Profanity is >> characteristically Western and it can be a turn-off for non-Westerners. I >> would phase it: "excessive or unnecessary profanity" >> >> Next, as much as possible, should we stick to "what you do" rather than >> "what you are"? Rather than "be careful in the words that we choose" what >> about "be respectful" or "be polite" or "be professional"? I can imagine >> somebody saying "I *did* carefully choose to say <something hurtful> >> because the situation demanded it." >> >> I know this code is intentionally subjective, so maybe my loophole is no >> big deal. Anyway, the current phrasing is a bit awkward in its own right. >> Maybe just "Choose words carefully" or "Communicate politely" (or any >> synonym). Or to keep your parallel structure, maybe "Be civil." >> >> >> On Sun, May 18, 2014 at 6:19 AM, Joan Touzet <[email protected]> wrote: >> >>> Hello everyone, >>> >>> The draft CoC and diversity statement have been published at: >>> >>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=41812010 >>> >>> The wiki is a bit slow today so if it doesn't load the first time, hit >>> reload and be patient. >>> >>> Please take the time to review this and post comments here on the dev >>> ML. >>> >>> Outstanding items (2 and 3 are specifically for the PMC): >>> >>> 1. Create expanded CoC for conferences/events >>> 2. Determine appropriate venue and scope for diversity ML >>> 3. Determine appropriate private reporting compliance mechanism >>> >>> -Joan >>> >> >> >> ----------------------------- >> >> >> Registered Office: 15 Stukeley Street, London WC2B 5LT, England. >> Registered in England number 1421223 >> >> This message is for the designated recipient only and may contain >> privileged, proprietary, or otherwise private information. If you have >> received it in error, please notify the sender immediately and delete the >> original. Any other use of the email by you is prohibited. Please note that >> the information provided in this e-mail is in any case not legally binding; >> all committing statements require legally binding signatures. >> >> >> http://www.inflightproductions.com >> >> >> > > > > > ----------------------------- > > > Registered Office: 15 Stukeley Street, London WC2B 5LT, England. > Registered in England number 1421223 > > This message is for the designated recipient only and may contain privileged, > proprietary, or otherwise private information. If you have received it in > error, please notify the sender immediately and delete the original. Any > other use of the email by you is prohibited. Please note that the information > provided in this e-mail is in any case not legally binding; all committing > statements require legally binding signatures. > > > http://www.inflightproductions.com >
