Re: [pytest-dev] Code of conduct for pytest organisation on GitHub

[Oliver Bestwalter]

Hi,

I was following along and will propose the same for tox where I will also
volunteer as a contact, so might as well volunteer here.

Would be great though if there also was a female person available for
contact (if possible then also for tox, if we do thr same there).

Cheers,
Oliver
On Sat 4. Aug 2018 at 15:00, Bruno Oliveira  wrote:

> Feel free to add me as well Florian.
>
> []s
>
> On Sat, Aug 4, 2018 at 8:58 AM RonnyPfannschmidt <
> opensou...@ronnypfannschmidt.de> wrote:
>
>> Hi,
>>
>> pytest+...@ronnypfannschmidt.de
>>
>> -- Ronny
>>
>> Am 04.08.2018 um 10:50 schrieb Florian Bruhin:
>>
>> On Tue, Jul 31, 2018 at 12:53:51PM +0100, Dave Hunt 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 tohttps://github.com/pytest-dev/pytest/community. 
>> Is there one
>> documented elsewhere? If not, which should we adopt?
>>
>> So I wanted to open a PR proposing the Contributor Covenant. However, I
>> noticed we don't have a suitable (non-public!) way of contacting us if
>> there's a need to.
>>
>> I'd propose we instead list mail addresses of some maintainers who'd be
>> interested and we feel like could handle potential conflicts in a fair
>> way.
>>
>> I'd gladly volunteer, but it'd be nice if some more people step up -
>> especially those who've been involved in pytest more from the community
>> rather than the technical side :)
>>
>> Florian
>>
>>
>>
>>
>> ___
>> pytest-dev mailing 
>> listpytest-dev@python.orghttps://mail.python.org/mailman/listinfo/pytest-dev
>>
>> ___
>> 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
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Code of conduct for pytest organisation on GitHub

[Bruno Oliveira]

Feel free to add me as well Florian.

[]s
On Sat, Aug 4, 2018 at 8:58 AM RonnyPfannschmidt <
opensou...@ronnypfannschmidt.de> wrote:

> Hi,
>
> pytest+...@ronnypfannschmidt.de
>
> -- Ronny
>
> Am 04.08.2018 um 10:50 schrieb Florian Bruhin:
>
> On Tue, Jul 31, 2018 at 12:53:51PM +0100, Dave Hunt 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 tohttps://github.com/pytest-dev/pytest/community. 
> Is there one
> documented elsewhere? If not, which should we adopt?
>
> So I wanted to open a PR proposing the Contributor Covenant. However, I
> noticed we don't have a suitable (non-public!) way of contacting us if
> there's a need to.
>
> I'd propose we instead list mail addresses of some maintainers who'd be
> interested and we feel like could handle potential conflicts in a fair
> way.
>
> I'd gladly volunteer, but it'd be nice if some more people step up -
> especially those who've been involved in pytest more from the community
> rather than the technical side :)
>
> Florian
>
>
>
>
> ___
> pytest-dev mailing 
> listpytest-dev@python.orghttps://mail.python.org/mailman/listinfo/pytest-dev
>
> ___
> 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

Re: [pytest-dev] Code of conduct for pytest organisation on GitHub

[RonnyPfannschmidt]

Hi,

pytest+...@ronnypfannschmidt.de

-- Ronny


Am 04.08.2018 um 10:50 schrieb Florian Bruhin:
> On Tue, Jul 31, 2018 at 12:53:51PM +0100, Dave Hunt 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?
> So I wanted to open a PR proposing the Contributor Covenant. However, I
> noticed we don't have a suitable (non-public!) way of contacting us if
> there's a need to.
>
> I'd propose we instead list mail addresses of some maintainers who'd be
> interested and we feel like could handle potential conflicts in a fair
> way.
>
> I'd gladly volunteer, but it'd be nice if some more people step up -
> especially those who've been involved in pytest more from the community
> rather than the technical side :)
>
> Florian
>
>
>
> ___
> 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

Re: [pytest-dev] Code of conduct for pytest organisation on GitHub

[Florian Bruhin]

On Tue, Jul 31, 2018 at 12:53:51PM +0100, Dave Hunt 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?

So I wanted to open a PR proposing the Contributor Covenant. However, I
noticed we don't have a suitable (non-public!) way of contacting us if
there's a need to.

I'd propose we instead list mail addresses of some maintainers who'd be
interested and we feel like could handle potential conflicts in a fair
way.

I'd gladly volunteer, but it'd be nice if some more people step up -
especially those who've been involved in pytest more from the community
rather than the technical side :)

Florian

-- 
https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Code of conduct for pytest organisation on GitHub

[Bruno Oliveira]

Howdy,

On Tue, Jul 31, 2018 at 3:51 PM Florian Bruhin  wrote:

> I was initially sceptical about CoCs in general as well, but after
> spending months researching the topic from both sides and talking to a
> lot of people, it got clear to me that CoCs are a very good thing -
> even/especially in communites which are already very much welcoming and
> healty.
>

I did take a look at the code of conduct, seems good to me. If you want to
go with it, you have my +1.

Cheers,
Bruno.
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Code of conduct for pytest organisation on GitHub

[Florian Bruhin]

On Tue, Jul 31, 2018 at 08:12:10PM +0200, Floris Bruynooghe wrote:
> I'm agree that we should probably have a code of conduct.  We had one
> for the sprint (we used https://www.python.org/psf/codeofconduct/ + 2
> contact details for violations) and I'm surprised it stopped at the
> sprint.  Probably an oversight.
> 
> I just skimmed through C4 again and didn't spot much useful there, in
> any case the bulk of C4 does not try to address people's conduct.  And
> the language used there is not very suitable for a code of conduct I
> think.  So I'd rather adopt another one.

I fully agree (with both paragraphs)!

> So as to which one to adopt I'm not sure.  The PSF one doesn't say
> anything about enforcement, which may not be ideal.  The PyconUK one
> isn't bad either I think.  But if Dave thinks the contributor-covenant
> is a good choice I'm happy to support that.

The PyConUK one is worded for conferences, which doesn't seem a suitable
choice for projects. We could of course rephrase it, but it's like with
licenses - there are projects where a lot of people put a lot of thought
into a given wording, so writing a homebrewed one is usually a bad idea.

+1 for the Contributor Covenant. It's well established and crafted with
a lot of attention to detail, with quite a big community[1].

I was initially sceptical about CoCs in general as well, but after
spending months researching the topic from both sides and talking to a
lot of people, it got clear to me that CoCs are a very good thing -
even/especially in communites which are already very much welcoming and
healty.

(If needed, I can go into details in September - sorry, exams are coming
closer and closer)

[1] https://github.com/ContributorCovenant/contributor_covenant

Florian

-- 
https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Code of conduct for pytest organisation on GitHub

[Floris Bruynooghe]

Hi,

I'm agree that we should probably have a code of conduct.  We had one
for the sprint (we used https://www.python.org/psf/codeofconduct/ + 2
contact details for violations) and I'm surprised it stopped at the
sprint.  Probably an oversight.

I just skimmed through C4 again and didn't spot much useful there, in
any case the bulk of C4 does not try to address people's conduct.  And
the language used there is not very suitable for a code of conduct I
think.  So I'd rather adopt another one.

So as to which one to adopt I'm not sure.  The PSF one doesn't say
anything about enforcement, which may not be ideal.  The PyconUK one
isn't bad either I think.  But if Dave thinks the contributor-covenant
is a good choice I'm happy to support that.


Cheers,
Floris


On Tue 31 Jul 2018 at 14:18 +0200, RonnyPfannschmidt wrote:

> 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 >> > wrote:
>>>
>>> Hi Dave,
>>>
>>>
>>> On Tue, Jul 31, 2018 at 8:54 AM Dave Hunt >> > 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
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Code of conduct for pytest organisation on GitHub

[RonnyPfannschmidt]

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 > > wrote:
>>
>> Hi Dave,
>>
>>
>> On Tue, Jul 31, 2018 at 8:54 AM Dave Hunt > > 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

Re: [pytest-dev] Code of conduct for pytest organisation on GitHub

[Bruno Oliveira]

Hi Dave,


On Tue, Jul 31, 2018 at 8:54 AM Dave Hunt  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] Code of conduct for pytest organisation on GitHub

[Dave Hunt]

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?

Cheers,
Dave


signature.asc
Description: Message signed with OpenPGP
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev