Code of Conduct violation contact

[rbeyer]

We need to have a contact for individuals to report Code of Conduct violations. What should we set up?

[jessemapel]

The e-mail listing we used for the PS TSC seems like a good solution. Could we setup something like that for the ISIS TC?

[rfergason]

I don't see why we couldn't set up an email listing for the ISIS TC. How does the PS TSC work (i.e., do you have to check a separate email account, or are emails automatically forwarded to members)?

Do you know who/how we set up that listing before? I'm happy to take care of this action, so long as I am aimed in a productive direction. I am assuming that all members listed in https://github.com/USGS-Astrogeology/ISIS_TC/blob/master/Members.md would be included in the email listing. Let me know if this assumption is incorrect.

[rbeyer]

Jay Laura (but really, anyone could have), set up a list via gaggle.email for the PSO TSC, which I had never heard of before, and have no idea as regards to security or quality, but it was a start. No, not all members should be included, only those that volunteer. This is not a general contact list, but more like an ombuds reporting mechanism: if someone has code of conduct issues, this is the contact. Not all TC members may want to participate in receiving and dealing with such complaints, but as long as we have three individuals on that list (I would volunteer), we should be fine (in case the complaint is about one of them, the other two can work the issue).

[KrisBecker]

Limiting the number of recipients of a complaint as Ross suggests is appealing. However, I think it be good to limit recipients to a short list of say just three individuals. Privacy is a concern and those submitting the complaint should know exactly who will see the complaint. This because the issue could involve a recipient and the submitter may not wish for that individual to see the complaint.

I like the suggestions/recommendations put forth by OpenSource.guide, particularly section 3 that discusses how to handle the privacy issue when one (or more!) of the recipients is involved.

The mail list would be fine, but the recipients should be listed to address privacy concerns. An alternative contact could be provided should the complaint include one of the recipients.

BTW, all the links in the BasePolicies/CODE_OF_CONDUCT.md are broken. I don't think that is intented but it could be as it is designated as a template.

[rbeyer]

I plan on reading that guide you mentioned, and I agree that putting more thought into how that is handled, would be great (for this group and the PSO TSC). By all means, file a PR here or on the PSO TSC repo.

I believe that all of the material in the ISIS_TC/BasePolicies/ directory is woefully out of date. We either need to decide to delete it for now, or commit to fixing it in the near term. This ISIS_TC repo suffers from a lot of these 'old' documents that have been lingering since before we formed the PSO TSC and improved a lot of these ideas.