search

OCNS / SoftwareWG

The primary housekeeping repository for the INCF/OCNS Software Working Group, and the sources for the web site.
https://ocns.github.io/SoftwareWG/
11 stars 3 forks source link

CoC for WG #123

Closed sanjayankur31 closed 1 year ago

sanjayankur31 commented 1 year ago

We don't have an explicit CoC for the WG, and we really should.

I propose we adopt the OCNS CoC for a start, and then make any further tweaks if required. The bit we do need to change is how it'll be enforced---I expect the chairs will be responsible for that particular bit.

https://www.cnsorg.org/code-of-conduct

Please take a look at let us know what you think, and we'll add the necessary info to our website when we're ready.

appukuttan-shailesh commented 1 year ago

Thanks @sanjayankur31 I agree, this can be used as a starting point, and can be adapted later as and when required.

sanjayankur31 commented 1 year ago

CC (just to make sure folks get a notification): @OCNS/software-wg

brenthuisman commented 1 year ago

The main thing/change is to have a contact point and one or more people who will handle any inquiries to it. Could that be the OCNS contact point and people? That would have the advantage of having some distance from the people commonly in this workgroup.

sanjayankur31 commented 1 year ago

Hrm, I'm not sure that'll necessarily result in "distance from.." because there's no real guarantee that folks from the OCNS board will (or will not) participate in the group. (We've had Thomas attend lots of meetings in the past, for example.)

It's usually members of the group that do it---the chairs or another small subset. I don't expect it to be needed often---it's usually very much a large resort when things have got to a stage when some action must be taken. The intention is always to diffuse situations before they escalate to such a point.