<div dir="ltr">Hi Corinne,<div><br></div><div>Thank you for the thoughtful suggestion. It is very well taken.</div><div><br></div><div>I want to make a couple points of clarification before addressing your main point.</div><div><br></div><div>1) "Core Developers" is a specific role that's defined in our governance document, which is itself based on FOSS community best practices.</div><div><br></div><div><a href="https://github.com/datactive/bigbang/wiki/Governance#core-developers">https://github.com/datactive/bigbang/wiki/Governance#core-developers</a><br></div><div><br></div><div>The idea is that this role extends gradually to those who make significant software contributions to the project. This is partly to incentive contributions and make sure that control over the project is in the hands of whoever knows best how it actually works and can maintain and improve its functionality going forward.</div><div><br></div><div>Currently, Nick Doty and myself are the only active Core Developers. The other core developer, Aryan, is inactive.</div><div>In my own view (which may not be held by everyone), eligibility for Core Developer status comes with having made substantive development contributions to the project. These can be roughly tracked with GitHub's Contributors visualization here:</div><div><br></div><div><a href="https://github.com/datactive/bigbang/graphs/contributors">https://github.com/datactive/bigbang/graphs/contributors</a><br></div><div><br></div><div>2) The Enforcement clause of the code of conduct says that enforcement requests go "the project team". I see that Niels has set up the bigbang-owners list to include himself and Davide. That's entirely appropriate because Niels and Davide have, as our DATACTIVE partners, have provided infrastructural and other support for the project and are definitely part of "the team".</div><div><br></div><div>I have to agree, though, that having what's essentially a more private, less accountable mailing list to discuss code of conduct violations with the same group of people, especially one so imbalanced in gender, seems less than ideal.</div><div><br></div><div>At the same time, I have say that having a code of conduct review group that includes somebody who is otherwise inactive in the project seems awkward to me.</div><div><br></div><div>In an ideal world, Corinne would be BOTH an active contributor to the project in some capacity AND be somebody who could be contacted about code of conduct violations, should they ever happen (which I hope is very, very rarely).</div><div><br></div><div>Is that ideal world possible?</div><div><br></div><div>Best regards,</div><div>Seb</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 12, 2018 at 11:58 AM, Corinne Cath <span dir="ltr"><<a href="mailto:corinnecath@gmail.com" target="_blank">corinnecath@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif"><div class="gmail_default" style="color:rgb(34,34,34);font-family:verdana,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)">Hi both,</div><div class="gmail_default" style="color:rgb(34,34,34);font-family:verdana,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><br></div><div class="gmail_default" style="color:rgb(34,34,34);font-family:verdana,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)">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 and also sending a complaint to four dudes might make some people uncomfortable. </div><div class="gmail_default" style="color:rgb(34,34,34);font-family:verdana,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><br></div><div class="gmail_default" style="color:rgb(34,34,34);font-family:verdana,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)">Do you think there is any way around? For instance by picking 2 people that deal with such issues and making sure there is a bit of a gender balance there? (Happy to volunteer btw). </div><div class="gmail_default" style="color:rgb(34,34,34);font-family:verdana,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><br></div><div class="gmail_default" style="color:rgb(34,34,34);font-family:verdana,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)">Let me know what you think.</div><div class="gmail_default" style="color:rgb(34,34,34);font-family:verdana,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><br></div><div class="gmail_default" style="color:rgb(34,34,34);font-family:verdana,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)">Kind regards,</div><div class="gmail_default" style="color:rgb(34,34,34);font-family:verdana,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><br></div><div class="gmail_default" style="color:rgb(34,34,34);font-family:verdana,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)">Corinne </div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 12, 2018 at 12:00 PM, <span dir="ltr"><<a href="mailto:bigbang-dev-request@data-activism.net" target="_blank">bigbang-dev-request@data-<wbr>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" target="_blank">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%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=Js0rlaAyGoFDorqLuxdq%2B20sFrVee9SDQ3UY8w0iuBA%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.prote<wbr>ction.outlook.com/?url=https%<wbr>3A%2F%2Flists.ghserv.net%<wbr>2Fmailman%2Flistinfo%2Fbigbang<wbr>-dev&data=02%7C01%7Cccath%<wbr>40turing.ac.uk%7C9979defac3cd4<wbr>871184d08d5a05c48b4%7C4395f4a7<wbr>e4554f958a9f1fbaef6384f9%7C0%<wbr>7C1%7C636591240576869803&<wbr>sdata=Js0rlaAyGoFDorqLuxdq%2B2<wbr>0sFrVee9SDQ3UY8w0iuBA%3D&reser<wbr>ved=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" target="_blank">bigbang-dev-request@data-activ<wbr>ism.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:bigbang-dev-owner@data-activism.net" target="_blank">bigbang-dev-owner@data-activis<wbr>m.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. Re: BigBang project code of conduct (Niels ten Oever)<br>
2. Re: BigBang project code of conduct (Nick Doty)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Wed, 11 Apr 2018 16:18:46 +0200<br>
From: Niels ten Oever <<a href="mailto:niels@article19.org" target="_blank">niels@article19.org</a>><br>
To: <a href="mailto:bigbang-dev@data-activism.net" target="_blank">bigbang-dev@data-activism.net</a><br>
Subject: Re: [Bigbang-dev] BigBang project code of conduct<br>
Message-ID: <<a href="mailto:db9fbc11-d4c9-0811-5664-f0d4f7bf5828@article19.org" target="_blank">db9fbc11-d4c9-0811-5664-f0d4f<wbr>7bf5828@article19.org</a>><br>
Content-Type: text/plain; charset="windows-1252"<br>
<br>
Hi all,<br>
<br>
I created <a href="mailto:bigbang-owners@data-activism.net" target="_blank">bigbang-owners@data-activism.n<wbr>et</a> and have added Sebastian,<br>
Nick, Davide and myself as list-admins and moderators.<br>
<br>
I have switched off the archiving and made it a private list.<br>
<br>
The community guidelines look good, so I think we're good to go!<br>
<br>
Cheers,<br>
<br>
Niels<br>
<br>
Niels ten Oever<br>
<br>
Article 19<br>
<a href="https://emea01.safelinks.protection.outlook.com/?url=www.article19.org&data=02%7C01%7Cccath%40turing.ac.uk%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=RmuPjFKnquDbpiLK3D8c%2FHrYE7gUjtVLjCPsvkeqTXc%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.prote<wbr>ction.outlook.com/?url=www.<wbr>article19.org&data=02%7C01%<wbr>7Cccath%40turing.ac.uk%7C9979d<wbr>efac3cd4871184d08d5a05c48b4%7C<wbr>4395f4a7e4554f958a9f1fbaef6384<wbr>f9%7C0%7C1%7C63659124057686980<wbr>3&sdata=RmuPjFKnquDbpiLK3D8c%2<wbr>FHrYE7gUjtVLjCPsvkeqTXc%3D&res<wbr>erved=0</a><br>
<br>
PGP fingerprint 2458 0B70 5C4A FD8A 9488<br>
643A 0ED8 3F3A 468A C8B3<br>
<br>
On 04/04/2018 07:04 AM, Nick Doty wrote:<br>
> In reviewing the community standards checklist on GitHub (thanks for the<br>
> pointer, Seb), I was reminded that we don't have a documented Code of<br>
> Conduct for our open source project. We are a small and friendly team,<br>
> but I think committing now to a code of conduct is important, and makes<br>
> 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%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=i92GNRo%2Fj5JJgN1jGWoHcVsEnSi1Av6chMYe0zhIVLA%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.prote<wbr>ction.outlook.com/?url=https%<wbr>3A%2F%2Fwww.contributor-covena<wbr>nt.org%2Fversion%2F1%2F4%<wbr>2Fcode-of-conduct.html&data=<wbr>02%7C01%7Cccath%40turing.ac.<wbr>uk%7C9979defac3cd4871184d08d5a<wbr>05c48b4%7C4395f4a7e4554f958a9f<wbr>1fbaef6384f9%7C0%7C1%7C6365912<wbr>40576869803&sdata=i92GNRo%2Fj5<wbr>JJgN1jGWoHcVsEnSi1Av6chMYe0zhI<wbr>VLA%3D&reserved=0</a><br>
> It's widely used and seems reasonable to me, so I suggest we go ahead<br>
> 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<br>
> abusive behavior to the project team. That needs to be an email address<br>
> that will be sent automatically to the core developers, but which<br>
> specifically isn't publicly archived, as such reports need to be kept<br>
> confidential while being investigated. So, it needs to be a separate<br>
> 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<br>
> bigbang-owners? Or I think I can create a Berkeley list (through our<br>
> special Google Groups install) and just manage the people invited to it<br>
> 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<br>
> 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>
><br>
><br>
> ______________________________<wbr>_________________<br>
> Bigbang-dev mailing list<br>
> <a href="mailto:Bigbang-dev@data-activism.net" target="_blank">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%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=Js0rlaAyGoFDorqLuxdq%2B20sFrVee9SDQ3UY8w0iuBA%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.prote<wbr>ction.outlook.com/?url=https%<wbr>3A%2F%2Flists.ghserv.net%<wbr>2Fmailman%2Flistinfo%2Fbigbang<wbr>-dev&data=02%7C01%7Cccath%<wbr>40turing.ac.uk%7C9979defac3cd4<wbr>871184d08d5a05c48b4%7C4395f4a7<wbr>e4554f958a9f1fbaef6384f9%7C0%<wbr>7C1%7C636591240576869803&<wbr>sdata=Js0rlaAyGoFDorqLuxdq%2B2<wbr>0sFrVee9SDQ3UY8w0iuBA%3D&reser<wbr>ved=0</a><br>
><br>
<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 833 bytes<br>
Desc: OpenPGP digital signature<br>
URL: <<a href="https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.ghserv.net%2Fpipermail%2Fbigbang-dev%2Fattachments%2F20180411%2F0cc31b04%2Fattachment-0001.sig&data=02%7C01%7Cccath%40turing.ac.uk%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=gMUOHllsFoTE7meeexe4xfZBf1GvfF40AZa7VnqO46o%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.prot<wbr>ection.outlook.com/?url=http%<wbr>3A%2F%2Flists.ghserv.net%2Fpip<wbr>ermail%2Fbigbang-dev%2Fattachm<wbr>ents%2F20180411%2F0cc31b04%<wbr>2Fattachment-0001.sig&data=02%<wbr>7C01%7Cccath%40turing.ac.uk%7C<wbr>9979defac3cd4871184d08d5a05c48<wbr>b4%7C4395f4a7e4554f958a9f1fbae<wbr>f6384f9%7C0%7C1%7C636591240576<wbr>869803&sdata=gMUOHllsFoTE7meee<wbr>xe4xfZBf1GvfF40AZa7VnqO46o%3D&<wbr>reserved=0</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 11 Apr 2018 13:55:25 -0700<br>
From: Nick Doty <<a href="mailto:npdoty@ischool.berkeley.edu" target="_blank">npdoty@ischool.berkeley.edu</a>><br>
To: Niels ten Oever <<a href="mailto:niels@article19.org" target="_blank">niels@article19.org</a>><br>
Cc: <a href="mailto:bigbang-dev@data-activism.net" target="_blank">bigbang-dev@data-activism.net</a><br>
Subject: Re: [Bigbang-dev] BigBang project code of conduct<br>
Message-ID:<br>
<<a href="mailto:EB0DA9F2-9237-463F-8853-7935732163AC@ischool.berkeley.edu" target="_blank">EB0DA9F2-9237-463F-8853-79357<wbr>32163AC@ischool.berkeley.edu</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Thanks, Niels!<br>
<br>
Someone can look over my work, but I've added the code of conduct and a link to it from the readme in this PR:<br>
<a href="https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdatactive%2Fbigbang%2Fpull%2F323&data=02%7C01%7Cccath%40turing.ac.uk%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=noqXDAxhH0hFLdNbBS5hkfCeeT%2BVZ5PZ7KPrQEu1vls%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.prote<wbr>ction.outlook.com/?url=https%<wbr>3A%2F%2Fgithub.com%2Fdatactive<wbr>%2Fbigbang%2Fpull%2F323&data=<wbr>02%7C01%7Cccath%40turing.ac.<wbr>uk%7C9979defac3cd4871184d08d5a<wbr>05c48b4%7C4395f4a7e4554f958a9f<wbr>1fbaef6384f9%7C0%7C1%7C6365912<wbr>40576869803&sdata=noqXDAxhH0hF<wbr>LdNbBS5hkfCeeT%2BVZ5PZ7KPrQEu1<wbr>vls%3D&reserved=0</a> <<a href="https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdatactive%2Fbigbang%2Fpull%2F323&data=02%7C01%7Cccath%40turing.ac.uk%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=noqXDAxhH0hFLdNbBS5hkfCeeT%2BVZ5PZ7KPrQEu1vls%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.prot<wbr>ection.outlook.com/?url=https%<wbr>3A%2F%2Fgithub.com%2Fdatactive<wbr>%2Fbigbang%2Fpull%2F323&data=<wbr>02%7C01%7Cccath%40turing.ac.<wbr>uk%7C9979defac3cd4871184d08d5a<wbr>05c48b4%7C4395f4a7e4554f958a9f<wbr>1fbaef6384f9%7C0%7C1%7C6365912<wbr>40576869803&sdata=noqXDAxhH0hF<wbr>LdNbBS5hkfCeeT%2BVZ5PZ7KPrQEu1<wbr>vls%3D&reserved=0</a>><br>
<br>
—Nick<br>
[sending from correct email address]<br>
<br>
> On Apr 11, 2018, at 7:18 AM, Niels ten Oever <<a href="mailto:niels@article19.org" target="_blank">niels@article19.org</a>> wrote:<br>
><br>
> Hi all,<br>
><br>
> I created <a href="mailto:bigbang-owners@data-activism.net" target="_blank">bigbang-owners@data-activism.n<wbr>et</a> and have added Sebastian,<br>
> Nick, Davide and myself as list-admins and moderators.<br>
><br>
> I have switched off the archiving and made it a private list.<br>
><br>
> The community guidelines look good, so I think we're good to go!<br>
><br>
> Cheers,<br>
><br>
> Niels<br>
><br>
> Niels ten Oever<br>
><br>
> Article 19<br>
> <a href="https://emea01.safelinks.protection.outlook.com/?url=www.article19.org&data=02%7C01%7Cccath%40turing.ac.uk%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=RmuPjFKnquDbpiLK3D8c%2FHrYE7gUjtVLjCPsvkeqTXc%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.prote<wbr>ction.outlook.com/?url=www.<wbr>article19.org&data=02%7C01%<wbr>7Cccath%40turing.ac.uk%7C9979d<wbr>efac3cd4871184d08d5a05c48b4%7C<wbr>4395f4a7e4554f958a9f1fbaef6384<wbr>f9%7C0%7C1%7C63659124057686980<wbr>3&sdata=RmuPjFKnquDbpiLK3D8c%2<wbr>FHrYE7gUjtVLjCPsvkeqTXc%3D&res<wbr>erved=0</a><br>
><br>
> PGP fingerprint 2458 0B70 5C4A FD8A 9488<br>
> 643A 0ED8 3F3A 468A C8B3<br>
><br>
> On 04/04/2018 07:04 AM, Nick Doty wrote:<br>
>> In reviewing the community standards checklist on GitHub (thanks for the<br>
>> pointer, Seb), I was reminded that we don't have a documented Code of<br>
>> Conduct for our open source project. We are a small and friendly team,<br>
>> but I think committing now to a code of conduct is important, and makes<br>
>> 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%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=i92GNRo%2Fj5JJgN1jGWoHcVsEnSi1Av6chMYe0zhIVLA%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.prote<wbr>ction.outlook.com/?url=https%<wbr>3A%2F%2Fwww.contributor-covena<wbr>nt.org%2Fversion%2F1%2F4%<wbr>2Fcode-of-conduct.html&data=<wbr>02%7C01%7Cccath%40turing.ac.<wbr>uk%7C9979defac3cd4871184d08d5a<wbr>05c48b4%7C4395f4a7e4554f958a9f<wbr>1fbaef6384f9%7C0%7C1%7C6365912<wbr>40576869803&sdata=i92GNRo%2Fj5<wbr>JJgN1jGWoHcVsEnSi1Av6chMYe0zhI<wbr>VLA%3D&reserved=0</a><br>
>> It's widely used and seems reasonable to me, so I suggest we go ahead<br>
>> 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<br>
>> abusive behavior to the project team. That needs to be an email address<br>
>> that will be sent automatically to the core developers, but which<br>
>> specifically isn't publicly archived, as such reports need to be kept<br>
>> confidential while being investigated. So, it needs to be a separate<br>
>> 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<br>
>> bigbang-owners? Or I think I can create a Berkeley list (through our<br>
>> special Google Groups install) and just manage the people invited to it<br>
>> 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<br>
>> 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>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> Bigbang-dev mailing list<br>
>> <a href="mailto:Bigbang-dev@data-activism.net" target="_blank">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%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=Js0rlaAyGoFDorqLuxdq%2B20sFrVee9SDQ3UY8w0iuBA%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.prote<wbr>ction.outlook.com/?url=https%<wbr>3A%2F%2Flists.ghserv.net%<wbr>2Fmailman%2Flistinfo%2Fbigbang<wbr>-dev&data=02%7C01%7Cccath%<wbr>40turing.ac.uk%7C9979defac3cd4<wbr>871184d08d5a05c48b4%7C4395f4a7<wbr>e4554f958a9f1fbaef6384f9%7C0%<wbr>7C1%7C636591240576869803&<wbr>sdata=Js0rlaAyGoFDorqLuxdq%2B2<wbr>0sFrVee9SDQ3UY8w0iuBA%3D&reser<wbr>ved=0</a><br>
>><br>
><br>
> ______________________________<wbr>_________________<br>
> Bigbang-dev mailing list<br>
> <a href="mailto:Bigbang-dev@data-activism.net" target="_blank">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%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=Js0rlaAyGoFDorqLuxdq%2B20sFrVee9SDQ3UY8w0iuBA%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.prote<wbr>ction.outlook.com/?url=https%<wbr>3A%2F%2Flists.ghserv.net%<wbr>2Fmailman%2Flistinfo%2Fbigbang<wbr>-dev&data=02%7C01%7Cccath%<wbr>40turing.ac.uk%7C9979defac3cd4<wbr>871184d08d5a05c48b4%7C4395f4a7<wbr>e4554f958a9f1fbaef6384f9%7C0%<wbr>7C1%7C636591240576869803&<wbr>sdata=Js0rlaAyGoFDorqLuxdq%2B2<wbr>0sFrVee9SDQ3UY8w0iuBA%3D&reser<wbr>ved=0</a><br>
<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%2F20180411%2Fca4839ab%2Fattachment-0001.html&data=02%7C01%7Cccath%40turing.ac.uk%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=YCVH4WhHHI7V%2BfMh%2Fh%2BcVSpKI7H2gUjLlCF6leR6NNQ%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.prot<wbr>ection.outlook.com/?url=http%<wbr>3A%2F%2Flists.ghserv.net%2Fpip<wbr>ermail%2Fbigbang-dev%2Fattachm<wbr>ents%2F20180411%2Fca4839ab%<wbr>2Fattachment-0001.html&data=<wbr>02%7C01%7Cccath%40turing.ac.<wbr>uk%7C9979defac3cd4871184d08d5a<wbr>05c48b4%7C4395f4a7e4554f958a9f<wbr>1fbaef6384f9%7C0%7C1%7C6365912<wbr>40576869803&sdata=YCVH4WhHHI7V<wbr>%2BfMh%2Fh%2BcVSpKI7H2gUjLlCF6<wbr>leR6NNQ%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%2F20180411%2Fca4839ab%2Fattachment-0001.sig&data=02%7C01%7Cccath%40turing.ac.uk%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=YVhp3VQM8dhFSBimj19yIeP%2Bq2NpDBtgos1m1fW4qEI%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.prot<wbr>ection.outlook.com/?url=http%<wbr>3A%2F%2Flists.ghserv.net%2Fpip<wbr>ermail%2Fbigbang-dev%2Fattachm<wbr>ents%2F20180411%2Fca4839ab%<wbr>2Fattachment-0001.sig&data=02%<wbr>7C01%7Cccath%40turing.ac.uk%7C<wbr>9979defac3cd4871184d08d5a05c48<wbr>b4%7C4395f4a7e4554f958a9f1fbae<wbr>f6384f9%7C0%7C1%7C636591240576<wbr>869803&sdata=YVhp3VQM8dhFSBimj<wbr>19yIeP%2Bq2NpDBtgos1m1fW4qEI%<wbr>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" target="_blank">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%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=Js0rlaAyGoFDorqLuxdq%2B20sFrVee9SDQ3UY8w0iuBA%3D&reserved=0" rel="noreferrer" target="_blank">https://emea01.safelinks.prote<wbr>ction.outlook.com/?url=https%<wbr>3A%2F%2Flists.ghserv.net%<wbr>2Fmailman%2Flistinfo%2Fbigbang<wbr>-dev&data=02%7C01%7Cccath%<wbr>40turing.ac.uk%7C9979defac3cd4<wbr>871184d08d5a05c48b4%7C4395f4a7<wbr>e4554f958a9f1fbaef6384f9%7C0%<wbr>7C1%7C636591240576869803&<wbr>sdata=Js0rlaAyGoFDorqLuxdq%2B2<wbr>0sFrVee9SDQ3UY8w0iuBA%3D&reser<wbr>ved=0</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Bigbang-dev Digest, Vol 9, Issue 2<br>
******************************<wbr>***********<span class="HOEnZb"><font color="#888888"><br>
</font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div class="m_3127858426455947040gmail_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/<wbr>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>
</font></span></div>
<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://lists.ghserv.net/mailman/listinfo/bigbang-dev" rel="noreferrer" target="_blank">https://lists.ghserv.net/<wbr>mailman/listinfo/bigbang-dev</a><br>
<br></blockquote></div><br></div>