[Bigbang-dev] Bigbang-dev Digest, Vol 9, Issue 1

[Corinne Cath]

Hi Nick,

Thanks for taking the lead on this. The code seems very reasonable and
comprehensive. My only concern is around setting up an email address that
links back to the core developers. This might create a thorny situation if
the complaint is lodged against someone of that group.

Do you think there is any way around? For instance by picking 2 people that
deal with such issues? (Happy to volunteer btw).

Let me know what you think.

Kind regards,

Corinne


On Wed, Apr 4, 2018 at 12:00 PM, <bigbang-dev-request at data-activism.net>
wrote:

> Send Bigbang-dev mailing list submissions to
>         bigbang-dev at data-activism.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://emea01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Flists.ghserv.net%2Fmailman%2Flistinfo%
> 2Fbigbang-dev&data=02%7C01%7Cccath%40turing.ac.uk%
> 7Cf031f5613d6d4dfa485708d59a12f892%7C4395f4a7e4554f958a9f1fbaef63
> 84f9%7C0%7C1%7C636584328642499298&sdata=vXk4fM8QKtIVuabib0wwtTDzC4mlO8
> 9ypPNPuvN%2FcMg%3D&reserved=0
> or, via email, send a message with subject or body 'help' to
>         bigbang-dev-request at data-activism.net
>
> You can reach the person managing the list at
>         bigbang-dev-owner at data-activism.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Bigbang-dev digest..."
>
>
> Today's Topics:
>
>    1. BigBang project code of conduct (Nick Doty)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 3 Apr 2018 22:04:06 -0700
> From: Nick Doty <npdoty at ischool.berkeley.edu>
> To: bigbang-dev at data-activism.net
> Subject: [Bigbang-dev] BigBang project code of conduct
> Message-ID:
>         <7430B0DD-74E5-412D-919F-656F8AC45A72 at ischool.berkeley.edu>
> Content-Type: text/plain; charset="utf-8"
>
> In reviewing the community standards checklist on GitHub (thanks for the
> pointer, Seb), I was reminded that we don't have a documented Code of
> Conduct for our open source project. We are a small and friendly team, but
> I think committing now to a code of conduct is important, and makes it
> easier to invite new contributors and encourage a welcoming environment.
>
> GitHub recommends starting from this one:
> https://emea01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.contributor-covenant.org%2Fversion%2F1%
> 2F4%2Fcode-of-conduct.html&data=02%7C01%7Cccath%40turing.ac.uk%
> 7Cf031f5613d6d4dfa485708d59a12f892%7C4395f4a7e4554f958a9f1fbaef63
> 84f9%7C0%7C1%7C636584328642499298&sdata=CLd2Em2S6u77X1GuKfDO1MEnchJq3k
> 9NHJQ%2FQn7%2Fp0I%3D&reserved=0 <https://emea01.safelinks.
> protection.outlook.com/?url=https%3A%2F%2Fwww.contributor-
> covenant.org%2Fversion%2F1%2F4%2Fcode-of-conduct.html&
> data=02%7C01%7Cccath%40turing.ac.uk%7Cf031f5613d6d4dfa485708d59a12f892%
> 7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636584328642499298&sdata=
> CLd2Em2S6u77X1GuKfDO1MEnchJq3k9NHJQ%2FQn7%2Fp0I%3D&reserved=0>
> It's widely used and seems reasonable to me, so I suggest we go ahead with
> that if we're all comfortable committing to it.
>
> One issue: we need an email address where people can report problems of
> abusive behavior to the project team. That needs to be an email address
> that will be sent automatically to the core developers, but which
> specifically isn't publicly archived, as such reports need to be kept
> confidential while being investigated. So, it needs to be a separate list
> from bigbang-dev.
>
> Niels, do you want to set up another list @data-activism.net, maybe
> bigbang-owners? Or I think I can create a Berkeley list (through our
> special Google Groups install) and just manage the people invited to it and
> make sure it isn't archived.
>
> Once we have an email address set up, I'll open a pull request to add the
> Code of Conduct and update the README to point to it.
>
> Cheers,
> Nick
>
> P.S. Also, should we update the Core Developers list on the wiki?
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://emea01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Flists.ghserv.net%2Fpipermail%2Fbigbang-dev%
> 2Fattachments%2F20180403%2F2996e533%2Fattachment-0001.
> html&data=02%7C01%7Cccath%40turing.ac.uk%7Cf031f5613d6d4dfa485708d59a12
> f892%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%
> 7C636584328642499298&sdata=IriL0zBZrEbrCRzIjprMj6yncncvux
> XUsq00%2B3Bz7C8%3D&reserved=0>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 488 bytes
> Desc: Message signed with OpenPGP
> URL: <https://emea01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Flists.ghserv.net%2Fpipermail%2Fbigbang-dev%
> 2Fattachments%2F20180403%2F2996e533%2Fattachment-0001.
> sig&data=02%7C01%7Cccath%40turing.ac.uk%7Cf031f5613d6d4dfa485708d59a12
> f892%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%
> 7C636584328642499298&sdata=ec1YslIQykMxEixQhyQAZsd3q6fjkF
> WPHrw4NUu7HRw%3D&reserved=0>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Bigbang-dev mailing list
> Bigbang-dev at data-activism.net
> https://emea01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Flists.ghserv.net%2Fmailman%2Flistinfo%
> 2Fbigbang-dev&data=02%7C01%7Cccath%40turing.ac.uk%
> 7Cf031f5613d6d4dfa485708d59a12f892%7C4395f4a7e4554f958a9f1fbaef63
> 84f9%7C0%7C1%7C636584328642499298&sdata=vXk4fM8QKtIVuabib0wwtTDzC4mlO8
> 9ypPNPuvN%2FcMg%3D&reserved=0
>
>
> ------------------------------
>
> End of Bigbang-dev Digest, Vol 9, Issue 1
> *****************************************
>



-- 
Corinne Cath
Ph.D. Candidate, Oxford Internet Institute & Alan Turing Institute

Web: www.oii.ox.ac.uk/people/corinne-cath
Email: ccath at turing.ac.uk & corinnecath at gmail.com
Twitter: @C_Cath
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ghserv.net/pipermail/bigbang-dev/attachments/20180410/92b4d391/attachment-0001.html>