make a policy for changing code of conduct

[slacksoc]

After issue #22 is adopted we need a way to change it.

Issue created via slack on behalf of tadh (Tim Henderson)

[brenns10]

Proposed process for updating a code of conduct (remarkably similar to adopting)

1. Pull request with updated draft. Solicit review from people (exec members would probably be nice).
2. Discuss in GB meeting. If there is general agreement, send out the draft to the mailing list to notify people that a vote will occur next meeting.
3. Conduct a vote, and if the majority supports the change, merge pull request.

For smaller changes (wording, typo, etc) it's probably reasonable to simple get a review or two from exec members. But as far as "what defines small changes" - that would have to be a "you know it when you see it" thing. Any reviewer should be able to blow the whistle and escalate to a full vote if they think it necessary.

[brenns10]

I say "exec members", but as a person who has never been ACM exec or Hacsoc maintainer, I do want to throw in that maybe "well-known contributors" to Hacsoc should be included in that term.

[ajm188]

Throwing in my two cents:

This seems mostly reasonable to me. My only concern as an alum who is still involved is that I won't be able to participate in the GB discussions/votes

[brenns10]

As far as discussions go... yeah. Your input is best heard on CRs for the drafts at this point, since being at GB is kinda impractical.

As far as your vote goes, I'm sure it can be given on slack before the GB meeting and counted.

Of course, that's kind of up to current leadership and how they want to handle alum participation. I think it's wise to take alum input pretty seriously. But on the other hand, as somebody who has one foot out the door, I already prefer to leave decisions to newer/younger/more recent members and leaders, since it more directly impacts them.

[brenns10]

Not that I've ever been much of a Hacsoc decision maker!