Skip to content

Adopt the NumFOCUS Code of Conduct #1735

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Jul 4, 2025

Conversation

JuliaSprenger
Copy link
Member

As decided in the last Neo Core Meeting, this MR replaces the current CoC with the NumFOCUS CoC. As recommended by NumFOCUS the MR does not copy the CoC, but rather links to the NumFOCUS document.

Furthermore this implies that Neo is now employing the NumFOCUS workflow for reporting CoC violations and NumFOCUS will advise Neo maintainers on how to proceed in case of a CoC violation.

The CoC also applies for events organized by the Neo Team, where the CoC will be introduced in the beginning of the event and a dedicated CoC contact person will be assigned.

Once this MR is merged I we will also announce the CoC change on the community mailing list.

@apdavison
Copy link
Member

Hi Julia,

Thanks for starting this. I think this needs more context, I don't think we yet mention in the docs that we're a NumFocus affiliated project, so people might wonder why the CoC talks about NumFocus but not Neo. Could you update the text in doc/source/governance.rst, and perhaps also add a paragraph at the start of doc/source/contributing.rst?

@apdavison apdavison self-assigned this Jun 27, 2025
@apdavison apdavison added this to the 0.14.2 milestone Jun 27, 2025
@zm711
Copy link
Contributor

zm711 commented Jul 3, 2025

Just a reminder we are doing the next release Monday or Tuesday of next week. So if we want the new code of conduct we should try to get that done today/tomorrow ideally or we can discuss on Monday.

@apdavison
Copy link
Member

My apologies for committing directly to your branch Julia, but I can't attend the maintainers' meeting on Monday, so I wanted to get these changes in before the release.

@apdavison apdavison merged commit 6a7b3e3 into NeuralEnsemble:master Jul 4, 2025
5 checks passed
@JuliaSprenger
Copy link
Member Author

No problem, thanks for fixing and merging it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants