通过 阿曼达法国 分类: 行政

在今日的会议, 该 THATCamp委员会 已同意将其张贴反骚扰政策,进行编辑和注释下列草案. 这是修订版 Code4Lib反骚扰政策, 而这又是基于 野人女性主义防骚扰 政策.

我们设想这是所有THATCamp组织者必须同意才可以采用文档 注册一个THATCamp. 我们将在今年夏天接受意见的截止日期 8月30日 (请在这个博客帖子发表评论) 并且将根据这些意见修改制作. 我们会表决通过的代码在下次THATCamp理事会会议, 这将发生在某个时候九月 2014.

  1. This seems to cover the increasingly agreed-on basics. It might be nice also to open with a less formal “short version” along the lines of the PyCon Code of Conduct. That would retain the usual THATCamp tone before laying out the (necessary) formal details of the policy. As a camper and (possibly someday) host this seems comfortable with or without that.

  2. Profile Photo

    One small suggestion, and one broad pattern observation

    Small suggestion: maybe expand

    produces an unsafe environment

    To either “produces an unsafe or unwelcoming environment” 或 “produces an unsafe or uninclusive environment”. Implicit in those options is what’s the difference between unwelcoming and uninclusive. I lean a little toward the “uninclusive” 语, as to me it says that challenging ideas can sometimes be unwelcome, but still done in an inclusive way.

    Broad pattern thing:
    We’d described using 克r该.P1521297480m一ct一1521297480HT@of1521297480ni1521297480 为 “non-public” concerns, which might include harassment problems in forums (or possibly in comments on individual sites/camps?). This doc also suggests contacting Council members. But for any particular situation at a THATCamp, the target of gro.p1521297480米acta1521297480Ĥt@of1521297480n我1521297480 and any council member won’t likely be in a position to take immediate action. I’m good with saying info/council member is a good, safe, non-public place for anything on, and also for situations that happen at any particular THATCamp that call for non-immediate attention. But I worry about suggesting info/council members can respond to immediate issues at a THATCamp. It’s the synchronous vs. asynchronous ability to take action that I’m fretting over here. It’s probably not realistic to say that a THATCamp Council member can take meaningful immediate action at any particular THATCamp, and so I worry about suggesting that we can by saying contact us in the initial incident phase if the initial incident is at a THATCamp.

    On the site, in forums or in any particular THATCamp’s site and discussion, definitely info / any council member is an appropriate place to report.

    Do we also want to say that THATCamp Council is an explicit resource for THATCamp organizers unsure about how to resolve an issue? If an issue comes up that an organizer is unsure how to respond to, is an anonymized forum post an appropriate way to get guidance? This touches on how THATCamp Council sees what it can and cannot realistically do to help.

  3. Profile Photo

    大点, 帕特里克. (I too like “uninclusive.”) It does seem like the proper “flow” for reports is to a THATCamp local organizer, who should then notify gro.p1521297480mact一1521297480ht@of1521297480ñi1521297480 and/or a member of the Council. But we should keep in something about reporting to info / the Council *instead* of to a local organizer, 我认为, though you’re right, with caveats that it might take us a couple of days to respond and so shouldn’t be used when urgent action is needed. But I can imagine reasons why someone might want to go to the Council directly.

  4. Profile Photo

    When we meet, we should probably also declare when the policy kicks in. That is, already-registered THATCamps probably shouldn’t be required to follow the policy — it would be adding a requirement that they didn’t accept at the time of registration. When, 然后, do we add the checkbox to the requirements for registering a THATCamp?

RCHN Mellon Mellon