You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/about/code_of_conduct/_index.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ title = "Code of Conduct"
4
4
5
5
# NUMFOCUS CODE OF CONDUCT
6
6
7
-
You can find the whole document herehttps://numfocus.org/code-of-conduct.
7
+
You can find the whole document [here][NumFOCUS Code of Conduct].
8
8
9
9
## THE SHORT VERSION
10
10
@@ -22,15 +22,17 @@ Thank you for helping make this a welcoming, friendly community for all.
22
22
23
23
## LONG VERSION
24
24
25
-
You can find the long version of the Code of Conduct on the NumFOCUS website https://numfocus.org/code-of-conduct
25
+
You can find the long version of the Code of Conduct on the [NumFOCUS Code of Conduct][] page.
26
26
27
27
## HOW TO REPORT
28
28
29
-
If you feel that the Code of Conduct has been violated, feel free to submit a report, by using the form: NumFOCUS Code of Conduct Reporting Form
29
+
If you feel that the Code of Conduct has been violated, feel free to submit a report, by using the [NumFOCUS Code of Conduct Reporting Form](https://numfocus.typeform.com/to/ynjGdT).
30
30
31
31
## WHO WILL RECEIVE YOUR REPORT
32
32
33
33
Your report will be received and handled by NumFOCUS Code of Conduct Working Group; trained, and experienced contributors with diverse backgrounds.
34
-
The group is making decisions independently from the project, PyData, NumFOCUS or any other organization.
34
+
The group is making decisions independently from the project, PyData, NumFOCUS or any other organization.
35
35
36
-
You can learn more about the current group members, as well as the reporting procedure [HERE](https://numfocus.org/code-of-conduct).
36
+
You can learn more about the current group members, as well as the reporting procedure on the [NumFOCUS Code of Conduct][] page.
37
+
38
+
[NumFOCUS Code of Conduct](https://numfocus.org/code-of-conduct)
Copy file name to clipboardExpand all lines: content/about/roles/_index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ This includes who gets commit rights to their projects.
44
44
45
45
The core team are community members who have demonstrated continued commitment to the project through ongoing contributions.
46
46
They have shown they can be trusted to maintain scverse with care.
47
-
Team members appear as organization members on the scverse [GitHub organization](https://github.com/orgs/scverse/people) and are on our [@scverse/core](https://github.com/orgs/scverse/teams/core) GitHub team.
47
+
Team members appear as organization members on the scverse [GitHub organization](https://github.com/orgs/scverse/people) and are on our [@scverse/core](https://github.com/orgs/scverse/teams/core) GitHub team, but can also be reached by e-mail at [core@scverse.org](core@scverse.org).
48
48
49
49
There are sub-roles within the core team depending on the kinds covering different kinds of contributions and responsibilities.
50
50
@@ -93,7 +93,7 @@ Nominees should have demonstrated long-term, continued commitment to the project
93
93
A nomination will result in discussion that cannot take more than a month and then admission to the SC by consensus.
94
94
During that time deadlocked votes of the SC will be postponed until the new member has joined and another vote can be held.
95
95
96
-
The `scverse` steering council may be contacted at `steering-council@scverse.org`, or via the [@scverse/steering-council](https://github.com/orgs/scverse/teams/steering-council) GitHub team.
96
+
The `scverse` steering council may be contacted at [steering-council@scverse.org](mailto:steering-council@scverse.org).
-[conference@scverse.org](conference@scverse.org): for matters regarding the [next conference](/conference2025)
45
+
-[steering-council@scverse.org](steering-council@scverse.org): [steering council](/about/roles#steering-council) (e.g. for questions about sponsorships)
0 commit comments