[Bigbang-dev] Bigbang-dev Digest, Vol 9, Issue 2
Sebastian Benthall
sbenthall at gmail.com
Thu Apr 12 22:32:10 CEST 2018
Hi Corinne,
Thank you for the thoughtful suggestion. It is very well taken.
I want to make a couple points of clarification before addressing your main
point.
1) "Core Developers" is a specific role that's defined in our governance
document, which is itself based on FOSS community best practices.
https://github.com/datactive/bigbang/wiki/Governance#core-developers
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.
Currently, Nick Doty and myself are the only active Core Developers. The
other core developer, Aryan, is inactive.
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:
https://github.com/datactive/bigbang/graphs/contributors
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".
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.
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.
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).
Is that ideal world possible?
Best regards,
Seb
On Thu, Apr 12, 2018 at 11:58 AM, Corinne Cath <corinnecath at gmail.com>
wrote:
> Hi both,
>
> 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.
>
> 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).
>
> Let me know what you think.
>
> Kind regards,
>
> Corinne
>
>
> On Thu, Apr 12, 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%7C9979defac3cd4
>> 871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%
>> 7C1%7C636591240576869803&sdata=Js0rlaAyGoFDorqLuxdq%2B2
>> 0sFrVee9SDQ3UY8w0iuBA%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. Re: BigBang project code of conduct (Niels ten Oever)
>> 2. Re: BigBang project code of conduct (Nick Doty)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Wed, 11 Apr 2018 16:18:46 +0200
>> From: Niels ten Oever <niels at article19.org>
>> To: bigbang-dev at data-activism.net
>> Subject: Re: [Bigbang-dev] BigBang project code of conduct
>> Message-ID: <db9fbc11-d4c9-0811-5664-f0d4f7bf5828 at article19.org>
>> Content-Type: text/plain; charset="windows-1252"
>>
>> Hi all,
>>
>> I created bigbang-owners at data-activism.net and have added Sebastian,
>> Nick, Davide and myself as list-admins and moderators.
>>
>> I have switched off the archiving and made it a private list.
>>
>> The community guidelines look good, so I think we're good to go!
>>
>> Cheers,
>>
>> Niels
>>
>> Niels ten Oever
>>
>> Article 19
>> https://emea01.safelinks.protection.outlook.com/?url=www.
>> article19.org&data=02%7C01%7Cccath%40turing.ac.uk%7C9979d
>> efac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384
>> f9%7C0%7C1%7C636591240576869803&sdata=RmuPjFKnquDbpiLK3D8c%2
>> FHrYE7gUjtVLjCPsvkeqTXc%3D&reserved=0
>>
>> PGP fingerprint 2458 0B70 5C4A FD8A 9488
>> 643A 0ED8 3F3A 468A C8B3
>>
>> On 04/04/2018 07:04 AM, Nick Doty wrote:
>> > 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%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f
>> 1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=i92GNRo%2Fj5
>> JJgN1jGWoHcVsEnSi1Av6chMYe0zhIVLA%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?
>> >
>> >
>> > _______________________________________________
>> > 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%7C9979defac3cd4
>> 871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%
>> 7C1%7C636591240576869803&sdata=Js0rlaAyGoFDorqLuxdq%2B2
>> 0sFrVee9SDQ3UY8w0iuBA%3D&reserved=0
>> >
>>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: signature.asc
>> Type: application/pgp-signature
>> Size: 833 bytes
>> Desc: OpenPGP digital signature
>> URL: <https://emea01.safelinks.protection.outlook.com/?url=http%
>> 3A%2F%2Flists.ghserv.net%2Fpipermail%2Fbigbang-dev%2Fattachm
>> ents%2F20180411%2F0cc31b04%2Fattachment-0001.sig&data=02%
>> 7C01%7Cccath%40turing.ac.uk%7C9979defac3cd4871184d08d5a05c48
>> b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576
>> 869803&sdata=gMUOHllsFoTE7meeexe4xfZBf1GvfF40AZa7VnqO46o%3D&reserved=0>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Wed, 11 Apr 2018 13:55:25 -0700
>> From: Nick Doty <npdoty at ischool.berkeley.edu>
>> To: Niels ten Oever <niels at article19.org>
>> Cc: bigbang-dev at data-activism.net
>> Subject: Re: [Bigbang-dev] BigBang project code of conduct
>> Message-ID:
>> <EB0DA9F2-9237-463F-8853-7935732163AC at ischool.berkeley.edu>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Thanks, Niels!
>>
>> 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:
>> https://emea01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fgithub.com%2Fdatactive%2Fbigbang%2Fpull%2F323&data=
>> 02%7C01%7Cccath%40turing.ac.uk%7C9979defac3cd4871184d08d5a
>> 05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C6365912
>> 40576869803&sdata=noqXDAxhH0hFLdNbBS5hkfCeeT%2BVZ5PZ7KPrQEu1
>> vls%3D&reserved=0 <https://emea01.safelinks.prot
>> ection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdatactive
>> %2Fbigbang%2Fpull%2F323&data=02%7C01%7Cccath%40turing.ac.
>> uk%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f
>> 1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=noqXDAxhH0hF
>> LdNbBS5hkfCeeT%2BVZ5PZ7KPrQEu1vls%3D&reserved=0>
>>
>> —Nick
>> [sending from correct email address]
>>
>> > On Apr 11, 2018, at 7:18 AM, Niels ten Oever <niels at article19.org>
>> wrote:
>> >
>> > Hi all,
>> >
>> > I created bigbang-owners at data-activism.net and have added Sebastian,
>> > Nick, Davide and myself as list-admins and moderators.
>> >
>> > I have switched off the archiving and made it a private list.
>> >
>> > The community guidelines look good, so I think we're good to go!
>> >
>> > Cheers,
>> >
>> > Niels
>> >
>> > Niels ten Oever
>> >
>> > Article 19
>> > https://emea01.safelinks.protection.outlook.com/?url=www.
>> article19.org&data=02%7C01%7Cccath%40turing.ac.uk%7C9979d
>> efac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384
>> f9%7C0%7C1%7C636591240576869803&sdata=RmuPjFKnquDbpiLK3D8c%2
>> FHrYE7gUjtVLjCPsvkeqTXc%3D&reserved=0
>> >
>> > PGP fingerprint 2458 0B70 5C4A FD8A 9488
>> > 643A 0ED8 3F3A 468A C8B3
>> >
>> > On 04/04/2018 07:04 AM, Nick Doty wrote:
>> >> 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%7C9979defac3cd4871184d08d5a05c48b4%7C4395f4a7e4554f958a9f
>> 1fbaef6384f9%7C0%7C1%7C636591240576869803&sdata=i92GNRo%2Fj5
>> JJgN1jGWoHcVsEnSi1Av6chMYe0zhIVLA%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?
>> >>
>> >>
>> >> _______________________________________________
>> >> 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%7C9979defac3cd4
>> 871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%
>> 7C1%7C636591240576869803&sdata=Js0rlaAyGoFDorqLuxdq%2B2
>> 0sFrVee9SDQ3UY8w0iuBA%3D&reserved=0
>> >>
>> >
>> > _______________________________________________
>> > 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%7C9979defac3cd4
>> 871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%
>> 7C1%7C636591240576869803&sdata=Js0rlaAyGoFDorqLuxdq%2B2
>> 0sFrVee9SDQ3UY8w0iuBA%3D&reserved=0
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <https://emea01.safelinks.protection.outlook.com/?url=http%
>> 3A%2F%2Flists.ghserv.net%2Fpipermail%2Fbigbang-dev%2Fattachm
>> ents%2F20180411%2Fca4839ab%2Fattachment-0001.html&data=
>> 02%7C01%7Cccath%40turing.ac.uk%7C9979defac3cd4871184d08d5a
>> 05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C6365912
>> 40576869803&sdata=YCVH4WhHHI7V%2BfMh%2Fh%2BcVSpKI7H2gUjLlCF6
>> leR6NNQ%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%2Fattachm
>> ents%2F20180411%2Fca4839ab%2Fattachment-0001.sig&data=02%
>> 7C01%7Cccath%40turing.ac.uk%7C9979defac3cd4871184d08d5a05c48
>> b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%7C1%7C636591240576
>> 869803&sdata=YVhp3VQM8dhFSBimj19yIeP%2Bq2NpDBtgos1m1fW4qEI%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%7C9979defac3cd4
>> 871184d08d5a05c48b4%7C4395f4a7e4554f958a9f1fbaef6384f9%7C0%
>> 7C1%7C636591240576869803&sdata=Js0rlaAyGoFDorqLuxdq%2B2
>> 0sFrVee9SDQ3UY8w0iuBA%3D&reserved=0
>>
>>
>> ------------------------------
>>
>> End of Bigbang-dev Digest, Vol 9, Issue 2
>> *****************************************
>>
>
>
>
> --
> 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
>
> _______________________________________________
> Bigbang-dev mailing list
> Bigbang-dev at data-activism.net
> https://lists.ghserv.net/mailman/listinfo/bigbang-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ghserv.net/pipermail/bigbang-dev/attachments/20180412/298292ff/attachment-0001.html>
More information about the Bigbang-dev
mailing list