Define sanctions appropriate for code4lib

[anarchivist]

As identified by @azaroth42 in 36cff4b14541c987d1b4feb40edc28c39c7757f0 :

violating these rules will be dealt with appropriately, and may be sanctioned, expelled, or banned at the discretion of the organizers or channel administrators.

What are sanctions appropriate to code4lib? From the Geek Feminism wiki, possible sanctions include:

• warning the harasser to cease their behaviour and that any further reports will result in sanctions
• requiring that the harasser avoid any interaction with, and physical proximity to, their victim for the remainder of the event
• ending a talk that violates the policy early
• not publishing the video or slides of a talk that violated the policy
• not allowing a speaker who violated the policy to give (further) talks at the event
• immediately ending any event volunteer responsibilities and privileges the harasser holds requiring that the harasser not volunteer for future events your organization runs (either indefinitely or for a certain time period)
• requiring that the harasser refund any travel grants and similar they received (this would need to be a condition of the grant at the time of being awarded)
• requiring that the harasser immediately leave the event and not return
• banning the harasser from future events (either indefinitely or for a certain time period)
• removing a harasser from membership of relevant organizations
• publishing an account of the harassment and calling for the resignation of the harasser from their responsibilities (usually pursued by people without formal authority: may be called for if the harasser is the event leader, or refuses to stand aside from the conflict of interest, or similar, typically event staff have sufficient governing rights over their space that this isn't as useful)
• providing a short report of a harasser's conduct to their employer if under some sort of "official" capacity (presenting on a product, recruiting, etc.)

[dltj]

I think it would be good to add this to a "long version" of the code of conduct, or just add it to the end of the code of conduct if we only have one version. This dovetails nicely with the change in my pull request to change this clause to "violating these rules should expect to be...sanctioned, expelled".

[mjgiarlo]

I pared down the above list of sanctions to include only the ones that made sense in the code4lib context:

• warning the harasser to cease their behavior and that any further reports will result in other sanctions
• requiring that the harasser avoid any interaction with, and physical proximity to, their victim for the remainder of the event
• ending a talk that violates the policy early
• not publishing the video or slides of a talk that violated the policy
• not allowing a speaker who violated the policy to give (further) talks at the event
• immediately ending any event volunteer responsibilities and privileges the harasser holds requiring that the harasser not volunteer for future events your organization runs (either indefinitely or for a certain time period)
• requiring that the harasser immediately leave the event and not return
• banning the harasser from future events (either indefinitely or for a certain time period)
• publishing an account of the harassment

[dltj]

+1 for mjgiarlo's pared down list.

[mjgiarlo]

Can we link to, or list, these sanctions and consider our alpha code of conduct done? I'm not trying to rush this, exactly, but I would like to get a version published and then iterate rather than get bogged down in the weeds. We all do that with our software projects, right?

[anarchivist]

Closed by 6ea8bb09b86f2a0d40a6264666413ea6c8c6fd6a. @mjgiarlo - we do have a version published! It's the one on Github!