Hi all,
i'd like to note that the C4 process has a general bad actor handling mechanism as well. i vaguely recall there have been various instances to bully projects into stuff like the contributors covenant, so personally i`m against conduct template that are associated with zealots pushing for them aggressively. i will try to substantiate this claim/memory with actual data later today. in case i can*t follow up today please consider it without merit until a demonstration is provided. -- Ronny Am 31.07.2018 um 14:12 schrieb Dave Hunt: > https://www.contributor-covenant.org/version/1/4/code-of-conduct.html looks > like a good place to start. > >> On 31 Jul 2018, at 13:00, Bruno Oliveira <nicodde...@gmail.com >> <mailto:nicodde...@gmail.com>> wrote: >> >> Hi Dave, >> >> >> On Tue, Jul 31, 2018 at 8:54 AM Dave Hunt <dh...@mozilla.com >> <mailto:dh...@mozilla.com>> wrote: >> >> I’d like to add a code of conduct for my pytest plugins, and as >> they’re mostly under the pytest organisation on GitHub I thought >> it would make sense to use the same as the pytest project. I was >> surprised to find that the pytest project does not currently have >> a code of conduct according >> to https://github.com/pytest-dev/pytest/community. Is there one >> documented elsewhere? If not, which should we adopt? >> >> >> I'm a little surprised myself that we don't have one yet. I agree we >> should adopt one. Do you have a suggestion? >> >> Cheers, >> Bruno. > > > > _______________________________________________ > pytest-dev mailing list > pytest-dev@python.org > https://mail.python.org/mailman/listinfo/pytest-dev
_______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev