[Systems] Access to info
James Cameron
quozl at laptop.org
Wed Nov 7 19:42:15 EST 2018
On Wed, Nov 07, 2018 at 04:38:22AM +0100, Samson Goddy wrote:
>
> On Wed, Nov 7, 2018, 4:28 AM James Cameron <[1]quozl at laptop.org wrote:
>
> Thanks. But I'm confused.
>
> What we had discussed on #sugar was changing mail aliases from;
>
> info: dogi
> pr: [2]d.crossland at gmail.com
>
> to a private mailing list with selected members, so your team could
> use the info@ and pr@ addresses in your marketing, and could be
> confident that suitable replies had been made.
>
> Public mailing list like marketing@ is too public; it does not give
> privacy to those who write to Sugar Labs. Default expectation for
> direct contact is to give privacy.
>
> By CC'ing them, I'm seeking consent from dogi and Dave to unhook them,
> but you need to explain what you need.
>
> Maybe there was a confusion somewhere. I asked to use info at SL dot org for
> sugar labs social media account that will be a private email at it will contain
> access like password.
>
> PR was what I was thinking to share among marketing team which I early thought
> redirecting or forwarding message from PR to [3]marketing at lists.sugarlabs.org
> will be a good choice. But I just noticed that just like how members at SL dot
> org are currently manage by some members. PR@ can take same
> direction too.
I'm not sure, from the above, exactly what you want pr@ to go to.
> So I am seeking permission from Dave to be added to PR@ and also seeking
> permission to gain sole access if possible for info@ because of confidential
> information that the email will have right on if granted.
Dave has agreed to unhook from pr at .
Apart from maintaining the privacy of what a random stranger
may send to the alias, what other confidential information do you plan
to handle?
I'd like Sugar Labs to operate transparently as much as possible.
https://en.wikipedia.org/wiki/Transparency_(behavior)
So it would be better if pr@ and info@ go to a team of people, and
that the team promises to itself to reply-all, cc'ing the pr@ or info@
aliases in their reply. So list more than one target of the alias, or
use a private mailing list in Mailman.
>
> Regards
>
> On Wed, Nov 07, 2018 at 01:44:42AM +0100, Samson Goddy wrote:
> > Hello all,
> >
> > I am requesting for the permission to use info at sugarlabs dot org for
> > marketing purposes. The goal of this request is to use this email on
> social
> > media purposes.
> >
> > email: samsongoddy at gmail dot com
> >
> > Regards
> > --
> >
> > Samson Goddy
> >
> > Twitter: [1][4]https://twitter.com/samson_goddy
> > Email: [2][5]samsongoddy at sugarlabs.org
> > [3][6]samsongoddy at gmail.com
> >
> > Website: [4][7]https://samsongoddy.me/
> >
> > References:
> >
> > [1] [8]https://twitter.com/samson_goddy
> > [2] mailto:[9]samsongoddy at sugarlabs.org
> > [3] mailto:[10]samsongoddy at gmail.com
> > [4] [11]https://www.sugarlabs.org/
>
> > _______________________________________________
> > Systems mailing list
> > [12]Systems at lists.sugarlabs.org
> > [13]http://lists.sugarlabs.org/listinfo/systems
>
> --
> James Cameron
> [14]http://quozl.netrek.org/
>
> References:
>
> [1] mailto:quozl at laptop.org
> [2] mailto:d.crossland at gmail.com
> [3] mailto:marketing at lists.sugarlabs.org
> [4] https://twitter.com/samson_goddy
> [5] mailto:samsongoddy at sugarlabs.org
> [6] mailto:samsongoddy at gmail.com
> [7] https://samsongoddy.me/
> [8] https://twitter.com/samson_goddy
> [9] mailto:samsongoddy at sugarlabs.org
> [10] mailto:samsongoddy at gmail.com
> [11] https://www.sugarlabs.org/
> [12] mailto:Systems at lists.sugarlabs.org
> [13] http://lists.sugarlabs.org/listinfo/systems
> [14] http://quozl.netrek.org/
--
James Cameron
http://quozl.netrek.org/
More information about the Systems
mailing list