conda-forge.github.io icon indicating copy to clipboard operation
conda-forge.github.io copied to clipboard

ENH code of conduct sub-team

Open beckermr opened this issue 3 years ago • 3 comments

@conda-forge/core I have finished the CoC sub-team charter. Comments are welcome. I will call a vote once it appears we have a consensus.

beckermr avatar Apr 28 '22 13:04 beckermr

Looks good to me -- thanks for putting this together

mwcraig avatar Apr 28 '22 13:04 mwcraig

Thanks for the comments @CJ-Wright! Can you take a pass at editing this?

I'm not sure I'll be able to capture what you are looking for efficiently.

beckermr avatar Apr 29 '22 13:04 beckermr

@CJ-Wright Did you get a chance to put in your edits here?

beckermr avatar Jun 09 '22 10:06 beckermr

It's long due we have this explicitly written somewhere, so I'd be inclined to bring this up in the next core call.

Also related to https://github.com/conda-forge/conda-forge.github.io/pull/1640

jaimergp avatar Jun 22 '23 11:06 jaimergp

We should also add a copy of our code of conduct (CODE_OF_CONDUCT.md) to the repo itself so Github picks it up as metadata. The conda-incubator community did it by taking the NF code (which we abide by, too) and adding some specific clauses. @CJ-Wright's comments are reasonable and we can try to address them in that extended document.

@beckermr what do you think about the following next steps:

  • I'll add a CODE_OF_CONDUCT.md file based on a copy of the conda-incubator CoC. That one is still based on NF so it should be compatible with ours.
  • Then I will add / adjust our own provisions there. Two separate commits so we can see the changes easily if needed.
  • Then we rephrase what we have in our subteams section so it refers to the main document as necessary.
  • Once happy, we call a standard vote to establish the CoC team.

jaimergp avatar Jun 29 '23 08:06 jaimergp

SGTM! Thanks for picking this up!

beckermr avatar Jun 29 '23 11:06 beckermr

Added some updates hopefully capturing most of the comments here!

jaimergp avatar Jul 11 '23 08:07 jaimergp

As per our governance, this should be a standard vote (public), with 50% majority pass and normal quorum (or time out) rules. If that's correct, that means we can just call it here via PR votes, right?

jaimergp avatar Jul 11 '23 11:07 jaimergp

Yep!

beckermr avatar Jul 11 '23 11:07 beckermr

@conda-forge/core:

  • This vote falls under the "Sub-team Formation" policy, please vote and/or comment on this issue.
  • This vote needs 50% of core to vote yea to pass.
  • To vote please review this PR with: "Approve" (yes) or "Request changes" (no).
  • If you would like changes to the current language please leave a comment.
  • This vote will end on July 27th 2023 at 23:59 AoE.

jaimergp avatar Jul 11 '23 14:07 jaimergp

I cannot approve my own PR but put me down for "yes!"

beckermr avatar Jul 11 '23 14:07 beckermr

Hey folks, we are going to cancel this vote temporarily (we will issue a new one soon), after receiving very important feedback in today's core call. We'll include some changes and then ask for comments; hopefully after that we can start a new vote. Thank you for understanding and sorry for the noise!

jaimergp avatar Jul 12 '23 17:07 jaimergp