Providing Guidance to Working Groups Around Privacy about community

[lucasgonze]

A starting point for the text of the guidance document:

Privacy Guidance for Working Groups

Metrics compilation and publication may lead to privacy violations. Each metric must be examined for potential data ethics problems.

Data relevant to a metric may have heightened sensitivity. Working groups should consider sensitivity levels.

Organizations may be exposed to risks. These risks may flow from compliance with the GDPR in the EU, with state law in the US, or with other regulations. These risks may flow from terms of service for data providers such as GitHub and GitLab.

[ElizabethN]

It was also discussed that the new Community Operations Team should have a hand in moving forward with this, since it touches on all metrics across Working Groups.

cc @germonprez

[lucasgonze]

We need to provide guidance to consumers of metrics (either implementors or consumers of implementations) as well as to working groups creating metrics.

[GeorgLink]

Thanks for the draft @lucasgonze.

I think this is a good start. I can also imagine that at some point we provide a list of ethical concerns and WGs can check which ones they might apply to any given metric.

[lucasgonze]

With regard to Silona's comments today on specific regulations in the EU, I have added a "# Relevant Regulations" section for gathering data on concrete restrictions.

[germonprez]

I'm closing this as the privacy/ethics statement has been added to all metrics -- even the Chinese/Mandarin release