WordPress.org

Making WordPress.org

Opened 14 months ago

Last modified 5 months ago

#3660 assigned enhancement

WordPress.org and Rosetta privacy pages mentions WordCamp Central’s DPO instead of w.org

Reported by: audrasjb Owned by: tellyworth
Milestone: Priority: normal
Component: General Keywords: has-patch
Cc:

Description

URL: https://wordpress.org/about/privacy/ and on all Rosetta websites.

At the bottom of the page:

Please contact us if you have any questions about our privacy policy or information we hold about you by emailing dpo@….

I guess the email address should be a generic dpo@… or privacy@… for better understanding since DPO is an english and not universally understandable term.

Cheers,
Jb

Attachments (1)

3660.diff (1.4 KB) - added by audrasjb 14 months ago.
Replace dpo@… email with privacy@… email

Download all attachments as: .zip

Change History (10)

#1 @obenland
14 months ago

  • Owner set to tellyworth
  • Status changed from new to assigned

@audrasjb
14 months ago

Replace dpo@… email with privacy@… email

#2 @audrasjb
14 months ago

  • Keywords has-patch added; needs-patch removed

#3 @Otto42
14 months ago

At present, this is intentionally set to dpo@… because that is a current and valid email address. Since WordCamp.org shares logins with WordPress.org (as well as buddypress.org, bbpress.org, etc), then it's basically the same system.

Making an additional email address and forwarder is possible, but it would simply forward to the same people.

#4 follow-up: @SergeyBiryukov
14 months ago

Creating a privacy@wordpress.org alias makes sense to me.

This ticket was mentioned in Slack in #meta by obenland. View the logs.


14 months ago

#6 @ocean90
6 months ago

#4215 was marked as a duplicate.

#7 @ocean90
6 months ago

  • Component changed from International Sites (Rosetta) to General
  • Type changed from defect to enhancement

#8 in reply to: ↑ 4 @garrett-eclipse
6 months ago

Replying to SergeyBiryukov:

Creating a privacy@wordpress.org alias makes sense to me.

I agree setting up an alias makes the most sense to me and would remove any confusion or concerns an end-user would have seeing a privacy email that's not under the same domain as the one they're raising a concern with.
Note: I've seen this question, as to why an @wordcamp.org email is being used, raised a few times now in #core-privacy.

Also looking at @audrasjb's patch 3660.diff I wonder if we protect the email address by removing it from the translation string with a printf.

This ticket was mentioned in Slack in #core-privacy by webdevlaw. View the logs.


5 months ago

Note: See TracTickets for help on using tickets.