<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Hi Nick,</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">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. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Do you think there is any way around? For instance by picking 2 people that deal with such issues? (Happy to volunteer btw). </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Let me know what you think.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Kind regards,</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Corinne </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 4, 2018 at 12:00 PM, <span dir="ltr"><<a href="mailto:bigbang-dev-request@data-activism.net" target="_blank">bigbang-dev-request@data-activism.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Bigbang-dev mailing list submissions to<br>
<a href="mailto:bigbang-dev@data-activism.net">bigbang-dev@data-activism.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="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%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636584328642499298&sdata=vXk4fM8QKtIVuabib0wwtTDzC4mlO89ypPNPuvN%2FcMg%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.<wbr>protection.outlook.com/?url=<wbr>https%3A%2F%2Flists.ghserv.<wbr>net%2Fmailman%2Flistinfo%<wbr>2Fbigbang-dev&data=02%7C01%<wbr>7Cccath%40turing.ac.uk%<wbr>7Cf031f5613d6d4dfa485708d59a12<wbr>f892%<wbr>7C4395f4a7e4554f958a9f1fbaef63<wbr>84f9%7C0%7C1%<wbr>7C636584328642499298&sdata=<wbr>vXk4fM8QKtIVuabib0wwtTDzC4mlO8<wbr>9ypPNPuvN%2FcMg%3D&reserved=0</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:bigbang-dev-request@data-activism.net">bigbang-dev-request@data-<wbr>activism.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:bigbang-dev-owner@data-activism.net">bigbang-dev-owner@data-<wbr>activism.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Bigbang-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. BigBang project code of conduct (Nick Doty)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Tue, 3 Apr 2018 22:04:06 -0700<br>
From: Nick Doty <<a href="mailto:npdoty@ischool.berkeley.edu">npdoty@ischool.berkeley.edu</a>><br>
To: <a href="mailto:bigbang-dev@data-activism.net">bigbang-dev@data-activism.net</a><br>
Subject: [Bigbang-dev] BigBang project code of conduct<br>
Message-ID:<br>
<<a href="mailto:7430B0DD-74E5-412D-919F-656F8AC45A72@ischool.berkeley.edu">7430B0DD-74E5-412D-919F-<wbr>656F8AC45A72@ischool.berkeley.<wbr>edu</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
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.<br>
<br>
GitHub recommends starting from this one:<br>
<a href="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" rel="noreferrer" target="_blank">https://emea01.safelinks.<wbr>protection.outlook.com/?url=<wbr>https%3A%2F%2Fwww.contributor-<wbr>covenant.org%2Fversion%2F1%<wbr>2F4%2Fcode-of-conduct.html&<wbr>data=02%7C01%7Cccath%40turing.<wbr>ac.uk%<wbr>7Cf031f5613d6d4dfa485708d59a12<wbr>f892%<wbr>7C4395f4a7e4554f958a9f1fbaef63<wbr>84f9%7C0%7C1%<wbr>7C636584328642499298&sdata=<wbr>CLd2Em2S6u77X1GuKfDO1MEnchJq3k<wbr>9NHJQ%2FQn7%2Fp0I%3D&reserved=<wbr>0</a> <<a href="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" rel="noreferrer" target="_blank">https://emea01.safelinks.<wbr>protection.outlook.com/?url=<wbr>https%3A%2F%2Fwww.contributor-<wbr>covenant.org%2Fversion%2F1%<wbr>2F4%2Fcode-of-conduct.html&<wbr>data=02%7C01%7Cccath%40turing.<wbr>ac.uk%<wbr>7Cf031f5613d6d4dfa485708d59a12<wbr>f892%<wbr>7C4395f4a7e4554f958a9f1fbaef63<wbr>84f9%7C0%7C1%<wbr>7C636584328642499298&sdata=<wbr>CLd2Em2S6u77X1GuKfDO1MEnchJq3k<wbr>9NHJQ%2FQn7%2Fp0I%3D&reserved=<wbr>0</a>><br>
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.<br>
<br>
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.<br>
<br>
Niels, do you want to set up another list @<a href="http://data-activism.net" rel="noreferrer" target="_blank">data-activism.net</a>, 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.<br>
<br>
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.<br>
<br>
Cheers,<br>
Nick<br>
<br>
P.S. Also, should we update the Core Developers list on the wiki?<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="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%7Cf031f5613d6d4dfa485708d59a12f892%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636584328642499298&sdata=IriL0zBZrEbrCRzIjprMj6yncncvuxXUsq00%2B3Bz7C8%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.<wbr>protection.outlook.com/?url=<wbr>http%3A%2F%2Flists.ghserv.net%<wbr>2Fpipermail%2Fbigbang-dev%<wbr>2Fattachments%2F20180403%<wbr>2F2996e533%2Fattachment-0001.<wbr>html&data=02%7C01%7Cccath%<wbr>40turing.ac.uk%<wbr>7Cf031f5613d6d4dfa485708d59a12<wbr>f892%<wbr>7C4395f4a7e4554f958a9f1fbaef63<wbr>84f9%7C0%7C1%<wbr>7C636584328642499298&sdata=<wbr>IriL0zBZrEbrCRzIjprMj6yncncvux<wbr>XUsq00%2B3Bz7C8%3D&reserved=0</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 488 bytes<br>
Desc: Message signed with OpenPGP<br>
URL: <<a href="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%7Cf031f5613d6d4dfa485708d59a12f892%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636584328642499298&sdata=ec1YslIQykMxEixQhyQAZsd3q6fjkFWPHrw4NUu7HRw%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.<wbr>protection.outlook.com/?url=<wbr>http%3A%2F%2Flists.ghserv.net%<wbr>2Fpipermail%2Fbigbang-dev%<wbr>2Fattachments%2F20180403%<wbr>2F2996e533%2Fattachment-0001.<wbr>sig&data=02%7C01%7Cccath%<wbr>40turing.ac.uk%<wbr>7Cf031f5613d6d4dfa485708d59a12<wbr>f892%<wbr>7C4395f4a7e4554f958a9f1fbaef63<wbr>84f9%7C0%7C1%<wbr>7C636584328642499298&sdata=<wbr>ec1YslIQykMxEixQhyQAZsd3q6fjkF<wbr>WPHrw4NUu7HRw%3D&reserved=0</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
______________________________<wbr>_________________<br>
Bigbang-dev mailing list<br>
<a href="mailto:Bigbang-dev@data-activism.net">Bigbang-dev@data-activism.net</a><br>
<a href="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%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636584328642499298&sdata=vXk4fM8QKtIVuabib0wwtTDzC4mlO89ypPNPuvN%2FcMg%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.<wbr>protection.outlook.com/?url=<wbr>https%3A%2F%2Flists.ghserv.<wbr>net%2Fmailman%2Flistinfo%<wbr>2Fbigbang-dev&data=02%7C01%<wbr>7Cccath%40turing.ac.uk%<wbr>7Cf031f5613d6d4dfa485708d59a12<wbr>f892%<wbr>7C4395f4a7e4554f958a9f1fbaef63<wbr>84f9%7C0%7C1%<wbr>7C636584328642499298&sdata=<wbr>vXk4fM8QKtIVuabib0wwtTDzC4mlO8<wbr>9ypPNPuvN%2FcMg%3D&reserved=0</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Bigbang-dev Digest, Vol 9, Issue 1<br>
******************************<wbr>***********<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><span style="font-family:verdana,sans-serif">Corinne Cath <br>Ph.D. Candidate, Oxford Internet Institute & Alan Turing Institute <br><br><span style="color:rgb(68,68,68)">Web: <a href="http://www.oii.ox.ac.uk/people/corinne-cath" target="_blank">www.oii.ox.ac.uk/people/corinne-cath</a> <br>Email: <a href="mailto:ccath@turing.ac.uk" target="_blank">ccath@turing.ac.uk</a> & <a href="mailto:corinnecath@gmail.com" target="_blank">corinnecath@gmail.com</a><br>Twitter: @C_Cath</span><br></span></div></div></div></div></div></div></div></div></div></div></div></div>
</div>