[Systems] Access to info

James Cameron quozl at laptop.org
Wed Nov 7 21:11:28 EST 2018


On Thu, Nov 08, 2018 at 02:09:11AM +0100, Samson Goddy wrote:
> 
> On Thu, Nov 8, 2018 at 1:42 AM James Cameron <[1]quozl at laptop.org> wrote:
> 
>     On Wed, Nov 07, 2018 at 04:38:22AM +0100, Samson Goddy wrote:
>     >
>     > On Wed, Nov 7, 2018, 4:28 AM James Cameron <[1][2]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][3]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][4]
>     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?
> 
> Starting from today all Sugar Labs social account is attached with info@
> meaning anyone with access can reset password of those account. For now I want
> to be only me until I mean a trusted team for that access.
> 
> Then for PR@ this is the mail I plan using as a team for marketing related. PR@
> will go to team of people that can handle marketing (working on the creating a
> team of volunteers) but until then. Dave, Walter and I should all be as a team
> on PR@ 

Thanks.  Alias changed;

pr: d.crossland at gmail.com, samsongoddy, walter

> 
>     I'd like Sugar Labs to operate transparently as much as possible.
> 
> I also agree too. 
> 
>     [5]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][6]https://twitter.com/samson_goddy
>     >     >   Email: [2][5][7]samsongoddy at sugarlabs.org
>     >     >               [3][6][8]samsongoddy at gmail.com
>     >     >
>     >     >   Website: [4][7][9]https://samsongoddy.me/ 
>     >     >
>     >     > References:
>     >     >
>     >     > [1] [8][10]https://twitter.com/samson_goddy
>     >     > [2] mailto:[9][11]samsongoddy at sugarlabs.org
>     >     > [3] mailto:[10][12]samsongoddy at gmail.com
>     >     > [4] [11][13]https://www.sugarlabs.org/
>     >
>     >     > _______________________________________________
>     >     > Systems mailing list
>     >     > [12][14]Systems at lists.sugarlabs.org
>     >     > [13][15]http://lists.sugarlabs.org/listinfo/systems
>     >
>     >     --
>     >     James Cameron
>     >     [14][16]http://quozl.netrek.org/
>     >
>     > References:
>     >
>     > [1] mailto:[17]quozl at laptop.org
>     > [2] mailto:[18]d.crossland at gmail.com
>     > [3] mailto:[19]marketing at lists.sugarlabs.org
>     > [4] [20]https://twitter.com/samson_goddy
>     > [5] mailto:[21]samsongoddy at sugarlabs.org
>     > [6] mailto:[22]samsongoddy at gmail.com
>     > [7] [23]https://samsongoddy.me/
>     > [8] [24]https://twitter.com/samson_goddy
>     > [9] mailto:[25]samsongoddy at sugarlabs.org
>     > [10] mailto:[26]samsongoddy at gmail.com
>     > [11] [27]https://www.sugarlabs.org/
>     > [12] mailto:[28]Systems at lists.sugarlabs.org
>     > [13] [29]http://lists.sugarlabs.org/listinfo/systems
>     > [14] [30]http://quozl.netrek.org/
> 
>     --
>     James Cameron
>     [31]http://quozl.netrek.org/
> 
> --
> 
>   Samson Goddy
> 
>   Twitter: [32]https://twitter.com/samson_goddy
>   Email: [33]samsongoddy at sugarlabs.org
>               [34]samsongoddy at gmail.com
> 
>   Website: [35]https://samsongoddy.me/ 
> 
> References:
> 
> [1] mailto:quozl at laptop.org
> [2] mailto:quozl at laptop.org
> [3] mailto:d.crossland at gmail.com
> [4] mailto:marketing at lists.sugarlabs.org
> [5] https://en.wikipedia.org/wiki/Transparency_(behavior)
> [6] https://twitter.com/samson_goddy
> [7] mailto:samsongoddy at sugarlabs.org
> [8] mailto:samsongoddy at gmail.com
> [9] https://samsongoddy.me/
> [10] https://twitter.com/samson_goddy
> [11] mailto:samsongoddy at sugarlabs.org
> [12] mailto:samsongoddy at gmail.com
> [13] https://www.sugarlabs.org/
> [14] mailto:Systems at lists.sugarlabs.org
> [15] http://lists.sugarlabs.org/listinfo/systems
> [16] http://quozl.netrek.org/
> [17] mailto:quozl at laptop.org
> [18] mailto:d.crossland at gmail.com
> [19] mailto:marketing at lists.sugarlabs.org
> [20] https://twitter.com/samson_goddy
> [21] mailto:samsongoddy at sugarlabs.org
> [22] mailto:samsongoddy at gmail.com
> [23] https://samsongoddy.me/
> [24] https://twitter.com/samson_goddy
> [25] mailto:samsongoddy at sugarlabs.org
> [26] mailto:samsongoddy at gmail.com
> [27] https://www.sugarlabs.org/
> [28] mailto:Systems at lists.sugarlabs.org
> [29] http://lists.sugarlabs.org/listinfo/systems
> [30] http://quozl.netrek.org/
> [31] http://quozl.netrek.org/
> [32] https://twitter.com/samson_goddy
> [33] mailto:samsongoddy at sugarlabs.org
> [34] mailto:samsongoddy at gmail.com
> [35] https://www.sugarlabs.org/

-- 
James Cameron
http://quozl.netrek.org/


More information about the Systems mailing list