>-----Original Message----- >From: ciphershed-bounce@xxxxxxxxxxxxx [mailto:ciphershed- >bounce@xxxxxxxxxxxxx] On Behalf Of Niklas Lemcke - ??? >Sent: Friday, June 27, 2014 10:41 >To: ciphershed@xxxxxxxxxxxxx >Subject: [ciphershed] Re: CipherShed.org mail addresses > >On Fri, 27 Jun 2014 10:30:05 -0400 >"Alain Forget" <aforget@xxxxxxx> wrote: > >> >-----Original Message----- >> >From: ciphershed-bounce@xxxxxxxxxxxxx [mailto:ciphershed- >> >bounce@xxxxxxxxxxxxx] On Behalf Of Niklas Lemcke - ??? >> >Sent: Friday, June 27, 2014 08:04 >> >To: ciphershed@xxxxxxxxxxxxx >> >Subject: [ciphershed] Re: CipherShed.org mail addresses >> > >> >On Fri, 27 Jun 2014 07:57:16 -0400 >> >"Alain Forget" <aforget@xxxxxxx> wrote: >> > >> >> >> >> >> >> >-----Original Message----- >> >> >From: ciphershed-bounce@xxxxxxxxxxxxx [mailto:ciphershed- >> >> >bounce@xxxxxxxxxxxxx] On Behalf Of Pid Zero >> >> >Sent: Friday, June 27, 2014 07:50 >> >> >To: ciphershed@xxxxxxxxxxxxx >> >> >Subject: [ciphershed] Re: CipherShed.org mail addresses >> >> > >> >> >Sounds like a good idea, helps to keep official comms separate. >> >> > >> >> >On Friday, June 27, 2014, Niklas Lemcke - 林樂寬 ><niklas@xxxxxxxxxxxxxx> >> >> >wrote: >> >> > >> >> > >> >> > I just added ciphershed.org to my postfix's domains. >> >> > >> >> > What do the others think about >> >> > - @ciphershed.org domains for the PMC and / or QA Team members? >> >> >> >> I'm not sure; should individual members be easily contactable? I realise >that >> >someone could look us up and get our e-mail addresses, but to actually >post >> >individual e-mail addresses for us on our website might make it too easy to >> >isolate single members? I think we want people to contact us all at the >same >> >time through the one contact e-mail address. >> > >> >The idea is not to put the addresses up publicly, but to have--as Chris >> >said--a frame for official messaging concerning the ciphershed project. >> >Otherwise users may see aforget@xxxxxxx post something on the list, >but >> >fail to see that it comes from someone on the inside / PMC. >> >> Ah, I see. That sounds reasonable. Hm, I'm just concerned that I (and >others) might accidentally post to the list with their default address (where >mine is aforget@xxxxxxx), instead of with the @ciphershed.org address. >Unfortunately, my client isn't smart enough to automatically change my >sending address depending on who I'm e-mailing...so I don't have a clear >solution. But yeah, this idea sounds reasonable, so I'll deal with it. > >just unsubscribe with your current mail and subscribe with the >ciphershed mail. Or do it manually if you don't want to rely on my >server. I'm not sure I understand what you mean. >> >> >> >> >> > - an email address for contact, that may or may not forward to either >> >> > the PMC mailing list or the public mailing list? >> >> >> >> We definitely need a general e-mail address for contact, and my initial >> >thought is that it should probably forward to the PMC mailing list. It's not >> >necessarily great, since this might muck the mailing list with spam or tech >> >support requests, but it would give the PMC the chance to either send it >> >wherever it should go and/or deliberate on how to respond, if it's a more >> >serious type thing. Will there be a (hopefully) easy way to reply from that >> >same e-mail address? >> > >> >Sure we could send something from that email. I don't know how great an >> >idea would be to share the login credentials with the whole PMC. I >> >think us answering from our personal @ciphershed.org domains might >> >actually be better, but that can be discussed. >> >> Yeah, we should discuss this. Responding from our personal >@ciphershed.org address isn't great, since I think "official" responses need to >be visible by the whole PMC. But yeah, put it on the agenda. > >CC the PMC mailing list on every response and there you go. But there's no guarantee that the other person will reply all. But yeah, something to discuss. Alain