[Bigbang-dev] BigBang project code of conduct

[Nick Doty]

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://github.com/datactive/bigbang/pull/323 <https://github.com/datactive/bigbang/pull/323>

—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
> www.article19.org
> 
> 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://www.contributor-covenant.org/version/1/4/code-of-conduct.html
>> 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://lists.ghserv.net/mailman/listinfo/bigbang-dev
>> 
> 
> _______________________________________________
> 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/20180411/ca4839ab/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.ghserv.net/pipermail/bigbang-dev/attachments/20180411/ca4839ab/attachment.sig>