Skip to content
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

Open
nigelmegitt opened this issue Mar 27, 2019 · 16 comments
Open

Visibility and retention of CEPC violation assessments #34

nigelmegitt opened this issue Mar 27, 2019 · 16 comments
Labels
Decision Needed Decision Needed for next version of CEPC policy PWE-homepage Issues with the content on the PWE homepage

Comments

@nigelmegitt
Copy link
Collaborator

When an Ombudsperson or group of Ombudspeople make an assessment about a reported violation incident, we should state that:

  • the reported participants in the incident will be informed of the assessment.

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?

This was referenced Mar 27, 2019
@nigelmegitt
Copy link
Collaborator Author

This issue was raised as a follow-on to the comment that I made to the proposed new wording in #33:

If such behaviour occurs W3C will act to minimise the harm caused to participants and the likelihood of the behaviour being repeated.

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:

  • provide impartial Ombudspeople who will:
    • assess whether or not the reported incident is a violation of the CEPC;
    • inform all the reported participants in the incident of the result of this assessment;
  • keep a confidential record of the assessment, available to [WHO SHOULD HAVE ACCESS?] for [HOW LONG SHOULD WE KEEP IT FOR?];
  • potentially take further action in relation to any individuals who have violated the CEPC.

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

@TzviyaSiegman
Copy link
Collaborator

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.

@nigelmegitt
Copy link
Collaborator Author

@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.

@AdaRoseCannon
Copy link
Collaborator

Regarding the reported participants in the incident will be informed of the assessment. is the person who raised it and the person is was on behalf of kept anonymous?

@nigelmegitt
Copy link
Collaborator Author

@AdaRoseCannon good point, they should be I think, but I'm not aware of us having discussed it. Options include:

  • Always anonymous
  • Anonymous only on request
  • Anonymous under judgement of the Ombudsperson
  • Never anonymous

@AdaRoseCannon
Copy link
Collaborator

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.

@nigelmegitt
Copy link
Collaborator Author

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?

@AdaRoseCannon
Copy link
Collaborator

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'.

@lianqi lianqi added the Decision Needed Decision Needed for next version of CEPC label Oct 31, 2019
@jeffjaffe
Copy link

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.

@brewerj
Copy link
Contributor

brewerj commented Oct 31, 2019

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.

@TzviyaSiegman
Copy link
Collaborator

We removed this line from the CEPC. It will be an issue for ombuds to assess.

@nigelmegitt
Copy link
Collaborator Author

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.

@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 nigelmegitt reopened this Dec 5, 2019
@TzviyaSiegman
Copy link
Collaborator

@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?

@nigelmegitt
Copy link
Collaborator Author

nigelmegitt commented Dec 12, 2019

@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.

@nigelmegitt nigelmegitt added the PWE-homepage Issues with the content on the PWE homepage label Dec 12, 2019
@wareid wareid added the policy label Jan 22, 2020
@mnot
Copy link
Member

mnot commented Jun 28, 2023

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.

@TzviyaSiegman
Copy link
Collaborator

Thank you. This will need to be part of ombuds training as well. There are concerns about both confidentiality and avoiding repeat offenders.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Decision Needed Decision Needed for next version of CEPC policy PWE-homepage Issues with the content on the PWE homepage
Projects
None yet
Development

No branches or pull requests

8 participants