Add a `privacy` focus and/or component

[iandunn]

It's been suggested several times^{[​1, ​2, etc]} that a new focus and/or component be created on core.trac for privacy-related issues.

What does everyone think of that? What should it be called? Should it be a focus, or a component, or both?

[desrosj]

I think "Privacy" is a good name. I can see the use case need for both.

In 4.9.6, the GDPR tickets have been labeled keyword: gdpr, component General (unless the issue clearly falls under another component). Having a component for Privacy would have helped organize a bit. But, I also see this being similar to the docs keyword. There are lots of components that may have tickets with a focus on privacy.

[allendav]

I also second "Privacy" as a good name. Keeps us from over emphasizing any particular privacy regulation.

[SergeyBiryukov]

Component created, per ​discussion in #meta: ​https://core.trac.wordpress.org/component/Privacy.

1. Who should be assigned as the component maintainers?
2. Who can help write a component description for the ​make/core page? See ​REST API page for example.

[SergeyBiryukov]

In 7211:

Trac: Add a privacy focus to core.trac.wordpress.org.

See #3622.

[SergeyBiryukov]

In 7213:

Slack: Send new tickets and commits for Privacy component and focus to #gdpr-compliance.

See #3622.

[netweb]

After discussing with each I've added @allendav, @desrosj, and @idea15 ( @webdevlaw) as component maintainers

[SergeyBiryukov]

In 8903:

Slack: Send new commits for Privacy component to #core-privacy.

See #3622, ​#WP43895.