New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visibility and retention of CEPC violation assessments #34
Comments
This issue was raised as a follow-on to the comment that I made to the proposed new wording in #33:
My comment was: This seems great, but realistically what can W3C do to minimise the harm caused to participants given that in this situation it has already been caused? I think what W3C will actually do is:
Perhaps we could write this down? Is this list correct and complete? Originally posted by @nigelmegitt in https://github.com/_render_node/MDIzOlB1bGxSZXF1ZXN0UmV2aWV3VGhyZWFkMTY0NjIzMjk2OnYy/pull_request_review_threads/discussion |
Thanks @nigelmegitt. I think this will be addressed as we (primarily @jorydotcom) fleshes out the work on an ombuds program. IMO, the process for these can be somewhat vague because some of this will be at the judgment of the ombuds and determined on a case by case basis. |
@TzviyaSiegman agreed the details of the process can be somewhat vague; we should write down the minimal expectations, for example about what communication is required, who should have access to records, and for how long, and if that is a matter for the ombud to decide on a case by case basis. |
Regarding |
@AdaRoseCannon good point, they should be I think, but I'm not aware of us having discussed it. Options include:
|
I think for the reporter and the person being reported on behalf of (sometimes the same person) being anonymous is important because it could invite later harassment from the reported person, even in the case where the ombuds person found no CEPC violating issue in the original situation, the reported person may hold a grudge for being reported at all against both or either reporter and the person it was on behalf of. |
So "always anonymous" unless the individual deliberately goes public, and even then, if they do that they are not permitted to de-anonymise anyone else? |
Yes, would be my go-to, or at least an option to be anonymous which defaults to 'keep me anonymous from the person being reported'. |
I'm a bit concerned about reaching a particular decision about retaining records. Each assessment is different and I worry that the keeping of records could actually discourage some people from using the process. |
I do not believe that this topic belongs in the CEPC. It may belong in the Procedures, but only once we have a more solid foundation with regard to handling confidentiality, to begin with; and because each case is different. |
We removed this line from the CEPC. It will be an issue for ombuds to assess. |
@jeffjaffe then we should say that the CEPC does not state any policy about keeping records and that they will be dealt with elsewhere. I have the converse concern, that a lack of clarity about record keeping will discourage people from using the process. I'm reopening this issue because the original issue as I raised at the top has not been addressed at all; rather it has been sidetracked by a side issue. |
@nigelmegitt the Process is a separate document. We are not addressing this in the CEPC. I have never seen a CoC address record keeping. Can you point to one that has? |
@TzviyaSiegman We don't seem to have labels on our issues to indicate which document they refer to. The procedures are in the PWE home page (Editor's Draft, source), which is in the same repo and is clearly being managed by the PWETF. I'm happy for this issue to be considered to apply to that document rather than the CEPC itself. Update: I saw that there is a CEPC label, but not a PWE-homepage label, so I added the latter and assigned it to this issue. |
Note that the Board is working on a records retention policy; see https://github.com/w3c/board/issues/13. Note that's separate from records visibility; at first blush, I'd be very reluctant to make such documents public or member-visible. Retention is more for legal purposes. |
Thank you. This will need to be part of ombuds training as well. There are concerns about both confidentiality and avoiding repeat offenders. |
When an Ombudsperson or group of Ombudspeople make an assessment about a reported violation incident, we should state that:
But what else should happen to that assessment? Should W3C keep it? Who should be able to see it? How long should it be kept for?
The text was updated successfully, but these errors were encountered: